void-packages/srcpkgs/gdb/template

45 lines
1.5 KiB
Plaintext
Raw Normal View History

# Template file for 'gdb'
pkgname=gdb
2010-05-06 00:11:23 +02:00
version=7.1
distfiles="http://ftp.gnu.org/gnu/$pkgname/$pkgname-$version.tar.bz2"
build_style=gnu_configure
configure_args="--disable-nls"
short_desc="The GNU Debugger"
maintainer="Juan RP <xtraeme@gmail.com>"
2010-05-06 00:11:23 +02:00
checksum=142c27d7970a4e652dc225d61d887777ae00cf22fdd75cd1e8e4e13bfbd85352
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 run glibc
Add_dependency run expat
2010-05-06 00:11:23 +02:00
Add_dependency run ncurses-libs
Add_dependency run zlib
Add_dependency run python
Add_dependency build texinfo
Add_dependency build ncurses-devel
Add_dependency build zlib-devel
Add_dependency build python-devel
post_install()
{
# resolve conflicts with binutils
rm -rf ${DESTDIR}/usr/include ${DESTDIR}/usr/lib
[ -d ${DESTDIR}/usr/lib64 ] && rm -rf ${DESTDIR}/usr/lib64
for f in bfd configure standards; do
rm -f ${DESTDIR}/usr/share/info/${f}.info*
done
}