Summary: | dev-libs/boost-1.52.0-r5[-threads] fails to build | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Thomas Beutin <tb> |
Component: | [OLD] Library | Assignee: | Julian Ospald <hasufell> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | bircoph, cpp+disabled, f_philipp, hasufell |
Priority: | Normal | Keywords: | STABLE |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://svn.boost.org/trac/boost/ticket/7105 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 525286 | ||
Bug Blocks: | |||
Attachments: |
/var/tmp/portage/dev-libs/boost-1.52.0-r5/temp/build.log
/media/GFZ650GB/gentoo/tmp/portage/dev-libs/boost-1.52.0-r6/temp/build.log boost-1.52.0-non-threaded.patch for USE="-threads" |
Description
Thomas Beutin
2013-02-20 06:05:43 UTC
Please attach the entire build log to this bug report. Created attachment 339504 [details]
/var/tmp/portage/dev-libs/boost-1.52.0-r5/temp/build.log
build log as requesting in #1
actually the build.log is from another system (with all of the portage stuff in standard locations) but the error is the same. the interesting part of the build.log was already given in the bug description. This might be fixed with boost-1.52.0-r6 — please try that and report, thanks! (In reply to comment #4) > This might be fixed with boost-1.52.0-r6 — please try that and report, > thanks! The problem still exists. I'll attach a build.log. Created attachment 340868 [details]
/media/GFZ650GB/gentoo/tmp/portage/dev-libs/boost-1.52.0-r6/temp/build.log
Okay, reproduced :) the problem persists on dev-libs/boost-1.52.0-r6 (In reply to comment #8) > the problem persists on dev-libs/boost-1.52.0-r6 sorry for re-reporting - i'm too confused this weekend.... Why do we want a 'threads' USE flag for boost again at all? Problem still exists in 1.54.0? It seems, that suggested allocator variants does not work in shared build in non-threading implementation? Cause we do not do ONLY static boost builds, maybe we should just drop 'threads' USE-flag? Sorry, just to clarify, there is no '?' in first sentence in previous comment same here with 1.53.0 Created attachment 364820 [details, diff]
boost-1.52.0-non-threaded.patch for USE="-threads"
Using this patch i can upgrade my system from dev-libs/boost-1.49.0-r2 to dev-libs/boost-1.52.0-r using the following patch for the ebuild:
# diff -ubB /usr/portage/dev-libs/boost/boost-1.52.0-r6.ebuild /usr/local/portage/dev-libs/boost/boost-1.52.0-r7.ebuild
--- /usr/portage/dev-libs/boost/boost-1.52.0-r6.ebuild 2013-09-26 19:31:09.000000000 +0200
+++ /usr/local/portage/dev-libs/boost/boost-1.52.0-r7.ebuild 2013-12-07 16:33:17.044262182 +0100
@@ -71,6 +71,7 @@
"${FILESDIR}/${PN}-1.48.0-disable_icu_rpath.patch" \
"${FILESDIR}/remove-toolset-1.48.0.patch" \
"${FILESDIR}/${PN}-1.52.0-tuple.patch" \
+ "${FILESDIR}/${PN}-1.52.0-non-threaded.patch" \
"${FILESDIR}/${P}-locale-utf.patch"
# Avoid a patch for now
An "emerge @preserved-rebuild" runs fine afterwards, and any other package which depends on dev-libs/boost on my system compiles fine as well.
But i've no clue if this works on a USE="threads" system...
Patch works fine here with boost-1.53.0-r1. why is this marked as a blocker of 467256 ? the OP reported seeing this against glibc-2.15 which means stabilizing 2.16 is not a regression. (In reply to SpanKY from comment #16) > why is this marked as a blocker of 467256 ? the OP reported seeing this > against glibc-2.15 which means stabilizing 2.16 is not a regression. kodama ~ # eix ^glibc$ [U] sys-libs/glibc Available versions: (2.2) ~2.9_p20081201-r3^s 2.10.1-r1^s 2.11.3^s ~2.12.1-r3^s 2.12.2^s ~2.13-r2^s 2.13-r4^s ~2.14^s ~2.14.1-r2^s 2.14.1-r3^s ~2.15-r1^s 2.15-r2^s 2.15-r3^s 2.16.0^s ~2.17^s **2.18^s **9999^s {debug gd hardened multilib nscd profile selinux suid systemtap vanilla CROSSCOMPILE_OPTS="headers-only"} Installed versions: 2.15-r3(2.2)^s(02:12:18 11/15/13)(gd multilib -debug -hardened -profile -selinux -vanilla CROSSCOMPILE_OPTS="-headers-only") Homepage: http://www.gnu.org/software/libc/libc.html Description: GNU libc6 (also called glibc2) C library kodama ~ # emerge -pv1DNu sys-libs/glibc These are the packages that would be merged, in order: Calculating dependencies... done! Total: 0 packages, Size of downloads: 0 kB WARNING: One or more updates have been skipped due to a dependency conflict: sys-libs/glibc:2.2 (sys-libs/glibc-2.16.0::gentoo, ebuild scheduled for merge) conflicts with <sys-libs/glibc-2.16 required by (dev-libs/boost-1.49.0-r2::gentoo, installed) * IMPORTANT: 10 news items need reading for repository 'gentoo'. * Use eselect news to read news items. As long as dev-libs/boost is not fixed on a non-threaded system i cannot install sys-libs/glibc-2.16. IMHO this is a blocker. (And what is "OP"?) The fix is accepted upstream, what are we waiting for? (In reply to Julian Ospald (hasufell) from comment #18) > The fix is accepted upstream, what are we waiting for? For the sky to fall, but ofcourse. update it already -.- +*boost-1.52.0-r7 (29 Jul 2014) + + 29 Jul 2014; Julian Ospald <hasufell@gentoo.org> +boost-1.52.0-r7.ebuild, + boost-1.53.0-r1.ebuild, boost-1.54.0-r1.ebuild, boost-1.55.0-r1.ebuild, + +files/boost-1.52.0-threads.patch: + fix build with USE=-threads wrt #458404 All arches have at least boost-1.52.0-r7 for now in stable, thus - this issue is fixed |