void-packages/srcpkgs/gdb/template

41 lines
1.5 KiB
Plaintext
Raw Normal View History

# Template file for 'gdb'
pkgname=gdb
2012-11-30 05:44:13 +01:00
version=7.5.1
2013-03-13 21:31:55 +01:00
revision=2
build_style=gnu-configure
2012-11-30 05:44:13 +01:00
configure_args="--disable-nls --with-system-readline
--with-system-gdbinit=/etc/gdb/gdbinit"
makedepends="ncurses-devel zlib-devel readline-devel python-devel"
2013-03-13 21:31:55 +01:00
crossmakedepends="${makedepends}"
short_desc="The GNU Debugger"
maintainer="Juan RP <xtraeme@gmail.com>"
2011-07-30 10:12:00 +02:00
homepage="http://www.gnu.org/software/gdb/"
license="GPL-3"
2012-08-20 11:28:19 +02:00
distfiles="http://ftp.gnu.org/gnu/gdb/gdb-$version.tar.bz2"
2012-11-30 05:44:13 +01:00
checksum=070b808d289fa8f0291738eeaccc0cd7700d476998781f572856155240d29d20
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:
2013-03-13 21:31:55 +01:00
* 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.
2013-03-13 21:31:55 +01:00
* Change things in your program, so you can experiment with correcting the
effects of one bug and go on to learn about another."
2011-11-14 21:19:45 +01:00
pycompile_dirs="usr/share/gdb/python/gdb"
2011-07-30 10:12:00 +02:00
conf_files="/etc/gdb/gdbinit"
2012-01-25 09:15:12 +01:00
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
}