Summary: | dev-libs/boost-1.34.1-r2 build fails | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Randy Johnson <theraptor2005> |
Component: | [OLD] Library | Assignee: | Tiziano Müller (RETIRED) <dev-zero> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge --info
replacement patch |
Description
Randy Johnson
2008-01-25 13:48:22 UTC
emerge --info please. Created attachment 141768 [details]
emerge --info
Sorry about that. emerge --info attached.
Any package specific USE flags? It fails in all combinations of USE flags I tried, including none selected. Noteably, I tried various combinations of icu, tools, and pyste. (I don't actually need any enabled) It appears that the patch 07_all_1.34.1-CVE-2008-0171_and_0172.patch07_all_1.34.1-CVE-2008-0171_and_0172.patch07_all_1.34.1-CVE-2008-0171_and_0172.patch applies incorrectly. When I manually apply the patch to a fresh untar, I get: patching file boost/regex/v4/basic_regex_parser.hpp Hunk #1 succeeded at 785 with fuzz 2. Hunk #2 succeeded at 1871 with fuzz 2. Hunk #3 succeeded at 1880 with fuzz 2. patching file libs/regex/test/regress/test_perl_ex.cpp Hunk #1 succeeded at 122 with fuzz 2. Looking at the appropriate lines shows code in obviously wrong places (such as a case outside of a switch. When I can get to it, I'll attempt to manually "patch" the files by hand, and post a modified patch if it works Created attachment 141804 [details, diff]
replacement patch
The attached replacement patch applies cleanly, and boost emerges correctly with it.
Hmm, can you please give me the output of this: 'grep ^PATCHSET_VERSION /usr/portage/dev-libs/boost/boost-1.34.1-r2.ebuild' ? Thanks. My fault. Grep output shows PATCHSET_VERSION="${PV}-2", where the latest ebuild has PATCHSET_VERSION="${PV}-3". This compiles properly. Sorry for wasting time. Comment http://bugs.gentoo.org/show_bug.cgi?id=205955#c13 fixes this *** This bug has been marked as a duplicate of bug 205955 *** |