diff options
Diffstat (limited to 'dev-util/boost-build')
23 files changed, 1931 insertions, 0 deletions
diff --git a/dev-util/boost-build/ChangeLog b/dev-util/boost-build/ChangeLog new file mode 100644 index 0000000..3c0683b --- /dev/null +++ b/dev-util/boost-build/ChangeLog @@ -0,0 +1,336 @@ +# ChangeLog for dev-util/boost-build +# Copyright 1999-2012 Gentoo Foundation; Distributed under the GPL v2 +# $Header: /var/cvsroot/gentoo-x86/dev-util/boost-build/ChangeLog,v 1.83 2012/04/02 01:09:10 floppym Exp $ + + 02 Apr 2012; Mike Gilbert <floppym@gentoo.org> -boost-build-1.48.0.ebuild: + Remove. + +*boost-build-1.49.0 (02 Apr 2012) + + 02 Apr 2012; Mike Gilbert <floppym@gentoo.org> +boost-build-1.49.0.ebuild: + Version bump. + +*boost-build-1.48.0-r1 (19 Jan 2012) + + 19 Jan 2012; Markos Chandras <hwoarang@gentoo.org> + +boost-build-1.48.0-r1.ebuild, + +files/boost-build-1.48.0-disable_python_rpath.patch, + +files/boost-build-1.48.0-support_dots_in_python-buildid.patch: + Remove directory used for searching of libpythonX.Y.so from rpath of all + libraries, which would occur in some situations. Initial support for dots in + argument of --python-buildid option. Patch by Arfrever + +*boost-build-1.48.0 (08 Jan 2012) + + 08 Jan 2012; Markos Chandras <hwoarang@gentoo.org> +boost-build-1.48.0.ebuild: + Version bump. Bug #391663 + + 28 Dec 2011; Mark Loeser <halcy0n@gentoo.org> boost-build-1.46.1.ebuild: + Stable for ppc64; bug #377805 + + 20 Oct 2011; Brent Baude <ranger@gentoo.org> boost-build-1.46.1.ebuild: + Marking boost-build-1.46.1 ppc for bug 377805 + +*boost-build-1.47.0 (26 Sep 2011) + + 26 Sep 2011; Markos Chandras <hwoarang@gentoo.org> + +boost-build-1.47.0.ebuild: + Version bump. Bug #376937 + + 16 Sep 2011; Jeroen Roovers <jer@gentoo.org> boost-build-1.46.1.ebuild: + Stable for HPPA (bug #377805). + + 10 Sep 2011; Raúl Porcel <armin76@gentoo.org> boost-build-1.46.1.ebuild: + alpha/ia64/s390/sh/sparc stable wrt #377805 + + 28 Aug 2011; Markus Meier <maekke@gentoo.org> boost-build-1.46.1.ebuild: + arm stable, bug #377805 + + 22 Aug 2011; Tony Vroon <chainsaw@gentoo.org> boost-build-1.46.1.ebuild: + Marked stable on AMD64 as a dependency of dev-libs/boost-1.46.1 based on arch + testing by Agostino "ago" Sarubbo in bug #377805. + + 12 Aug 2011; Thomas Kahle <tomka@gentoo.org> boost-build-1.46.1.ebuild: + x86 stable per bug 377805 + + 10 Jul 2011; Alexis Ballier <aballier@gentoo.org> boost-build-1.46.1.ebuild: + keyword ~x86-fbsd + + 16 Apr 2011; Raúl Porcel <armin76@gentoo.org> boost-build-1.42.0.ebuild: + ia64/s390/sh stable wrt #344677 + +*boost-build-1.46.1 (22 Mar 2011) + + 22 Mar 2011; Markos Chandras <hwoarang@gentoo.org> + +boost-build-1.46.1.ebuild: + Version bump. Bug #356479 + + 13 Mar 2011; Markus Meier <maekke@gentoo.org> boost-build-1.42.0.ebuild: + arm stable, bug #344677 + + 08 Mar 2011; Tobias Klausmann <klausman@gentoo.org> + boost-build-1.42.0.ebuild: + Stable on alpha, bug #344677 + + 06 Mar 2011; Kacper Kowalik <xarthisius@gentoo.org> + boost-build-1.42.0.ebuild: + ppc64 stable wrt #344677 + + 21 Feb 2011; Michael Weber <xmw@gentoo.org> boost-build-1.42.0.ebuild: + sparc stable, bug 344677 + + 10 Jan 2011; Markos Chandras <hwoarang@gentoo.org> boost-build-1.42.0.ebuild: + Stable on amd64 wrt bug 344677 + + 08 Jan 2011; Brent Baude <ranger@gentoo.org> boost-build-1.42.0.ebuild: + Marking boost-build-1.42.0 ppc for bug 344677 + +*boost-build-1.45.0 (06 Jan 2011) + + 06 Jan 2011; Tiziano Müller <dev-zero@gentoo.org> + +boost-build-1.45.0.ebuild: + Version bump (bug #320039). + + 01 Jan 2011; Thomas Kahle <tomka@gentoo.org> boost-build-1.42.0.ebuild: + x86 stable per bug 344677 + + 12 Dec 2010; Markos Chandras <hwoarang@gentoo.org> metadata.xml: + add myself on metadata + + 09 Dec 2010; Dirkjan Ochtman <djc@gentoo.org> metadata.xml: + Remove myself as a maintainer. + + 24 Nov 2010; Jeroen Roovers <jer@gentoo.org> boost-build-1.42.0.ebuild: + Stable for HPPA (bug #344677). + + 19 Sep 2010; Raúl Porcel <armin76@gentoo.org> boost-build-1.41.0.ebuild: + s390 stable wrt #306335 + + 14 Aug 2010; Ryan Hill <dirtyepic@gentoo.org> boost-build-1.34.1.ebuild, + boost-build-1.35.0-r1.ebuild, boost-build-1.35.0-r2.ebuild, + boost-build-1.37.0.ebuild, boost-build-1.39.0.ebuild, + boost-build-1.40.0.ebuild, boost-build-1.41.0.ebuild, + boost-build-1.42.0.ebuild, +files/boost-build-1.42-env-whitespace.patch: + Fix build failures when compiler flags contain whitespace (bug #293652 by + Sebastian Luther). + + 22 Apr 2010; Samuli Suominen <ssuominen@gentoo.org> + -boost-build-1.36.0.ebuild: + Remove boost-1.36.0 for gcc-porting wrt #287638. + + 17 Apr 2010; Joseph Jezak <josejx@gentoo.org> boost-build-1.41.0.ebuild: + Marked ppc stable for bug #305195. + + 31 Mar 2010; Raúl Porcel <armin76@gentoo.org> boost-build-1.41.0.ebuild: + alpha/arm/ia64/sh/sparc stable wrt #306335 + + 27 Mar 2010; Pacho Ramos <pacho@gentoo.org> boost-build-1.41.0.ebuild: + amd64 stable, security bug 305195 + + 21 Mar 2010; Brent Baude <ranger@gentoo.org> boost-build-1.41.0.ebuild: + Marking boost-build-1.41.0 ppc64 for bug 306335 + + 04 Mar 2010; Jeroen Roovers <jer@gentoo.org> boost-build-1.41.0.ebuild: + Stable for HPPA (bug #306333). + +*boost-build-1.42.0 (03 Mar 2010) + + 03 Mar 2010; Dirkjan Ochtman <djc@gentoo.org> + +files/boost-1.42-fix-mpich2-detection.patch, +boost-build-1.42.0.ebuild: + Version bump to dev-util/boost-build-1.42.0. + + 03 Mar 2010; Christian Faulhammer <fauli@gentoo.org> + boost-build-1.41.0.ebuild: + stable x86, security bug 305195 + + 27 Dec 2009; Raúl Porcel <armin76@gentoo.org> + boost-build-1.35.0-r2.ebuild: + alpha/arm/ia64/s390/sh/sparc stable + + 10 Dec 2009; Alexis Ballier <aballier@gentoo.org> + boost-build-1.41.0.ebuild: + keyword ~x86-fbsd + + 02 Dec 2009; Dirkjan Ochtman <djc@gentoo.org> metadata.xml: + Add maintainer-by-proxy. + +*boost-build-1.41.0 (02 Dec 2009) + + 02 Dec 2009; Dirkjan Ochtman <djc@gentoo.org> + +files/boost-1.41-fix-mpich2-detection.patch, +boost-build-1.41.0.ebuild: + Version bump to boost-build-1.41.0. + + 25 Oct 2009; Markus Meier <maekke@gentoo.org> + boost-build-1.35.0-r2.ebuild: + amd64/x86 stable, bug #284686 + + 24 Oct 2009; nixnut <nixnut@gentoo.org> boost-build-1.35.0-r2.ebuild: + ppc stable #284686 + + 24 Oct 2009; Mike Frysinger <vapier@gentoo.org> + boost-build-1.35.0-r2.ebuild, boost-build-1.36.0.ebuild, + boost-build-1.37.0.ebuild, boost-build-1.39.0.ebuild, + boost-build-1.40.0.ebuild: + Add missing `die` check to tarball unpack. + + 23 Oct 2009; Jeroen Roovers <jer@gentoo.org> boost-build-1.35.0-r2.ebuild: + Stable for HPPA (bug #288723). + +*boost-build-1.40.0 (21 Oct 2009) + + 21 Oct 2009; Dirkjan Ochtman <djc@gentoo.org> +boost-build-1.40.0.ebuild, + metadata.xml: + Version bump to 1.40 (add myself to maintainers). + +*boost-build-1.39.0 (16 Jul 2009) + + 16 Jul 2009; Tiziano Müller <dev-zero@gentoo.org> + +boost-build-1.39.0.ebuild: + Version bump (bug #261400). + + 15 May 2009; Raúl Porcel <armin76@gentoo.org> + boost-build-1.35.0-r1.ebuild: + arm/s390/sh stable wrt #245192 + + 14 Apr 2009; Brent Baude <ranger@gentoo.org> boost-build-1.35.0-r1.ebuild: + Marking boost-build-1.35.0-r1 ppc64 for bug 245192 + + 04 Apr 2009; Raúl Porcel <armin76@gentoo.org> + boost-build-1.35.0-r1.ebuild: + ia64 stable wrt #245192 + + 04 Apr 2009; Markus Meier <maekke@gentoo.org> + boost-build-1.35.0-r1.ebuild: + x86 stable, bug #245192 + + 02 Apr 2009; Friedrich Oslage <bluebird@gentoo.org> + boost-build-1.35.0-r1.ebuild: + Stable on sparc, bug #245192 + + 01 Apr 2009; Joseph Jezak <josejx@gentoo.org> + boost-build-1.35.0-r1.ebuild: + Marked ppc stable for bug #245192. + + 29 Mar 2009; Thomas Anderson <gentoofan23@gentoo.org> + boost-build-1.35.0-r1.ebuild: + stable amd64, bug 245192 + + 24 Mar 2009; Ryan Hill <dirtyepic@gentoo.org> boost-build-1.34.1.ebuild, + boost-build-1.35.0-r1.ebuild, boost-build-1.35.0-r2.ebuild, + boost-build-1.36.0.ebuild, boost-build-1.37.0.ebuild: + Fix homepage. Bug #234246. + + 07 Feb 2009; Tobias Klausmann <klausman@gentoo.org> + boost-build-1.35.0-r1.ebuild: + Stable on alpha, bug #245192 + +*boost-build-1.37.0 (16 Dec 2008) +*boost-build-1.36.0 (16 Dec 2008) +*boost-build-1.35.0-r2 (16 Dec 2008) + + 16 Dec 2008; Tiziano Müller <dev-zero@gentoo.org> + +boost-build-1.35.0-r2.ebuild, +boost-build-1.36.0.ebuild, + +boost-build-1.37.0.ebuild: + Version bump. Still p.masked since the new versions are slottable. + +*boost-build-1.35.0-r1 (05 Jun 2008) + + 05 Jun 2008; Tiziano Müller <dev-zero@gentoo.org> + +files/1.35.0-fix_broken_icu_build.patch, -boost-build-1.35.0.ebuild, + +boost-build-1.35.0-r1.ebuild: + Fixed ICU compilation bug + + 05 May 2008; Jeroen Roovers <jer@gentoo.org> boost-build-1.34.1.ebuild, + boost-build-1.35.0.ebuild: + Remove unneeded quotation marks (bug #210029, comment #30). + +*boost-build-1.35.0 (24 Apr 2008) + + 24 Apr 2008; Tiziano Müller <dev-zero@gentoo.org> + +boost-build-1.35.0.ebuild: + Version bump (bug #216037) + + 15 Mar 2008; Tiziano Müller <dev-zero@gentoo.org> + boost-build-1.34.1.ebuild: + Fixed typo in description. + + 14 Feb 2008; Mark Loeser <halcy0n@gentoo.org> boost-build-1.34.1.ebuild: + Fix bug #210029; thanks to Daniel Pielmeier <daniel.pielmeier AT googlemail + DOT com> + + 13 Feb 2008; Tiziano Müller <dev-zero@gentoo.org> + boost-build-1.34.1.ebuild: + Added python USE-flag. Adding LDFLAGS to LIBS to fix bug #209794 (see ebuild + for more info). + + 05 Feb 2008; Samuli Suominen <drac@gentoo.org> boost-build-1.34.1.ebuild: + amd64 stable wrt security #205955 + + 26 Jan 2008; Tobias Scherbaum <dertobi123@gentoo.org> + boost-build-1.34.1.ebuild: + ppc stable, bug #205955 + + 26 Jan 2008; Jeroen Roovers <jer@gentoo.org> boost-build-1.34.1.ebuild: + Stable for HPPA (bug #205955). + + 25 Jan 2008; Markus Rothe <corsair@gentoo.org> boost-build-1.34.1.ebuild: + Stable on ppc64; bug #205955 + + 25 Jan 2008; Raúl Porcel <armin76@gentoo.org> boost-build-1.34.1.ebuild: + alpha/ia64/sparc stable wrt security #205955 + + 24 Jan 2008; Christian Faulhammer <opfer@gentoo.org> + boost-build-1.34.1.ebuild: + stable x86, security bug 205955 + + 20 Jan 2008; Ryan Hill <dirtyepic@gentoo.org> Manifest: + Fix Manifest. + + 24 Dec 2007; Tiziano Müller <dev-zero@gentoo.org> + -boost-build-1.34.0.ebuild: + Dropped old version. + + 26 Sep 2007; Tiziano Müller <dev-zero@gentoo.org> + boost-build-1.34.1.ebuild: + Marked ~arm and ~sh for bug #182196 + +*boost-build-1.34.1 (29 Jul 2007) + + 29 Jul 2007; Tiziano Müller <dev-zero@gentoo.org> + +boost-build-1.34.1.ebuild: + Version bump (bug #186811) + + 23 Jun 2007; Joshua Kinard <kumba@gentoo.org> boost-build-1.34.0.ebuild: + Marked unstable on mips, per #182196. + + 20 Jun 2007; Joseph Jezak <josejx@gentoo.org> boost-build-1.34.0.ebuild: + Marked ~ppc for bug #182196. + + 18 Jun 2007; Raúl Porcel <armin76@gentoo.org> boost-build-1.34.0.ebuild: + Add ~alpha/~ia64 wrt #182196 + + 18 Jun 2007; Markus Rothe <corsair@gentoo.org> boost-build-1.34.0.ebuild: + Added ~ppc64; bug #182196 + + 18 Jun 2007; Jeroen Roovers <jer@gentoo.org> boost-build-1.34.0.ebuild: + Marked ~hppa (bug #182196). + + 16 Jun 2007; Ferris McCormick <fmccor@gentoo.org> + boost-build-1.34.0.ebuild: + Add ~sparc keyword --- part of Bug #182196 --- installs as expected. + + 10 Jun 2007; Ryan Hill <dirtyepic@gentoo.org> boost-build-1.34.0.ebuild: + Boost building boost-build with GCC 4.2, bug #181139. + +*boost-build-1.34.0 (03 Jun 2007) + + 03 Jun 2007; Tiziano Müller <dev-zero@gentoo.org> + -boost-build-1.34_pre20061214.ebuild, +boost-build-1.34.0.ebuild: + Version bump. + +*boost-build-1.34_pre20061214 (18 Dec 2006) + + 18 Dec 2006; Tiziano Müller <dev-zero@gentoo.org> +metadata.xml, + +boost-build-1.34_pre20061214.ebuild: + Initial commit. + diff --git a/dev-util/boost-build/Manifest b/dev-util/boost-build/Manifest new file mode 100644 index 0000000..0c7632c --- /dev/null +++ b/dev-util/boost-build/Manifest @@ -0,0 +1,43 @@ +-----BEGIN PGP SIGNED MESSAGE----- +Hash: SHA256 + +AUX 1.35.0-fix_broken_icu_build.patch 1752 RMD160 0e7ee05c17d76e29abff915e84181361e4095b89 SHA1 273de1fa957091bf3c0d041f54aec9797810f3cf SHA256 71d858236c47b835947d996d3caf0a1de96ace267140d52dd09594db3a96729d +AUX boost-1.41-fix-mpich2-detection.patch 1378 RMD160 fd81c6a03dd8bf2d6afdaf3fa4957ee0ff1f6e10 SHA1 bbe5ba6fb554ab89e5fa4649f8a44ad7cd1dfa80 SHA256 8e1adadb1345ff045930bbd1c6d9d6e4b06462de2939021bf9e3a3fe1c9d6100 +AUX boost-1.42-fix-mpich2-detection.patch 1378 RMD160 fd81c6a03dd8bf2d6afdaf3fa4957ee0ff1f6e10 SHA1 bbe5ba6fb554ab89e5fa4649f8a44ad7cd1dfa80 SHA256 8e1adadb1345ff045930bbd1c6d9d6e4b06462de2939021bf9e3a3fe1c9d6100 +AUX boost-build-1.42-env-whitespace.patch 683 RMD160 a96ff55a09a889c5fba0c898cc7d4c2a6d2ef1a5 SHA1 9fd231fc699813df1d3ba78ae95f5f322166ade7 SHA256 52714f45a54cad8c126d5fca8bd5eacc4d746b29df24aaa9d2c55e3694a6f4aa +AUX boost-build-1.48.0-disable_python_rpath.patch 337 RMD160 33acc4edab1d6cb4f50f88f0c6f68c69bfbe34d9 SHA1 8fd5e5b014d153534eec89da1c2908e1706d984f SHA256 979727bd1aabf6df05d8b06e3ac525bb6d44c2b18c3e4e1331528c4633b7e9df +AUX boost-build-1.48.0-support_dots_in_python-buildid.patch 627 RMD160 9658ae404de38f225e892024bbf0224ed7de9eee SHA1 6be6221afbc54fac2a4371f0e19fa8acd14e4f71 SHA256 e544b0c81a09ad3e56800bef4e7a3e78b5b27ee7377e7f4fc66d1aecd955ae0a +DIST boost_1_34_1.tar.bz2 12986931 RMD160 303327ff852bc19dd7a94657fdef3c56f5882e06 SHA1 b771271d5cbd3bdb0f119dd66dfd36bad7a66866 SHA256 0f866c75b025a4f1340117a106595cc0675f48ba1e5a9b5c221ec7f19e96ec4c +DIST boost_1_35_0.tar.bz2 23416747 RMD160 89dc46b7841cd288b5fb6f4b9a1ac7309786dc14 SHA1 80d1fe7b0c45541e2af7628295b18f2af996de16 SHA256 f8bf7368a22ccf2e2cf77048ab2129744be4c03f8488c76ad31c0aa229b280da +DIST boost_1_37_0.tar.bz2 29435646 RMD160 3c4cf7eb97a8fb126e564ba529ed9edec8765185 SHA1 c0d0cf9ad8d954507824aed51a3e93e6a9da1d99 SHA256 d52ef49f70b1b9addc4e0d1a3a2a1966227f0d173c3301bac3e6d399eeac5472 +DIST boost_1_39_0.tar.bz2 29408537 RMD160 4962256b48fa8563bf373b8bed97cc8655206a51 SHA1 6af42f74ab24ccc51589a025593bad298c8adde8 SHA256 44785eae8c6cce61a29a8a51f9b737e57b34d66baa7c0bcd4af188832b8018fd +DIST boost_1_40_0.tar.bz2 32068759 RMD160 dabcc7442b73048095aa3037917ea0713782781f SHA1 9dbaa06ce1d99ce310011c2eaf816ecb003b3096 SHA256 36cf4a239b587067a4923fdf6e290525a14c3af29829524fa73f3dec6841530c +DIST boost_1_41_0.tar.bz2 33348161 RMD160 a604ef5a6f6f5bf50be59206c8534258ab431aea SHA1 31134e28866b90c39ca4a903c263e036bb25550c SHA256 1ef94e6749eaf13318284b4f629be063544c7015b45e38113b975ac1945cc726 +DIST boost_1_42_0.tar.bz2 33426755 RMD160 90cea6aaa35f22b97e6eb3f5879ca9fe21098349 SHA1 3ce3bb1a1bed504635287017f9e628597b409e7b SHA256 4b1eb95bd250ce15ac66435d6167f225b072b0d3a7eb72477a31847a9ca9e609 +DIST boost_1_45_0.tar.bz2 39330184 RMD160 1402cb49e0d680268109ef1bf16aea9bc4a127b0 SHA1 eb7424ef99df4e38af7431e38ff9849651b8aaf5 SHA256 55ed3ec51d5687e8224c988e22bef215dacce04e037d9f689569a80c4377a6d5 +DIST boost_1_46_1.tar.bz2 42001335 RMD160 bb43b39f7c4b683b80bafa3042b95e65a242d9c3 SHA1 3ca6e173ec805e5126868d8a03618e587aa26aef SHA256 e1dfbf42b16e5015c46b98e9899c423ca4d04469cbeee05e43ea19236416d883 +DIST boost_1_47_0.tar.bz2 45952657 RMD160 511144eb5ade340115971c372a3c849bd55181f1 SHA1 6e3eb548b9d955c0bc6f71c51042b713b678136a SHA256 815a5d9faac4dbd523fbcf3fe1065e443c0bbf43427c44aa423422c6ec4c2e31 +DIST boost_1_48_0.tar.bz2 48236989 RMD160 e006121ae5cac37aa419ac5bbf59e090e6ca7f70 SHA1 27aced5086e96c6f7b2b684bda2bd515e115da35 SHA256 1bf254b2d69393ccd57a3cdd30a2f80318a005de8883a0792ed2f5e2598e5ada +DIST boost_1_49_0.tar.bz2 48499961 RMD160 3504c6f27c63ab52182c822d45d020fa30179abc SHA1 26a52840e9d12f829e3008589abf0a925ce88524 SHA256 dd748a7f5507a7e7af74f452e1c52a64e651ed1f7263fce438a06641d2180d3c +EBUILD boost-build-1.34.1.ebuild 2449 RMD160 2c66c3c1b52cb15aea3ce8ee39d860a8d10faf29 SHA1 1a01b722f78e7e75add539e9bf2c5c0a3206c78f SHA256 0d12d3be2859e96f988e4279dc72c42bf420262673d9b6bf5344896089bd7770 +EBUILD boost-build-1.35.0-r1.ebuild 2779 RMD160 93fca7f1c241a01afcabd63fa6195c1be86b1775 SHA1 d48b0626273f6abb32aaccf4e66e21ec9dc5b5e3 SHA256 a02f12355f9d84cf7e47cffcd6001838b1747eadca2608cab9469490b3117801 +EBUILD boost-build-1.35.0-r2.ebuild 3134 RMD160 b9c8335cffeb8881ee2ccabc44ed03c328d489ab SHA1 2ce79d1cf84f85454c6e56c30baa748222ff8c1c SHA256 f324e074f6c01381a39b5521ec558e994565ebfbdc1575eae73d6e490f13ce73 +EBUILD boost-build-1.37.0.ebuild 3115 RMD160 848a75ae7c614e58ae212494140e61db80ef4ba3 SHA1 411862adf745eaa8b5b6f83e0ea5000363771987 SHA256 cc4b9e938dabbcc8b941bdac549e5f4bfb7d28d33f40e0cbdf2d1b6742b47adb +EBUILD boost-build-1.39.0.ebuild 3200 RMD160 bd2c408aab985f7af268c1777fc8614ac7c0646b SHA1 b1e9e251fae02736f491d651aa22ebf6c72a832f SHA256 64aea9788d166844187918c01b4c80725b4e8fdef9129649d69569472b2bd576 +EBUILD boost-build-1.40.0.ebuild 3200 RMD160 640ec5948d4d4c5ce166b2c92cb504691832f3bb SHA1 1759bac7c70e1c6e0d3197d50f197342027d04f4 SHA256 320dfc12eacea3946c309056242aa2e721bd34715829f533536a904470d0d948 +EBUILD boost-build-1.41.0.ebuild 3258 RMD160 0a738f43d1770fb817e868340a1e64f1da4725a2 SHA1 3b9102fcec4d109ee2f688006f462829be45b0d1 SHA256 286b32e7d7061b19780a8fea535ece191ab58c2322b4bb198404522cfc3d7f47 +EBUILD boost-build-1.42.0.ebuild 3248 RMD160 8ec1c03eb28bf4b550aec7e6a013a1facb30be2b SHA1 1e3023e75a6a44133fa1d529ffede218063e6ae9 SHA256 a3645740879ce87633398f34fb582ea05695962e45bea85860e5c9fc6ced3f43 +EBUILD boost-build-1.45.0.ebuild 3309 RMD160 70f308ca0f6322d6cdd2f95746be7ce0abc610f9 SHA1 511990fc07e64b1941227747c43feedf68d53712 SHA256 889fc96586966fd52db2bfa1cfcf296dda766bf0fc996f0a643f69da07874c06 +EBUILD boost-build-1.46.1.ebuild 3307 RMD160 33e17b065a02770234ef521f74ff7e4bd02414b7 SHA1 0846856a149658610c2cbfccd4ea3887bdd750ce SHA256 86ada1e18fbf568d0479374f53fc0dd2d257066dc85651154a515b402aa38a49 +EBUILD boost-build-1.47.0.ebuild 3455 RMD160 bbcd8be5e3f5494ce19351fd49aac44f14b9b005 SHA1 6b7dc37a2ee68c5c68c26aed4d1fc4b4fb91c998 SHA256 201bcd7ba558e4e24a437eb83c881b0ca802706b7bb2699bc083b87d2b02ec49 +EBUILD boost-build-1.48.0-r1.ebuild 3430 RMD160 900546b9ee7641d4f5c791b7467f8a2dae92788b SHA1 6aafdbcdf4cc7dd73855d34d283fea81cdd052c8 SHA256 324663a6c08652d6cb5f9d936d83e8a58adb6f74a153477ca5c1044bf151cb1e +EBUILD boost-build-1.49.0.ebuild 3442 RMD160 d9d724548d6b4f1ea3c8183c251f66fdaf8cf668 SHA1 6432898a02c8f66bf60af8102631985104eb4ed4 SHA256 e7931535d30eff4eae3714221e85477d793049d5725a82d542f95a1aca638cf2 +MISC ChangeLog 11368 RMD160 1646f66529ef1b28efdfdbc114dab605637977d2 SHA1 508fdc7a795eefcff285f58155d76bd049eb61c9 SHA256 78915cc8ce7dff5f782227db4487beec58f45aeb4b1ab9394bc086134a210b5b +MISC metadata.xml 467 RMD160 46a5b92ef812d514cce62b4a7d6644597c137bf9 SHA1 c47d4a412061b3fe75a2ac875542bc6f1ea4d269 SHA256 45d1630f3fe0286a9ea6cb8cb04ec73ae7f4b7fd52f413e423fce4c436c23f6a +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0.17 (GNU/Linux) + +iF4EAREIAAYFAk94/DsACgkQC77qH+pIQ6RDywD/bum2KaW75m/83C7h4GiCA/Mb +WFIS21v4Z4L75MIpv6gA/3twdGCDfVyVPRjLXJT97klYydoBaNjKaaESHzfrMGNP +=63bb +-----END PGP SIGNATURE----- diff --git a/dev-util/boost-build/boost-build-1.34.1.ebuild b/dev-util/boost-build/boost-build-1.34.1.ebuild new file mode 100644 index 0000000..483496d --- /dev/null +++ b/dev-util/boost-build/boost-build-1.34.1.ebuild @@ -0,0 +1,80 @@ +# Copyright 1999-2010 Gentoo Foundation +# Distributed under the terms of the GNU General Public License v2 +# $Header: /var/cvsroot/gentoo-x86/dev-util/boost-build/boost-build-1.34.1.ebuild,v 1.17 2010/08/14 06:35:54 dirtyepic Exp $ + +inherit flag-o-matic toolchain-funcs versionator + +MY_PV=$(replace_all_version_separators _) + +DESCRIPTION="A system for large project software construction, which is simple to use and powerful." +HOMEPAGE="http://www.boost.org/doc/tools/build/index.html" +SRC_URI="mirror://sourceforge/boost/boost_${MY_PV}.tar.bz2" + +LICENSE="Boost-1.0" +SLOT="0" +KEYWORDS="alpha amd64 arm hppa ia64 ~mips ppc ppc64 s390 sh sparc x86" +IUSE="python" + +DEPEND="!<dev-libs/boost-1.34.0 + python? ( dev-lang/python )" +RDEPEND="" + +S=${WORKDIR}/boost_${MY_PV}/tools + +src_unpack() { + unpack ${A} + + # Remove stripping option + cd "${S}/jam/src" + sed -i \ + -e 's/-s\b//' \ + build.jam || die "sed failed" + + # This patch allows us to fully control optimization + # and stripping flags when bjam is used as build-system + # We simply extend the optimization and debug-symbols feature + # with empty dummies called 'none' + cd "${S}/build/v2" + sed -i \ + -e 's/\(feature optimization : off speed space\)/\1 none/' \ + -e 's/\(feature debug-symbols : on off\)/\1 none/' \ + tools/builtin.jam || die "sed failed" +} + +src_compile() { + cd jam/src + local toolset + + if [[ ${CHOST} == *-darwin* ]] ; then + toolset=darwin + else + # Using boost's generic toolset here, which respects CC and CFLAGS + toolset=cc + fi + + append-flags -fno-strict-aliasing + + # The build.jam file for building bjam using a bootstrapped jam0 ignores + # the LDFLAGS env var (bug #209794). We have now two options: + # a) change the cc-target definition in build.jam to include separate compile + # and link targets to make it use the LDFLAGS var, or + # b) a simple dirty workaround by injecting the LDFLAGS in the LIBS env var + # (which should not be set by us). + if [[ -z "${LDFLAGS}" ]] ; then + CC=$(tc-getCC) ./build.sh ${toolset} $(use_with python) \ + || die "building bjam failed" + else + LDFLAGS=$(echo ${LDFLAGS}) # 293652 + LIBS=${LDFLAGS} CC=$(tc-getCC) ./build.sh ${toolset} \ + $(use_with python) || die "building bjam failed" + fi +} + +src_install() { + dobin jam/src/bin.*/bjam || die + + cd "${S}/build/v2" + insinto /usr/share/boost-build + doins -r boost-build.jam bootstrap.jam build-system.jam site-config.jam user-config.jam \ + build kernel options tools util || die +} diff --git a/dev-util/boost-build/boost-build-1.35.0-r1.ebuild b/dev-util/boost-build/boost-build-1.35.0-r1.ebuild new file mode 100644 index 0000000..0437625 --- /dev/null +++ b/dev-util/boost-build/boost-build-1.35.0-r1.ebuild @@ -0,0 +1,95 @@ +# Copyright 1999-2010 Gentoo Foundation +# Distributed under the terms of the GNU General Public License v2 +# $Header: /var/cvsroot/gentoo-x86/dev-util/boost-build/boost-build-1.35.0-r1.ebuild,v 1.11 2010/08/14 06:35:54 dirtyepic Exp $ + +inherit flag-o-matic toolchain-funcs versionator + +MY_PV=$(replace_all_version_separators _) + +DESCRIPTION="A system for large project software construction, which is simple to use and powerful." +HOMEPAGE="http://www.boost.org/doc/tools/build/index.html" +SRC_URI="mirror://sourceforge/boost/boost_${MY_PV}.tar.bz2" +LICENSE="Boost-1.0" +SLOT="0" +KEYWORDS="alpha amd64 arm ~hppa ia64 ~mips ppc ppc64 s390 sh sparc x86" +IUSE="examples python" + +DEPEND="!<dev-libs/boost-1.34.0 + python? ( dev-lang/python )" +RDEPEND="${DEPEND}" + +S=${WORKDIR}/boost_${MY_PV}/tools + +src_unpack() { + unpack ${A} + cd "${S}" + + epatch "${FILESDIR}/${PV}-fix_broken_icu_build.patch" + + # Remove stripping option + cd "${S}/jam/src" + sed -i \ + -e 's/-s\b//' \ + build.jam || die "sed failed" + + # This patch allows us to fully control optimization + # and stripping flags when bjam is used as build-system + # We simply extend the optimization and debug-symbols feature + # with empty dummies called 'none' + cd "${S}/build/v2" + sed -i \ + -e 's/\(off speed space\)/\1 none/' \ + -e 's/\(debug-symbols : on off\)/\1 none/' \ + tools/builtin.jam || die "sed failed" +} + +src_compile() { + cd jam/src + local toolset + + if [[ ${CHOST} == *-darwin* ]] ; then + toolset=darwin + else + # Using boost's generic toolset here, which respects CC and CFLAGS + toolset=cc + fi + + append-flags -fno-strict-aliasing + + # The build.jam file for building bjam using a bootstrapped jam0 ignores + # the LDFLAGS env var (bug #209794). We have now two options: + # a) change the cc-target definition in build.jam to include separate compile + # and link targets to make it use the LDFLAGS var, or + # b) a simple dirty workaround by injecting the LDFLAGS in the LIBS env var + # (which should not be set by us). + if [[ -z "${LDFLAGS}" ]] ; then + CC=$(tc-getCC) ./build.sh ${toolset} $(use_with python) \ + || die "building bjam failed" + else + LDFLAGS=$(echo ${LDFLAGS}) # 293652 + LIBS=${LDFLAGS} CC=$(tc-getCC) ./build.sh ${toolset} \ + $(use_with python) || die "building bjam failed" + fi +} + +src_install() { + dobin jam/src/bin.*/bjam + + cd "${S}/build/v2" + insinto /usr/share/boost-build + doins -r boost-build.jam bootstrap.jam build-system.jam site-config.jam user-config.jam \ + build kernel options tools util || die + + dodoc doc/userman.pdf changes.txt hacking.txt release_procedure.txt \ + notes/build_dir_option.txt notes/relative_source_paths.txt + + if use examples ; then + insinto /usr/share/doc/${PF} + doins -r examples + fi +} + +src_test() { + cd jam/test + ./test.sh || die "tests failed" +} diff --git a/dev-util/boost-build/boost-build-1.35.0-r2.ebuild b/dev-util/boost-build/boost-build-1.35.0-r2.ebuild new file mode 100644 index 0000000..e433c26 --- /dev/null +++ b/dev-util/boost-build/boost-build-1.35.0-r2.ebuild @@ -0,0 +1,106 @@ +# Copyright 1999-2010 Gentoo Foundation +# Distributed under the terms of the GNU General Public License v2 +# $Header: /var/cvsroot/gentoo-x86/dev-util/boost-build/boost-build-1.35.0-r2.ebuild,v 1.10 2010/08/14 06:35:54 dirtyepic Exp $ + +EAPI="2" + +inherit eutils flag-o-matic toolchain-funcs versionator + +MY_PV=$(replace_all_version_separators _) +MAJOR_PV="$(replace_all_version_separators _ $(get_version_component_range 1-2))" + +DESCRIPTION="A system for large project software construction, which is simple to use and powerful." +HOMEPAGE="http://www.boost.org/doc/tools/build/index.html" +SRC_URI="mirror://sourceforge/boost/boost_${MY_PV}.tar.bz2" +LICENSE="Boost-1.0" +SLOT="0" +KEYWORDS="alpha amd64 arm hppa ia64 ~mips ppc ~ppc64 s390 sh sparc x86" +IUSE="examples python" + +DEPEND="!<dev-libs/boost-1.34.0 + python? ( dev-lang/python )" +RDEPEND="${DEPEND}" + +S="${WORKDIR}/boost_${MY_PV}/tools" + +src_unpack() { + tar xjpf "${DISTDIR}/${A}" boost_${MY_PV}/tools/{jam,build/v2} || die +} + +src_prepare() { + epatch "${FILESDIR}/${PV}-fix_broken_icu_build.patch" + + # Remove stripping option + cd "${S}/jam/src" + sed -i -e 's|-s\b||' \ + build.jam || die "sed failed" + + # Force regeneration + rm jambase.c + + # This patch allows us to fully control optimization + # and stripping flags when bjam is used as build-system + # We simply extend the optimization and debug-symbols feature + # with empty dummies called 'none' + cd "${S}/build/v2" + sed -i \ + -e 's/\(off speed space\)/\1 none/' \ + -e 's/\(debug-symbols : on off\)/\1 none/' \ + tools/builtin.jam || die "sed failed" +} + +src_compile() { + cd jam/src + local toolset + + if [[ ${CHOST} == *-darwin* ]] ; then + toolset=darwin + else + # Using boost's generic toolset here, which respects CC and CFLAGS + toolset=cc + fi + + append-flags -fno-strict-aliasing + + # For slotting + sed -i \ + -e "s|/usr/share/boost-build|/usr/share/boost-build-${MAJOR_PV}|" \ + Jambase || die "sed failed" + + # The build.jam file for building bjam using a bootstrapped jam0 ignores + # the LDFLAGS env var (bug #209794). We have now two options: + # a) change the cc-target definition in build.jam to include separate compile + # and link targets to make it use the LDFLAGS var, or + # b) a simple dirty workaround by injecting the LDFLAGS in the LIBS env var + # (which should not be set by us). + if [[ -z "${LDFLAGS}" ]] ; then + CC=$(tc-getCC) ./build.sh ${toolset} $(use_with python) \ + || die "building bjam failed" + else + LDFLAGS=$(echo ${LDFLAGS}) # 293652 + LIBS=${LDFLAGS} CC=$(tc-getCC) ./build.sh ${toolset} \ + $(use_with python) || die "building bjam failed" + fi +} + +src_install() { + newbin jam/src/bin.*/bjam bjam-${MAJOR_PV} + + cd "${S}/build/v2" + insinto /usr/share/boost-build-${MAJOR_PV} + doins -r boost-build.jam bootstrap.jam build-system.jam site-config.jam user-config.jam \ + build kernel options tools util || die + + dodoc doc/userman.pdf changes.txt hacking.txt release_procedure.txt \ + notes/build_dir_option.txt notes/relative_source_paths.txt + + if use examples ; then + insinto /usr/share/doc/${PF} + doins -r example + fi +} + +src_test() { + cd jam/test + ./test.sh || die "tests failed" +} diff --git a/dev-util/boost-build/boost-build-1.37.0.ebuild b/dev-util/boost-build/boost-build-1.37.0.ebuild new file mode 100644 index 0000000..6120eb3 --- /dev/null +++ b/dev-util/boost-build/boost-build-1.37.0.ebuild @@ -0,0 +1,105 @@ +# Copyright 1999-2010 Gentoo Foundation +# Distributed under the terms of the GNU General Public License v2 +# $Header: /var/cvsroot/gentoo-x86/dev-util/boost-build/boost-build-1.37.0.ebuild,v 1.4 2010/08/14 06:35:54 dirtyepic Exp $ + +EAPI="2" + +inherit flag-o-matic toolchain-funcs versionator + +MY_PV=$(replace_all_version_separators _) +MAJOR_PV="$(replace_all_version_separators _ $(get_version_component_range 1-2))" + +DESCRIPTION="A system for large project software construction, which is simple to use and powerful." +HOMEPAGE="http://www.boost.org/doc/tools/build/index.html" +SRC_URI="mirror://sourceforge/boost/boost_${MY_PV}.tar.bz2" +LICENSE="Boost-1.0" +SLOT="1.37" +KEYWORDS="~alpha ~amd64 ~arm ~hppa ~ia64 ~mips ~ppc ~ppc64 ~s390 ~sh ~sparc ~x86" +IUSE="examples python" + +DEPEND="!<dev-libs/boost-1.34.0 + !<=dev-util/boost-build-1.35.0-r1 + python? ( dev-lang/python )" +RDEPEND="${DEPEND}" + +S="${WORKDIR}/boost_${MY_PV}/tools" + +src_unpack() { + tar xjpf "${DISTDIR}/${A}" boost_${MY_PV}/tools/{jam,build/v2} || die +} + +src_prepare() { + # Remove stripping option + cd "${S}/jam/src" + sed -i -e 's|-s\b||' \ + build.jam || die "sed failed" + + # Force regeneration + rm jambase.c + + # This patch allows us to fully control optimization + # and stripping flags when bjam is used as build-system + # We simply extend the optimization and debug-symbols feature + # with empty dummies called 'none' + cd "${S}/build/v2" + sed -i \ + -e 's/\(off speed space\)/\1 none/' \ + -e 's/\(debug-symbols : on off\)/\1 none/' \ + tools/builtin.jam || die "sed failed" +} + +src_compile() { + cd jam/src + local toolset + + if [[ ${CHOST} == *-darwin* ]] ; then + toolset=darwin + else + # Using boost's generic toolset here, which respects CC and CFLAGS + toolset=cc + fi + + append-flags -fno-strict-aliasing + + # For slotting + sed -i \ + -e "s|/usr/share/boost-build|/usr/share/boost-build-${MAJOR_PV}|" \ + Jambase || die "sed failed" + + # The build.jam file for building bjam using a bootstrapped jam0 ignores + # the LDFLAGS env var (bug #209794). We have now two options: + # a) change the cc-target definition in build.jam to include separate compile + # and link targets to make it use the LDFLAGS var, or + # b) a simple dirty workaround by injecting the LDFLAGS in the LIBS env var + # (which should not be set by us). + if [[ -z "${LDFLAGS}" ]] ; then + CC=$(tc-getCC) ./build.sh ${toolset} $(use_with python) \ + || die "building bjam failed" + else + LDFLAGS=$(echo ${LDFLAGS}) # 293652 + LIBS=${LDFLAGS} CC=$(tc-getCC) ./build.sh ${toolset} \ + $(use_with python) || die "building bjam failed" + fi +} + +src_install() { + newbin jam/src/bin.*/bjam bjam-${MAJOR_PV} + + cd "${S}/build/v2" + insinto /usr/share/boost-build-${MAJOR_PV} + doins -r boost-build.jam bootstrap.jam build-system.jam site-config.jam user-config.jam \ + build kernel options tools util || die + + dodoc doc/userman.pdf changes.txt hacking.txt release_procedure.txt \ + notes/build_dir_option.txt notes/relative_source_paths.txt + + if use examples ; then + insinto /usr/share/doc/${PF} + doins -r example + fi +} + +src_test() { + cd jam/test + ./test.sh || die "tests failed" +} diff --git a/dev-util/boost-build/boost-build-1.39.0.ebuild b/dev-util/boost-build/boost-build-1.39.0.ebuild new file mode 100644 index 0000000..447741c --- /dev/null +++ b/dev-util/boost-build/boost-build-1.39.0.ebuild @@ -0,0 +1,107 @@ +# Copyright 1999-2010 Gentoo Foundation +# Distributed under the terms of the GNU General Public License v2 +# $Header: /var/cvsroot/gentoo-x86/dev-util/boost-build/boost-build-1.39.0.ebuild,v 1.3 2010/08/14 06:35:54 dirtyepic Exp $ + +EAPI="2" + +inherit eutils flag-o-matic toolchain-funcs versionator + +MY_PV=$(replace_all_version_separators _) +MAJOR_PV="$(replace_all_version_separators _ $(get_version_component_range 1-2))" + +DESCRIPTION="A system for large project software construction, which is simple to use and powerful." +HOMEPAGE="http://www.boost.org/doc/tools/build/index.html" +SRC_URI="mirror://sourceforge/boost/boost_${MY_PV}.tar.bz2" +LICENSE="Boost-1.0" +SLOT="$(get_version_component_range 1-2)" +KEYWORDS="~alpha ~amd64 ~arm ~hppa ~ia64 ~mips ~ppc ~ppc64 ~s390 ~sh ~sparc ~x86" +IUSE="examples python" + +DEPEND="!<dev-libs/boost-1.34.0 + !<=dev-util/boost-build-1.35.0-r1 + python? ( dev-lang/python )" +RDEPEND="${DEPEND}" + +S="${WORKDIR}/boost_${MY_PV}/tools" + +src_unpack() { + tar xjpf "${DISTDIR}/${A}" boost_${MY_PV}/tools/{jam,build/v2} || die +} + +src_prepare() { + epatch "${FILESDIR}/${PN}-1.42-env-whitespace.patch" # 293652 + + # Remove stripping option + cd "${S}/jam/src" + sed -i -e 's|-s\b||' \ + build.jam || die "sed failed" + + # Force regeneration + rm jambase.c + + # This patch allows us to fully control optimization + # and stripping flags when bjam is used as build-system + # We simply extend the optimization and debug-symbols feature + # with empty dummies called 'none' + cd "${S}/build/v2" + sed -i \ + -e 's/\(off speed space\)/\1 none/' \ + -e 's/\(debug-symbols : on off\)/\1 none/' \ + tools/builtin.jam || die "sed failed" +} + +src_compile() { + cd jam/src + local toolset + + if [[ ${CHOST} == *-darwin* ]] ; then + toolset=darwin + else + # Using boost's generic toolset here, which respects CC and CFLAGS + toolset=cc + fi + + append-flags -fno-strict-aliasing + + # For slotting + sed -i \ + -e "s|/usr/share/boost-build|/usr/share/boost-build-${MAJOR_PV}|" \ + Jambase || die "sed failed" + + # The build.jam file for building bjam using a bootstrapped jam0 ignores + # the LDFLAGS env var (bug #209794). We have now two options: + # a) change the cc-target definition in build.jam to include separate compile + # and link targets to make it use the LDFLAGS var, or + # b) a simple dirty workaround by injecting the LDFLAGS in the LIBS env var + # (which should not be set by us). + if [[ -z "${LDFLAGS}" ]] ; then + CC=$(tc-getCC) ./build.sh ${toolset} $(use_with python) \ + || die "building bjam failed" + else + LDFLAGS=$(echo ${LDFLAGS}) # 293652 + LIBS=${LDFLAGS} CC=$(tc-getCC) ./build.sh ${toolset} \ + $(use_with python) || die "building bjam failed" + fi +} + +src_install() { + newbin jam/src/bin.*/bjam bjam-${MAJOR_PV} + + cd "${S}/build/v2" + insinto /usr/share/boost-build-${MAJOR_PV} + doins -r boost-build.jam bootstrap.jam build-system.jam site-config.jam user-config.jam \ + build kernel options tools util || die + + dodoc changes.txt hacking.txt release_procedure.txt \ + notes/build_dir_option.txt notes/relative_source_paths.txt + + if use examples ; then + insinto /usr/share/doc/${PF} + doins -r example + fi +} + +src_test() { + cd jam/test + ./test.sh || die "tests failed" +} diff --git a/dev-util/boost-build/boost-build-1.40.0.ebuild b/dev-util/boost-build/boost-build-1.40.0.ebuild new file mode 100644 index 0000000..5abf0b3 --- /dev/null +++ b/dev-util/boost-build/boost-build-1.40.0.ebuild @@ -0,0 +1,107 @@ +# Copyright 1999-2010 Gentoo Foundation +# Distributed under the terms of the GNU General Public License v2 +# $Header: /var/cvsroot/gentoo-x86/dev-util/boost-build/boost-build-1.40.0.ebuild,v 1.3 2010/08/14 06:35:53 dirtyepic Exp $ + +EAPI="2" + +inherit eutils flag-o-matic toolchain-funcs versionator + +MY_PV=$(replace_all_version_separators _) +MAJOR_PV="$(replace_all_version_separators _ $(get_version_component_range 1-2))" + +DESCRIPTION="A system for large project software construction, which is simple to use and powerful." +HOMEPAGE="http://www.boost.org/doc/tools/build/index.html" +SRC_URI="mirror://sourceforge/boost/boost_${MY_PV}.tar.bz2" +LICENSE="Boost-1.0" +SLOT="$(get_version_component_range 1-2)" +KEYWORDS="~alpha ~amd64 ~arm ~hppa ~ia64 ~mips ~ppc ~ppc64 ~s390 ~sh ~sparc ~x86" +IUSE="examples python" + +DEPEND="!<dev-libs/boost-1.34.0 + !<=dev-util/boost-build-1.35.0-r1 + python? ( dev-lang/python )" +RDEPEND="${DEPEND}" + +S="${WORKDIR}/boost_${MY_PV}/tools" + +src_unpack() { + tar xjpf "${DISTDIR}/${A}" boost_${MY_PV}/tools/{jam,build/v2} || die +} + +src_prepare() { + epatch "${FILESDIR}/${PN}-1.42-env-whitespace.patch" # 293652 + + # Remove stripping option + cd "${S}/jam/src" + sed -i -e 's|-s\b||' \ + build.jam || die "sed failed" + + # Force regeneration + rm jambase.c + + # This patch allows us to fully control optimization + # and stripping flags when bjam is used as build-system + # We simply extend the optimization and debug-symbols feature + # with empty dummies called 'none' + cd "${S}/build/v2" + sed -i \ + -e 's/\(off speed space\)/\1 none/' \ + -e 's/\(debug-symbols : on off\)/\1 none/' \ + tools/builtin.jam || die "sed failed" +} + +src_compile() { + cd jam/src + local toolset + + if [[ ${CHOST} == *-darwin* ]] ; then + toolset=darwin + else + # Using boost's generic toolset here, which respects CC and CFLAGS + toolset=cc + fi + + append-flags -fno-strict-aliasing + + # For slotting + sed -i \ + -e "s|/usr/share/boost-build|/usr/share/boost-build-${MAJOR_PV}|" \ + Jambase || die "sed failed" + + # The build.jam file for building bjam using a bootstrapped jam0 ignores + # the LDFLAGS env var (bug #209794). We have now two options: + # a) change the cc-target definition in build.jam to include separate compile + # and link targets to make it use the LDFLAGS var, or + # b) a simple dirty workaround by injecting the LDFLAGS in the LIBS env var + # (which should not be set by us). + if [[ -z "${LDFLAGS}" ]] ; then + CC=$(tc-getCC) ./build.sh ${toolset} $(use_with python) \ + || die "building bjam failed" + else + LDFLAGS=$(echo ${LDFLAGS}) # 293652 + LIBS=${LDFLAGS} CC=$(tc-getCC) ./build.sh ${toolset} \ + $(use_with python) || die "building bjam failed" + fi +} + +src_install() { + newbin jam/src/bin.*/bjam bjam-${MAJOR_PV} + + cd "${S}/build/v2" + insinto /usr/share/boost-build-${MAJOR_PV} + doins -r boost-build.jam bootstrap.jam build-system.jam site-config.jam user-config.jam \ + build kernel options tools util || die + + dodoc changes.txt hacking.txt release_procedure.txt \ + notes/build_dir_option.txt notes/relative_source_paths.txt + + if use examples ; then + insinto /usr/share/doc/${PF} + doins -r example + fi +} + +src_test() { + cd jam/test + ./test.sh || die "tests failed" +} diff --git a/dev-util/boost-build/boost-build-1.41.0.ebuild b/dev-util/boost-build/boost-build-1.41.0.ebuild new file mode 100644 index 0000000..75dbe85 --- /dev/null +++ b/dev-util/boost-build/boost-build-1.41.0.ebuild @@ -0,0 +1,108 @@ +# Copyright 1999-2010 Gentoo Foundation +# Distributed under the terms of the GNU General Public License v2 +# $Header: /var/cvsroot/gentoo-x86/dev-util/boost-build/boost-build-1.41.0.ebuild,v 1.10 2010/09/19 17:52:31 armin76 Exp $ + +EAPI="2" + +inherit eutils flag-o-matic toolchain-funcs versionator + +MY_PV=$(replace_all_version_separators _) +MAJOR_PV="$(replace_all_version_separators _ $(get_version_component_range 1-2))" + +DESCRIPTION="A system for large project software construction, which is simple to use and powerful." +HOMEPAGE="http://www.boost.org/doc/tools/build/index.html" +SRC_URI="mirror://sourceforge/boost/boost_${MY_PV}.tar.bz2" +LICENSE="Boost-1.0" +SLOT="$(get_version_component_range 1-2)" +KEYWORDS="alpha amd64 arm hppa ia64 ~mips ppc ppc64 s390 sh sparc x86 ~x86-fbsd" +IUSE="examples python" + +DEPEND="!<dev-libs/boost-1.34.0 + !<=dev-util/boost-build-1.35.0-r1 + python? ( dev-lang/python )" +RDEPEND="${DEPEND}" + +S="${WORKDIR}/boost_${MY_PV}/tools" + +src_unpack() { + tar xjpf "${DISTDIR}/${A}" boost_${MY_PV}/tools/{jam,build/v2} || die +} + +src_prepare() { + epatch "${FILESDIR}/boost-1.41-fix-mpich2-detection.patch" + epatch "${FILESDIR}/${PN}-1.42-env-whitespace.patch" # 293652 + + # Remove stripping option + cd "${S}/jam/src" + sed -i -e 's|-s\b||' \ + build.jam || die "sed failed" + + # Force regeneration + rm jambase.c + + # This patch allows us to fully control optimization + # and stripping flags when bjam is used as build-system + # We simply extend the optimization and debug-symbols feature + # with empty dummies called 'none' + cd "${S}/build/v2" + sed -i \ + -e 's/\(off speed space\)/\1 none/' \ + -e 's/\(debug-symbols : on off\)/\1 none/' \ + tools/builtin.jam || die "sed failed" +} + +src_compile() { + cd jam/src + local toolset + + if [[ ${CHOST} == *-darwin* ]] ; then + toolset=darwin + else + # Using boost's generic toolset here, which respects CC and CFLAGS + toolset=cc + fi + + append-flags -fno-strict-aliasing + + # For slotting + sed -i \ + -e "s|/usr/share/boost-build|/usr/share/boost-build-${MAJOR_PV}|" \ + Jambase || die "sed failed" + + # The build.jam file for building bjam using a bootstrapped jam0 ignores + # the LDFLAGS env var (bug #209794). We have now two options: + # a) change the cc-target definition in build.jam to include separate compile + # and link targets to make it use the LDFLAGS var, or + # b) a simple dirty workaround by injecting the LDFLAGS in the LIBS env var + # (which should not be set by us). + if [[ -z "${LDFLAGS}" ]] ; then + CC=$(tc-getCC) ./build.sh ${toolset} $(use_with python) \ + || die "building bjam failed" + else + LDFLAGS=$(echo ${LDFLAGS}) # 293652 + LIBS=${LDFLAGS} CC=$(tc-getCC) ./build.sh ${toolset} \ + $(use_with python) || die "building bjam failed" + fi +} + +src_install() { + newbin jam/src/bin.*/bjam bjam-${MAJOR_PV} + + cd "${S}/build/v2" + insinto /usr/share/boost-build-${MAJOR_PV} + doins -r boost-build.jam bootstrap.jam build-system.jam site-config.jam user-config.jam \ + build kernel options tools util || die + + dodoc changes.txt hacking.txt release_procedure.txt \ + notes/build_dir_option.txt notes/relative_source_paths.txt + + if use examples ; then + insinto /usr/share/doc/${PF} + doins -r example + fi +} + +src_test() { + cd jam/test + ./test.sh || die "tests failed" +} diff --git a/dev-util/boost-build/boost-build-1.42.0.ebuild b/dev-util/boost-build/boost-build-1.42.0.ebuild new file mode 100644 index 0000000..0f69d87 --- /dev/null +++ b/dev-util/boost-build/boost-build-1.42.0.ebuild @@ -0,0 +1,108 @@ +# Copyright 1999-2011 Gentoo Foundation +# Distributed under the terms of the GNU General Public License v2 +# $Header: /var/cvsroot/gentoo-x86/dev-util/boost-build/boost-build-1.42.0.ebuild,v 1.11 2011/04/16 11:29:07 armin76 Exp $ + +EAPI="2" + +inherit eutils flag-o-matic toolchain-funcs versionator + +MY_PV=$(replace_all_version_separators _) +MAJOR_PV="$(replace_all_version_separators _ $(get_version_component_range 1-2))" + +DESCRIPTION="A system for large project software construction, which is simple to use and powerful." +HOMEPAGE="http://www.boost.org/doc/tools/build/index.html" +SRC_URI="mirror://sourceforge/boost/boost_${MY_PV}.tar.bz2" +LICENSE="Boost-1.0" +SLOT="$(get_version_component_range 1-2)" +KEYWORDS="alpha amd64 arm hppa ia64 ~mips ppc ppc64 s390 sh sparc x86" +IUSE="examples python" + +DEPEND="!<dev-libs/boost-1.34.0 + !<=dev-util/boost-build-1.35.0-r1 + python? ( dev-lang/python )" +RDEPEND="${DEPEND}" + +S="${WORKDIR}/boost_${MY_PV}/tools" + +src_unpack() { + tar xjpf "${DISTDIR}/${A}" boost_${MY_PV}/tools/{jam,build/v2} || die +} + +src_prepare() { + epatch "${FILESDIR}/boost-1.42-fix-mpich2-detection.patch" + epatch "${FILESDIR}/${PN}-1.42-env-whitespace.patch" # 293652 + + # Remove stripping option + cd "${S}/jam/src" + sed -i -e 's|-s\b||' \ + build.jam || die "sed failed" + + # Force regeneration + rm jambase.c + + # This patch allows us to fully control optimization + # and stripping flags when bjam is used as build-system + # We simply extend the optimization and debug-symbols feature + # with empty dummies called 'none' + cd "${S}/build/v2" + sed -i \ + -e 's/\(off speed space\)/\1 none/' \ + -e 's/\(debug-symbols : on off\)/\1 none/' \ + tools/builtin.jam || die "sed failed" +} + +src_compile() { + cd jam/src + local toolset + + if [[ ${CHOST} == *-darwin* ]] ; then + toolset=darwin + else + # Using boost's generic toolset here, which respects CC and CFLAGS + toolset=cc + fi + + append-flags -fno-strict-aliasing + + # For slotting + sed -i \ + -e "s|/usr/share/boost-build|/usr/share/boost-build-${MAJOR_PV}|" \ + Jambase || die "sed failed" + + # The build.jam file for building bjam using a bootstrapped jam0 ignores + # the LDFLAGS env var (bug #209794). We have now two options: + # a) change the cc-target definition in build.jam to include separate compile + # and link targets to make it use the LDFLAGS var, or + # b) a simple dirty workaround by injecting the LDFLAGS in the LIBS env var + # (which should not be set by us). + if [[ -z "${LDFLAGS}" ]] ; then + CC=$(tc-getCC) ./build.sh ${toolset} $(use_with python) \ + || die "building bjam failed" + else + LDFLAGS=$(echo ${LDFLAGS}) # 293652 + LIBS=${LDFLAGS} CC=$(tc-getCC) ./build.sh ${toolset} \ + $(use_with python) || die "building bjam failed" + fi +} + +src_install() { + newbin jam/src/bin.*/bjam bjam-${MAJOR_PV} + + cd "${S}/build/v2" + insinto /usr/share/boost-build-${MAJOR_PV} + doins -r boost-build.jam bootstrap.jam build-system.jam site-config.jam user-config.jam \ + build kernel options tools util || die + + dodoc changes.txt hacking.txt release_procedure.txt \ + notes/build_dir_option.txt notes/relative_source_paths.txt + + if use examples ; then + insinto /usr/share/doc/${PF} + doins -r example + fi +} + +src_test() { + cd jam/test + ./test.sh || die "tests failed" +} diff --git a/dev-util/boost-build/boost-build-1.45.0.ebuild b/dev-util/boost-build/boost-build-1.45.0.ebuild new file mode 100644 index 0000000..6c9c2a4 --- /dev/null +++ b/dev-util/boost-build/boost-build-1.45.0.ebuild @@ -0,0 +1,111 @@ +# Copyright 1999-2011 Gentoo Foundation +# Distributed under the terms of the GNU General Public License v2 +# $Header: /var/cvsroot/gentoo-x86/dev-util/boost-build/boost-build-1.45.0.ebuild,v 1.1 2011/01/06 14:00:10 dev-zero Exp $ + +EAPI="2" + +inherit eutils flag-o-matic toolchain-funcs versionator + +MY_PV=$(replace_all_version_separators _) +MAJOR_PV="$(replace_all_version_separators _ $(get_version_component_range 1-2))" + +DESCRIPTION="A system for large project software construction, which is simple to use and powerful." +HOMEPAGE="http://www.boost.org/doc/tools/build/index.html" +SRC_URI="mirror://sourceforge/boost/boost_${MY_PV}.tar.bz2" +LICENSE="Boost-1.0" +SLOT="$(get_version_component_range 1-2)" +KEYWORDS="~alpha ~amd64 ~arm ~hppa ~ia64 ~mips ~ppc ~ppc64 ~s390 ~sh ~sparc ~x86" +IUSE="examples python" + +DEPEND="!<dev-libs/boost-1.34.0 + !<=dev-util/boost-build-1.35.0-r1 + python? ( dev-lang/python )" +RDEPEND="${DEPEND}" + +S="${WORKDIR}/boost_${MY_PV}/tools/build/v2" + +src_unpack() { + tar xjpf "${DISTDIR}/${A}" boost_${MY_PV}/tools/build/v2 || die "unpacking tar failed" +} + +src_prepare() { + # TODO: + # epatch "${FILESDIR}/boost-1.42-fix-mpich2-detection.patch" + + cd "${S}/engine" + epatch "${FILESDIR}/${PN}-1.42-env-whitespace.patch" # 293652 + + # Remove stripping option + cd "${S}/engine/src" + sed -i -e 's|-s\b||' \ + build.jam || die "sed failed" + + # Force regeneration + rm jambase.c + + # This patch allows us to fully control optimization + # and stripping flags when bjam is used as build-system + # We simply extend the optimization and debug-symbols feature + # with empty dummies called 'none' + cd "${S}" + sed -i \ + -e 's/\(off speed space\)/\1 none/' \ + -e 's/\(debug-symbols : on off\)/\1 none/' \ + tools/builtin.jam || die "sed failed" +} + +src_compile() { + cd engine/src + local toolset + + if [[ ${CHOST} == *-darwin* ]] ; then + toolset=darwin + else + # Using boost's generic toolset here, which respects CC and CFLAGS + toolset=cc + fi + + append-flags -fno-strict-aliasing + + # For slotting + sed -i \ + -e "s|/usr/share/boost-build|/usr/share/boost-build-${MAJOR_PV}|" \ + Jambase || die "sed failed" + + # The build.jam file for building bjam using a bootstrapped jam0 ignores + # the LDFLAGS env var (bug #209794). We have now two options: + # a) change the cc-target definition in build.jam to include separate compile + # and link targets to make it use the LDFLAGS var, or + # b) a simple dirty workaround by injecting the LDFLAGS in the LIBS env var + # (which should not be set by us). + if [[ -z "${LDFLAGS}" ]] ; then + CC=$(tc-getCC) ./build.sh ${toolset} $(use_with python) \ + || die "building bjam failed" + else + LDFLAGS=$(echo ${LDFLAGS}) # 293652 + LIBS=${LDFLAGS} CC=$(tc-getCC) ./build.sh ${toolset} \ + $(use_with python) || die "building bjam failed" + fi +} + +src_install() { + newbin engine/src/bin.*/bjam bjam-${MAJOR_PV} + + cd "${S}" + insinto /usr/share/boost-build-${MAJOR_PV} + doins -r boost-build.jam bootstrap.jam build-system.jam site-config.jam user-config.jam \ + build kernel options tools util || die + + dodoc changes.txt hacking.txt release_procedure.txt \ + notes/build_dir_option.txt notes/relative_source_paths.txt + + if use examples ; then + insinto /usr/share/doc/${PF} + doins -r example + fi +} + +src_test() { + cd engine/test + ./test.sh || die "tests failed" +} diff --git a/dev-util/boost-build/boost-build-1.46.1.ebuild b/dev-util/boost-build/boost-build-1.46.1.ebuild new file mode 100644 index 0000000..287a5b9 --- /dev/null +++ b/dev-util/boost-build/boost-build-1.46.1.ebuild @@ -0,0 +1,111 @@ +# Copyright 1999-2011 Gentoo Foundation +# Distributed under the terms of the GNU General Public License v2 +# $Header: /var/cvsroot/gentoo-x86/dev-util/boost-build/boost-build-1.46.1.ebuild,v 1.9 2011/12/28 19:22:06 halcy0n Exp $ + +EAPI="2" + +inherit eutils flag-o-matic toolchain-funcs versionator + +MY_PV=$(replace_all_version_separators _) +MAJOR_PV="$(replace_all_version_separators _ $(get_version_component_range 1-2))" + +DESCRIPTION="A system for large project software construction, which is simple to use and powerful." +HOMEPAGE="http://www.boost.org/doc/tools/build/index.html" +SRC_URI="mirror://sourceforge/boost/boost_${MY_PV}.tar.bz2" +LICENSE="Boost-1.0" +SLOT="$(get_version_component_range 1-2)" +KEYWORDS="alpha amd64 arm hppa ia64 ~mips ppc ppc64 s390 sh sparc x86 ~x86-fbsd" +IUSE="examples python" + +DEPEND="!<dev-libs/boost-1.34.0 + !<=dev-util/boost-build-1.35.0-r1 + python? ( dev-lang/python )" +RDEPEND="${DEPEND}" + +S="${WORKDIR}/boost_${MY_PV}/tools/build/v2" + +src_unpack() { + tar xjpf "${DISTDIR}/${A}" boost_${MY_PV}/tools/build/v2 || die "unpacking tar failed" +} + +src_prepare() { + # TODO: + # epatch "${FILESDIR}/boost-1.42-fix-mpich2-detection.patch" + + cd "${S}/engine" + epatch "${FILESDIR}/${PN}-1.42-env-whitespace.patch" # 293652 + + # Remove stripping option + cd "${S}/engine/src" + sed -i -e 's|-s\b||' \ + build.jam || die "sed failed" + + # Force regeneration + rm jambase.c + + # This patch allows us to fully control optimization + # and stripping flags when bjam is used as build-system + # We simply extend the optimization and debug-symbols feature + # with empty dummies called 'none' + cd "${S}" + sed -i \ + -e 's/\(off speed space\)/\1 none/' \ + -e 's/\(debug-symbols : on off\)/\1 none/' \ + tools/builtin.jam || die "sed failed" +} + +src_compile() { + cd engine/src + local toolset + + if [[ ${CHOST} == *-darwin* ]] ; then + toolset=darwin + else + # Using boost's generic toolset here, which respects CC and CFLAGS + toolset=cc + fi + + append-flags -fno-strict-aliasing + + # For slotting + sed -i \ + -e "s|/usr/share/boost-build|/usr/share/boost-build-${MAJOR_PV}|" \ + Jambase || die "sed failed" + + # The build.jam file for building bjam using a bootstrapped jam0 ignores + # the LDFLAGS env var (bug #209794). We have now two options: + # a) change the cc-target definition in build.jam to include separate compile + # and link targets to make it use the LDFLAGS var, or + # b) a simple dirty workaround by injecting the LDFLAGS in the LIBS env var + # (which should not be set by us). + if [[ -z "${LDFLAGS}" ]] ; then + CC=$(tc-getCC) ./build.sh ${toolset} $(use_with python) \ + || die "building bjam failed" + else + LDFLAGS=$(echo ${LDFLAGS}) # 293652 + LIBS=${LDFLAGS} CC=$(tc-getCC) ./build.sh ${toolset} \ + $(use_with python) || die "building bjam failed" + fi +} + +src_install() { + newbin engine/src/bin.*/bjam bjam-${MAJOR_PV} + + cd "${S}" + insinto /usr/share/boost-build-${MAJOR_PV} + doins -r boost-build.jam bootstrap.jam build-system.jam site-config.jam user-config.jam \ + build kernel options tools util || die + + dodoc changes.txt hacking.txt release_procedure.txt \ + notes/build_dir_option.txt notes/relative_source_paths.txt + + if use examples ; then + insinto /usr/share/doc/${PF} + doins -r example + fi +} + +src_test() { + cd engine/test + ./test.sh || die "tests failed" +} diff --git a/dev-util/boost-build/boost-build-1.46.1.ebuild.new b/dev-util/boost-build/boost-build-1.46.1.ebuild.new new file mode 120000 index 0000000..95b1162 --- /dev/null +++ b/dev-util/boost-build/boost-build-1.46.1.ebuild.new @@ -0,0 +1 @@ +/gentoo/usr/portage/dev-util/boost-build/boost-build-1.46.1.ebuild
\ No newline at end of file diff --git a/dev-util/boost-build/boost-build-1.47.0.ebuild b/dev-util/boost-build/boost-build-1.47.0.ebuild new file mode 100644 index 0000000..322571c --- /dev/null +++ b/dev-util/boost-build/boost-build-1.47.0.ebuild @@ -0,0 +1,114 @@ +# Copyright 1999-2011 Gentoo Foundation +# Distributed under the terms of the GNU General Public License v2 +# $Header: /var/cvsroot/gentoo-x86/dev-util/boost-build/boost-build-1.47.0.ebuild,v 1.1 2011/09/26 11:01:51 hwoarang Exp $ + +EAPI="2" + +inherit eutils flag-o-matic toolchain-funcs versionator + +MY_PV=$(replace_all_version_separators _) +MAJOR_PV="$(replace_all_version_separators _ $(get_version_component_range 1-2))" + +DESCRIPTION="A system for large project software construction, which is simple to use and powerful." +HOMEPAGE="http://www.boost.org/doc/tools/build/index.html" +SRC_URI="mirror://sourceforge/boost/boost_${MY_PV}.tar.bz2" +LICENSE="Boost-1.0" +SLOT="$(get_version_component_range 1-2)" +KEYWORDS="~alpha ~amd64 ~arm ~hppa ~ia64 ~mips ~ppc ~ppc64 ~s390 ~sh ~sparc ~x86 ~x86-fbsd" +IUSE="examples python" + +DEPEND="!<dev-libs/boost-1.34.0 + !<=dev-util/boost-build-1.35.0-r1 + python? ( dev-lang/python )" +RDEPEND="${DEPEND}" + +S="${WORKDIR}/boost_${MY_PV}/tools/build/v2" + +src_unpack() { + tar xjpf "${DISTDIR}/${A}" boost_${MY_PV}/tools/build/v2 || die "unpacking tar failed" +} + +src_prepare() { + # TODO: + # epatch "${FILESDIR}/boost-1.42-fix-mpich2-detection.patch" + + cd "${S}/engine" + epatch "${FILESDIR}/${PN}-1.42-env-whitespace.patch" # 293652 + + # Remove stripping option + cd "${S}/engine" + sed -i -e 's|-s\b||' \ + build.jam || die "sed failed" + + # Force regeneration + rm jambase.c || die + + # This patch allows us to fully control optimization + # and stripping flags when bjam is used as build-system + # We simply extend the optimization and debug-symbols feature + # with empty dummies called 'none' + cd "${S}" + sed -i \ + -e 's/\(off speed space\)/\1 none/' \ + -e 's/\(debug-symbols : on off\)/\1 none/' \ + tools/builtin.jam || die "sed failed" +} + +src_compile() { + cd engine + local toolset + + if [[ ${CHOST} == *-darwin* ]] ; then + toolset=darwin + else + # Using boost's generic toolset here, which respects CC and CFLAGS + toolset=cc + fi + + # For slotting + sed -i \ + -e "s|/usr/share/boost-build|/usr/share/boost-build-${MAJOR_PV}|" \ + Jambase || die "sed failed" + + # The build.jam file for building bjam using a bootstrapped jam0 ignores + # the LDFLAGS env var (bug #209794). We have now two options: + # a) change the cc-target definition in build.jam to include separate compile + # and link targets to make it use the LDFLAGS var, or + # b) a simple dirty workaround by injecting the LDFLAGS in the LIBS env var + # (which should not be set by us). + if [[ -z "${LDFLAGS}" ]] ; then + CC=$(tc-getCC) ./build.sh ${toolset} $(use_with python) \ + || die "building bjam failed" + else + LDFLAGS=$(echo ${LDFLAGS}) # 293652 + LIBS=${LDFLAGS} CC=$(tc-getCC) ./build.sh ${toolset} \ + $(use_with python) || die "building bjam failed" + fi +} + +src_install() { + newbin engine/bin.*/bjam bjam-${MAJOR_PV} + newbin engine/bin.*/b2 b2-${MAJOR_PV} + + cd "${S}" + insinto /usr/share/boost-build-${MAJOR_PV} + doins -r boost-build.jam bootstrap.jam build-system.jam site-config.jam user-config.jam \ + build kernel options tools util || die + + dodoc changes.txt hacking.txt release_procedure.txt \ + notes/build_dir_option.txt notes/relative_source_paths.txt + + if use examples ; then + insinto /usr/share/doc/${PF} + doins -r example + fi +} + +src_test() { + cd test/engine + + FIXME: Replace the ls call with the proper way of doing this. + + BJAM_BIN=$(ls ../../engine/bin.*/b2) + ${BJAM_BIN} -f test.jam "-sBJAM=${BJAM_BIN}" || die "tests failed" +} diff --git a/dev-util/boost-build/boost-build-1.48.0-r1.ebuild b/dev-util/boost-build/boost-build-1.48.0-r1.ebuild new file mode 100644 index 0000000..8815aa3 --- /dev/null +++ b/dev-util/boost-build/boost-build-1.48.0-r1.ebuild @@ -0,0 +1,112 @@ +# Copyright 1999-2012 Gentoo Foundation +# Distributed under the terms of the GNU General Public License v2 +# $Header: /var/cvsroot/gentoo-x86/dev-util/boost-build/boost-build-1.48.0-r1.ebuild,v 1.1 2012/01/19 22:40:07 hwoarang Exp $ + +EAPI="4" +PYTHON_DEPEND="python? *" + +inherit eutils flag-o-matic python toolchain-funcs versionator + +MY_PV=$(replace_all_version_separators _) +MAJOR_PV="$(replace_all_version_separators _ $(get_version_component_range 1-2))" + +DESCRIPTION="A system for large project software construction, which is simple to use and powerful." +HOMEPAGE="http://www.boost.org/doc/tools/build/index.html" +SRC_URI="mirror://sourceforge/boost/boost_${MY_PV}.tar.bz2" + +LICENSE="Boost-1.0" +SLOT="$(get_version_component_range 1-2)" +KEYWORDS="~alpha ~amd64 ~arm ~hppa ~ia64 ~mips ~ppc ~ppc64 ~s390 ~sh ~sparc ~x86 ~x86-fbsd" +IUSE="examples python" + +DEPEND="!<dev-libs/boost-1.34.0 + !<=dev-util/boost-build-1.35.0-r1" +RDEPEND="${DEPEND}" + +S="${WORKDIR}/boost_${MY_PV}/tools/build/v2" + +src_unpack() { + tar xjpf "${DISTDIR}/${A}" boost_${MY_PV}/tools/build/v2 || die "unpacking tar failed" +} + +src_prepare() { + epatch "${FILESDIR}/${P}-support_dots_in_python-buildid.patch" + epatch "${FILESDIR}/${P}-disable_python_rpath.patch" + + # Remove stripping option + cd "${S}/engine" + sed -i -e 's|-s\b||' \ + build.jam || die "sed failed" + + # Force regeneration + rm jambase.c || die + + # This patch allows us to fully control optimization + # and stripping flags when bjam is used as build-system + # We simply extend the optimization and debug-symbols feature + # with empty dummies called 'none' + cd "${S}" + sed -i \ + -e 's/\(off speed space\)/\1 none/' \ + -e 's/\(debug-symbols : on off\)/\1 none/' \ + tools/builtin.jam || die "sed failed" +} + +src_compile() { + cd engine + local toolset + + if [[ ${CHOST} == *-darwin* ]] ; then + toolset=darwin + else + # Using boost's generic toolset here, which respects CC and CFLAGS + toolset=cc + fi + + # For slotting + sed -i \ + -e "s|/usr/share/boost-build|/usr/share/boost-build-${MAJOR_PV}|" \ + Jambase || die "sed failed" + + # The build.jam file for building bjam using a bootstrapped jam0 ignores + # the LDFLAGS env var (bug #209794). We have now two options: + # a) change the cc-target definition in build.jam to include separate compile + # and link targets to make it use the LDFLAGS var, or + # b) a simple dirty workaround by injecting the LDFLAGS in the LIBS env var + # (which should not be set by us). + if [[ -z "${LDFLAGS}" ]] ; then + CC=$(tc-getCC) ./build.sh ${toolset} $(use_with python) \ + || die "building bjam failed" + else + LDFLAGS=$(echo ${LDFLAGS}) # 293652 + LIBS=${LDFLAGS} CC=$(tc-getCC) ./build.sh ${toolset} \ + $(use_with python) || die "building bjam failed" + fi +} + +src_install() { + newbin engine/bin.*/bjam bjam-${MAJOR_PV} + newbin engine/bin.*/b2 b2-${MAJOR_PV} + + cd "${S}" + insinto /usr/share/boost-build-${MAJOR_PV} + doins -r boost-build.jam bootstrap.jam build-system.jam site-config.jam user-config.jam \ + build kernel options tools util || die + + dodoc changes.txt hacking.txt release_procedure.txt \ + notes/build_dir_option.txt notes/relative_source_paths.txt + + if use examples ; then + insinto /usr/share/doc/${PF} + doins -r example + fi +} + +src_test() { + cd test/engine + + # FIXME: Replace the ls call with the proper way of doing this. + + BJAM_BIN=$(ls ../../engine/bin.*/b2) + ${BJAM_BIN} -f test.jam "-sBJAM=${BJAM_BIN}" || die "tests failed" +} diff --git a/dev-util/boost-build/boost-build-1.49.0.ebuild b/dev-util/boost-build/boost-build-1.49.0.ebuild new file mode 100644 index 0000000..8ab1617 --- /dev/null +++ b/dev-util/boost-build/boost-build-1.49.0.ebuild @@ -0,0 +1,112 @@ +# Copyright 1999-2012 Gentoo Foundation +# Distributed under the terms of the GNU General Public License v2 +# $Header: /var/cvsroot/gentoo-x86/dev-util/boost-build/boost-build-1.49.0.ebuild,v 1.1 2012/04/02 00:00:51 floppym Exp $ + +EAPI="4" +PYTHON_DEPEND="python? *" + +inherit eutils flag-o-matic python toolchain-funcs versionator + +MY_PV=$(replace_all_version_separators _) +MAJOR_PV="$(replace_all_version_separators _ $(get_version_component_range 1-2))" + +DESCRIPTION="A system for large project software construction, which is simple to use and powerful." +HOMEPAGE="http://www.boost.org/doc/tools/build/index.html" +SRC_URI="mirror://sourceforge/boost/boost_${MY_PV}.tar.bz2" + +LICENSE="Boost-1.0" +SLOT="$(get_version_component_range 1-2)" +KEYWORDS="~alpha ~amd64 ~arm ~hppa ~ia64 ~mips ~ppc ~ppc64 ~s390 ~sh ~sparc ~x86 ~x86-fbsd" +IUSE="examples python" + +DEPEND="!<dev-libs/boost-1.34.0 + !<=dev-util/boost-build-1.35.0-r1" +RDEPEND="${DEPEND}" + +S="${WORKDIR}/boost_${MY_PV}/tools/build/v2" + +src_unpack() { + tar xjpf "${DISTDIR}/${A}" boost_${MY_PV}/tools/build/v2 || die "unpacking tar failed" +} + +src_prepare() { + epatch "${FILESDIR}/${PN}-1.48.0-support_dots_in_python-buildid.patch" + epatch "${FILESDIR}/${PN}-1.48.0-disable_python_rpath.patch" + + # Remove stripping option + cd "${S}/engine" + sed -i -e 's|-s\b||' \ + build.jam || die "sed failed" + + # Force regeneration + rm jambase.c || die + + # This patch allows us to fully control optimization + # and stripping flags when bjam is used as build-system + # We simply extend the optimization and debug-symbols feature + # with empty dummies called 'none' + cd "${S}" + sed -i \ + -e 's/\(off speed space\)/\1 none/' \ + -e 's/\(debug-symbols : on off\)/\1 none/' \ + tools/builtin.jam || die "sed failed" +} + +src_compile() { + cd engine + local toolset + + if [[ ${CHOST} == *-darwin* ]] ; then + toolset=darwin + else + # Using boost's generic toolset here, which respects CC and CFLAGS + toolset=cc + fi + + # For slotting + sed -i \ + -e "s|/usr/share/boost-build|/usr/share/boost-build-${MAJOR_PV}|" \ + Jambase || die "sed failed" + + # The build.jam file for building bjam using a bootstrapped jam0 ignores + # the LDFLAGS env var (bug #209794). We have now two options: + # a) change the cc-target definition in build.jam to include separate compile + # and link targets to make it use the LDFLAGS var, or + # b) a simple dirty workaround by injecting the LDFLAGS in the LIBS env var + # (which should not be set by us). + if [[ -z "${LDFLAGS}" ]] ; then + CC=$(tc-getCC) ./build.sh ${toolset} $(use_with python) \ + || die "building bjam failed" + else + LDFLAGS=$(echo ${LDFLAGS}) # 293652 + LIBS=${LDFLAGS} CC=$(tc-getCC) ./build.sh ${toolset} \ + $(use_with python) || die "building bjam failed" + fi +} + +src_install() { + newbin engine/bin.*/bjam bjam-${MAJOR_PV} + newbin engine/bin.*/b2 b2-${MAJOR_PV} + + cd "${S}" + insinto /usr/share/boost-build-${MAJOR_PV} + doins -r boost-build.jam bootstrap.jam build-system.jam site-config.jam user-config.jam \ + build kernel options tools util || die + + dodoc changes.txt hacking.txt release_procedure.txt \ + notes/build_dir_option.txt notes/relative_source_paths.txt + + if use examples ; then + insinto /usr/share/doc/${PF} + doins -r example + fi +} + +src_test() { + cd test/engine + + # FIXME: Replace the ls call with the proper way of doing this. + + BJAM_BIN=$(ls ../../engine/bin.*/b2) + ${BJAM_BIN} -f test.jam "-sBJAM=${BJAM_BIN}" || die "tests failed" +} diff --git a/dev-util/boost-build/files/1.35.0-fix_broken_icu_build.patch b/dev-util/boost-build/files/1.35.0-fix_broken_icu_build.patch new file mode 100644 index 0000000..b461105 --- /dev/null +++ b/dev-util/boost-build/files/1.35.0-fix_broken_icu_build.patch @@ -0,0 +1,33 @@ +--- trunk/tools/build/v2/build/targets.jam (revision 45072) ++++ trunk/tools/build/v2/build/targets.jam (revision 45245) +@@ -1170,5 +1170,5 @@ + ECHO [ targets.indent ] "Building target '$(fn)'" ; + targets.increase-indent ; +- ECHO [ targets.indent ] "Build request: " [ $(property-set).raw ] ; ++ ECHO [ targets.indent ] "Build request: " $(property-set) [ $(property-set).raw ] ; + local cf = [ build-system.command-line-free-features ] ; + ECHO [ targets.indent ] "Command line free features: " [ $(cf).raw ] ; +@@ -1275,5 +1275,14 @@ + # case we don't want any diagnostic. In the former case, we need + # diagnostics. FIXME +- self.generated.$(property-set) = $(rproperties) ; ++ ++ # If this target fails to build, add <build>no to properties ++ # to cause any parent target to fail to build. Except that it ++ # - does not work now, since we check for <build>no only in ++ # common properties, but not in properties that came from ++ # dependencies ++ # - it's not clear if that's a good idea anyway. The alias ++ # target, for example, should not fail to build if a dependency ++ # fails. ++ self.generated.$(property-set) = [ property-set.create <build>no ] ; + } + } +@@ -1283,4 +1292,7 @@ + { + ECHO [ targets.indent ] "Already built" ; ++ local ur = $(self.generated.$(property-set)) ; ++ ur = $(ur[0]) ; ++ ECHO [ targets.indent ] " Usage requirements " [ $(ur).raw ] ; + } + } diff --git a/dev-util/boost-build/files/boost-1.41-fix-mpich2-detection.patch b/dev-util/boost-build/files/boost-1.41-fix-mpich2-detection.patch new file mode 100644 index 0000000..d3bd646 --- /dev/null +++ b/dev-util/boost-build/files/boost-1.41-fix-mpich2-detection.patch @@ -0,0 +1,35 @@ +Index: tools/build/v2/tools/mpi.jam +=================================================================== +--- tools/build/v2/tools/mpi.jam (revision 57744) ++++ tools/build/v2/tools/mpi.jam (working copy) +@@ -156,14 +156,27 @@ + # into a feature. + local match = [ MATCH "^(-.)(.*)" : $(cmdline) ] ; + local matched ; +- if $(match) && $(match[2]) { ++ if $(match) && $(match[2]) { + local prefix = $(match[1]) ; + if $(feature_kinds$(prefix)) { + local name = $(feature_kinds$(prefix)) ; + local add = [ add_feature $(prefix) $(name) $(cmdline) ] ; + + if $(add) { +- result += $(add[1]) ; ++ ++ if $(add[1]) = <find-shared-library>pthread ++ { ++ # Uhm. It's not really nice that this MPI implementation ++ # uses -lpthread as opposed to -pthread. We do want to ++ # set <threading>multi, instead of -lpthread. ++ result += "<threading>multi" ; ++ MPI_EXTRA_REQUIREMENTS += "<threading>multi" ; ++ } ++ else ++ { ++ result += $(add[1]) ; ++ } ++ + cmdline = $(add[2]) ; + matched = yes ; + } + diff --git a/dev-util/boost-build/files/boost-1.42-fix-mpich2-detection.patch b/dev-util/boost-build/files/boost-1.42-fix-mpich2-detection.patch new file mode 100644 index 0000000..d3bd646 --- /dev/null +++ b/dev-util/boost-build/files/boost-1.42-fix-mpich2-detection.patch @@ -0,0 +1,35 @@ +Index: tools/build/v2/tools/mpi.jam +=================================================================== +--- tools/build/v2/tools/mpi.jam (revision 57744) ++++ tools/build/v2/tools/mpi.jam (working copy) +@@ -156,14 +156,27 @@ + # into a feature. + local match = [ MATCH "^(-.)(.*)" : $(cmdline) ] ; + local matched ; +- if $(match) && $(match[2]) { ++ if $(match) && $(match[2]) { + local prefix = $(match[1]) ; + if $(feature_kinds$(prefix)) { + local name = $(feature_kinds$(prefix)) ; + local add = [ add_feature $(prefix) $(name) $(cmdline) ] ; + + if $(add) { +- result += $(add[1]) ; ++ ++ if $(add[1]) = <find-shared-library>pthread ++ { ++ # Uhm. It's not really nice that this MPI implementation ++ # uses -lpthread as opposed to -pthread. We do want to ++ # set <threading>multi, instead of -lpthread. ++ result += "<threading>multi" ; ++ MPI_EXTRA_REQUIREMENTS += "<threading>multi" ; ++ } ++ else ++ { ++ result += $(add[1]) ; ++ } ++ + cmdline = $(add[2]) ; + matched = yes ; + } + diff --git a/dev-util/boost-build/files/boost-build-1.42-env-whitespace.patch b/dev-util/boost-build/files/boost-build-1.42-env-whitespace.patch new file mode 100644 index 0000000..681de7a --- /dev/null +++ b/dev-util/boost-build/files/boost-build-1.42-env-whitespace.patch @@ -0,0 +1,25 @@ +diff --git a/tools/jam/src/build.jam b/tools/jam/src/build.jam +index e30e854..7b397a3 100644 +--- a/tools/jam/src/build.jam ++++ b/tools/jam/src/build.jam +@@ -2,6 +2,20 @@ + #~ Distributed under the Boost Software License, Version 1.0. + #~ (See accompanying file LICENSE_1_0.txt or http://www.boost.org/LICENSE_1_0.txt) + ++# Clean env vars of any "extra" empty values. ++for local v in ARGV CC CFLAGS ++{ ++ local values ; ++ for local x in $($(v)) ++ { ++ if $(x) != "" ++ { ++ values += $(x) ; ++ } ++ } ++ $(v) = $(values) ; ++} ++ + # Platform related specifics. + if $(NT) { rule .path { return "$(<:J=\\)" ; } ./ = "/" ; } + else if $(OS2) { rule .path { return "$(<:J=\\)" ; } ./ = "/" ; } diff --git a/dev-util/boost-build/files/boost-build-1.48.0-disable_python_rpath.patch b/dev-util/boost-build/files/boost-build-1.48.0-disable_python_rpath.patch new file mode 100644 index 0000000..8b88b43 --- /dev/null +++ b/dev-util/boost-build/files/boost-build-1.48.0-disable_python_rpath.patch @@ -0,0 +1,11 @@ +--- tools/python.jam ++++ tools/python.jam +@@ -961,7 +961,7 @@ + # linux). + : $(usage-requirements) + <testing.launcher>$(set-PYTHONPATH) +- <library-path>$(libraries) <dll-path>$(dll-path) <library>python.lib ++ <library-path>$(libraries) <library>python.lib + ; + } + diff --git a/dev-util/boost-build/files/boost-build-1.48.0-support_dots_in_python-buildid.patch b/dev-util/boost-build/files/boost-build-1.48.0-support_dots_in_python-buildid.patch new file mode 100644 index 0000000..b3bee03 --- /dev/null +++ b/dev-util/boost-build/files/boost-build-1.48.0-support_dots_in_python-buildid.patch @@ -0,0 +1,19 @@ +--- tools/common.jam ++++ tools/common.jam +@@ -759,7 +759,15 @@ + switch $(f:G) + { + case <base> : +- result += $(name:B) ; ++ local matched = [ MATCH "^(boost.*python)-.*" : $(name) ] ; ++ if $(matched) = boost_python || $(matched) = boost_mpi_python ++ { ++ result += $(name) ; ++ } ++ else ++ { ++ result += $(name:B) ; ++ } + + case <toolset> : + result += [ join-tag $(f:G=) : [ toolset-tag $(name) : $(type) : diff --git a/dev-util/boost-build/metadata.xml b/dev-util/boost-build/metadata.xml new file mode 100644 index 0000000..5b304b7 --- /dev/null +++ b/dev-util/boost-build/metadata.xml @@ -0,0 +1,17 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd"> +<pkgmetadata> + <herd>cpp</herd> + <maintainer> + <email>dev-zero@gentoo.org</email> + <name>Tiziano Müller</name> + </maintainer> + <maintainer> + <email>SebastianLuther@gmx.de</email> + <name>Sebastian Luther</name> + </maintainer> + <maintainer> + <email>hwoarang@gentoo.org</email> + <name>Markos Chandras</name> + </maintainer> +</pkgmetadata> |