2009-05-16 02:14:59 +02:00
|
|
|
# Template file for 'gdb'
|
|
|
|
|
pkgname=gdb
|
2009-10-29 02:00:13 +01:00
|
|
|
version=7.0
|
2009-05-16 02:14:59 +02:00
|
|
|
distfiles="http://ftp.gnu.org/gnu/$pkgname/$pkgname-$version.tar.gz"
|
|
|
|
|
build_style=gnu_configure
|
2009-10-29 02:00:13 +01:00
|
|
|
configure_args="--disable-nls"
|
2009-05-16 02:14:59 +02:00
|
|
|
short_desc="The GNU Debugger"
|
|
|
|
|
maintainer="Juan RP <xtraeme@gmail.com>"
|
2009-10-29 02:00:13 +01:00
|
|
|
checksum=ccff6cab0e847c486d30b70bdddac4e6646bafcecaa3b63134d6e3d4d5a4b91d
|
2009-05-16 02:14:59 +02:00
|
|
|
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
|
2009-11-07 19:21:34 +01:00
|
|
|
Add_dependency build texinfo
|
|
|
|
|
Add_dependency build gettext
|
2009-05-16 02:14:59 +02:00
|
|
|
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
|
|
|
|
|
}
|
