Added gdb-6.8 template.
--HG-- extra : convert_revision : a2559f14025f3b38b81511e7283878e6369add81
This commit is contained in:
parent
14ce2422be
commit
dd9f4c519a
|
@ -0,0 +1,41 @@
|
|||
# Template file for 'gdb'
|
||||
pkgname=gdb
|
||||
version=6.8
|
||||
distfiles="http://ftp.gnu.org/gnu/$pkgname/$pkgname-$version.tar.gz"
|
||||
build_style=gnu_configure
|
||||
configure_args="--disable-werror"
|
||||
short_desc="The GNU Debugger"
|
||||
maintainer="Juan RP <xtraeme@gmail.com>"
|
||||
checksum=a3c5455f30ffb3e6eeafb9e54598b48f9fbf46e3e99f431120360c183ddcc889
|
||||
long_desc="
|
||||
The purpose of a debugger such as GDB is to allow you to see what
|
||||
is going on \"inside\" another program while it executes--or what
|
||||
another program was doing at the moment it crashed.
|
||||
|
||||
GDB can do four main kinds of things (plus other things in support
|
||||
of these) to help you catch bugs in the act:
|
||||
|
||||
* Start your program, specifying anything that might affect its
|
||||
behavior.
|
||||
|
||||
* Make your program stop on specified conditions.
|
||||
|
||||
* Examine what has happened, when your program has stopped.
|
||||
|
||||
* Change things in your program, so you can experiment with
|
||||
correcting the effects of one bug and go on to learn about
|
||||
another."
|
||||
|
||||
Add_dependency full glibc
|
||||
Add_dependency full expat
|
||||
Add_dependency build ncurses
|
||||
Add_dependency run ncurses-libs
|
||||
|
||||
post_install()
|
||||
{
|
||||
# resolve conflicts with binutils
|
||||
rm -rf ${DESTDIR}/usr/include ${DESTDIR}/usr/lib
|
||||
for f in bfd configure standards; do
|
||||
rm -f ${DESTDIR}/usr/share/info/${f}.info*
|
||||
done
|
||||
}
|
Loading…
Reference in New Issue