Added new version 3.0.1 of valgrind that defaults to building without PIE (solves...
authorMaurice van der Pot <griffon26@gentoo.org>
Tue, 30 Aug 2005 20:01:54 +0000 (20:01 +0000)
committerMaurice van der Pot <griffon26@gentoo.org>
Tue, 30 Aug 2005 20:01:54 +0000 (20:01 +0000)
Package-Manager: portage-2.0.51.22-r1

dev-util/valgrind/ChangeLog
dev-util/valgrind/Manifest
dev-util/valgrind/files/digest-valgrind-3.0.1 [new file with mode: 0644]
dev-util/valgrind/valgrind-3.0.1.ebuild [new file with mode: 0644]

index 45ec6a561293fc01cee5e9302662e7a8015bc270..e1b1811bb32ff384adc8f1e75db646789ed9759a 100644 (file)
@@ -1,6 +1,14 @@
 # ChangeLog for dev-util/valgrind
 # Copyright 2000-2005 Gentoo Foundation; Distributed under the GPL v2
-# $Header: /var/cvsroot/gentoo-x86/dev-util/valgrind/ChangeLog,v 1.52 2005/08/04 22:31:25 herbs Exp $
+# $Header: /var/cvsroot/gentoo-x86/dev-util/valgrind/ChangeLog,v 1.53 2005/08/30 20:01:54 griffon26 Exp $
+
+*valgrind-3.0.1 (30 Aug 2005)
+
+  30 Aug 2005; Maurice van der Pot <griffon26@gentoo.org>
+  +valgrind-3.0.1.ebuild:
+  Added version 3.0.1 of valgrind. This one is built without PIE as it seems to
+  cause trouble from time to time. This should fix bug #102157 reported by Dizzy
+  <dizzy@roedu.net>.
 
   04 Aug 2005; Herbie Hopkins <herbs@gentoo.org> valgrind-3.0.0.ebuild:
   Marked ~amd64 wrt bug #101386.
index 382f62146853c846df562fb9dc0d3367481915b0..1f8e7d02393018d45ee9bf9d80f9a892ae70ef83 100644 (file)
@@ -1,26 +1,28 @@
 -----BEGIN PGP SIGNED MESSAGE-----
 Hash: SHA1
 
-MD5 98fd3a4e78d2c75a2de9d2f7595a649c valgrind-2.4.0.ebuild 1407
+MD5 799f0b61a3a686b4074bd61acc572c5c metadata.xml 1003
+MD5 fc311d6ac7b19d831f6e18e9588c2053 valgrind-3.0.1.ebuild 1690
+MD5 c0a200046e327d2c145fc55f2611607f ChangeLog 5691
 MD5 16efe20081a8edc14768a1ea1e4664be valgrind-3.0.0.ebuild 1799
 MD5 9c6171e63f2c500b26cd6c2dd98d42e8 valgrind-2.2.0-r2.ebuild 1716
+MD5 98fd3a4e78d2c75a2de9d2f7595a649c valgrind-2.4.0.ebuild 1407
 MD5 cb18085a00f509803e6e539543cb20f9 valgrind-2.4.1.ebuild 1881
-MD5 9094dca5251546e931a2385bae050e9d ChangeLog 5389
-MD5 799f0b61a3a686b4074bd61acc572c5c metadata.xml 1003
-MD5 24971d28d91da6c61168fa217d10b47b files/valgrind-3.0.0-pie-fix.patch 864
-MD5 c67ef295757f9c8b4e9be146f6c4f873 files/valgrind-2.4.1-dont-trample-cflags.patch 442
-MD5 d177de2c2f79d24d4ad74644ee49f667 files/valgrind-2.4.1-static-const.patch 4397
 MD5 fc1dda2b6f2603a4244ad25f555f2034 files/valgrind-2.2.0-no-exec-stack.patch 1711
-MD5 c6fe697b4c25fb9e5c7482496ebabf06 files/digest-valgrind-2.4.0 140
-MD5 a5dde62cbb4bb255219643b61493b950 files/digest-valgrind-2.4.1 68
-MD5 af6b49666df28ad2a40f2f644fefce83 files/digest-valgrind-3.0.0 68
+MD5 26192577445b467e528408118f7ee6ec files/digest-valgrind-2.2.0-r2 139
 MD5 d10a593e8cb1c5074c438adc226d1c81 files/valgrind-2.2.0-current-macro-clash.patch 1871
+MD5 c6fe697b4c25fb9e5c7482496ebabf06 files/digest-valgrind-2.4.0 140
 MD5 e878f97b4c6308515baf5abaee045ce7 files/valgrind-2.4.0-pie-fix.patch 2335
-MD5 26192577445b467e528408118f7ee6ec files/digest-valgrind-2.2.0-r2 139
+MD5 af6b49666df28ad2a40f2f644fefce83 files/digest-valgrind-3.0.0 68
+MD5 a5dde62cbb4bb255219643b61493b950 files/digest-valgrind-2.4.1 68
+MD5 c67ef295757f9c8b4e9be146f6c4f873 files/valgrind-2.4.1-dont-trample-cflags.patch 442
+MD5 d177de2c2f79d24d4ad74644ee49f667 files/valgrind-2.4.1-static-const.patch 4397
+MD5 24971d28d91da6c61168fa217d10b47b files/valgrind-3.0.0-pie-fix.patch 864
+MD5 bcce75140a2ec484339b6d1844e20a0a files/digest-valgrind-3.0.1 68
 -----BEGIN PGP SIGNATURE-----
-Version: GnuPG v1.4.2 (GNU/Linux)
+Version: GnuPG v1.4.1 (GNU/Linux)
 
-iD8DBQFC8pdM2G5bA0cA/ScRAiVaAJwIIuVFk/wb8p1liiZXTLH3dd8zKACguUPj
-BCKdA7Akc0Uk4DZgQa75N0A=
-=DkfR
+iD8DBQFDFLsnMGnpIbeahxwRAnblAKCujbxLNGuaMTeTVV4Y7/pkD6PILACgp5tb
+0InkqH9bkQAJ//1vfeNGao0=
+=cN6Y
 -----END PGP SIGNATURE-----
diff --git a/dev-util/valgrind/files/digest-valgrind-3.0.1 b/dev-util/valgrind/files/digest-valgrind-3.0.1
new file mode 100644 (file)
index 0000000..ded1c70
--- /dev/null
@@ -0,0 +1 @@
+MD5 c29efdb7d1a93440f5644a6769054681 valgrind-3.0.1.tar.bz2 2688531
diff --git a/dev-util/valgrind/valgrind-3.0.1.ebuild b/dev-util/valgrind/valgrind-3.0.1.ebuild
new file mode 100644 (file)
index 0000000..26904a9
--- /dev/null
@@ -0,0 +1,56 @@
+# Copyright 1999-2005 Gentoo Foundation
+# Distributed under the terms of the GNU General Public License v2
+# $Header: /var/cvsroot/gentoo-x86/dev-util/valgrind/valgrind-3.0.1.ebuild,v 1.1 2005/08/30 20:01:54 griffon26 Exp $
+
+inherit eutils flag-o-matic
+
+DESCRIPTION="An open-source memory debugger for GNU/Linux"
+HOMEPAGE="http://www.valgrind.org"
+SRC_URI="http://www.valgrind.org/downloads/${P}.tar.bz2"
+
+LICENSE="GPL-2"
+SLOT="0"
+KEYWORDS="-* ~amd64 ~ppc ~x86"
+IUSE="X"
+
+# bug #49147 (bogus stacktrace in gdb with --db-attach=yes) does not seem to be applicable anymore
+#RESTRICT="strip"
+
+src_unpack() {
+       unpack ${A}
+       cd "${S}"
+
+       # make sure our CFLAGS are respected
+       einfo "Changing configure to respect CFLAGS"
+       sed -i -e 's:CFLAGS="-Wno-long-long":CFLAGS="$CFLAGS -Wno-long-long":' configure
+
+       # Correct hard coded doc location
+       sed -i -e "s:doc/valgrind/:doc/${P}/:" docs/Makefile.in
+}
+
+src_compile() {
+       local myconf
+
+       # -fomit-frame-pointer  "Assembler messages: Error: junk `8' after expression"
+       #                       while compiling insn_sse.c in none/tests/x86
+       # -fpie                 valgrind seemingly hangs when built with pie on
+       #                       amd64 (bug #102157)
+       # -fstack-protector     ???
+       # -ggdb3                segmentation fault on startup
+       filter-flags -fomit-frame-pointer
+       filter-flags -fpie
+       #filter-flags -fstack-protector
+       replace-flags -ggdb3 -ggdb2
+
+       # Optionally build in X suppression files
+       use X && myconf="--with-x" || myconf="--with-x=no"
+
+       econf ${myconf} || die "Configure failed!"
+       emake || die "Make failed!"
+}
+
+src_install() {
+       make DESTDIR="${D}" install || die "Install failed!"
+       dodoc ACKNOWLEDGEMENTS AUTHORS FAQ.txt NEWS README*
+}
+