Summary: | dev-util/boost-build-1.51.0 cannot be compiled | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jimis Hol <jimishol> |
Component: | New packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | doug.hunley, neil, NightNord |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
build.log of boost-1.51.0
enviroment of boost-1.51.0 build.log of boost-1.51.0 in english i hope Proposed patch to strip LDFLAGS |
Description
Jimis Hol
2012-11-02 18:13:04 UTC
Created attachment 328120 [details]
build.log of boost-1.51.0
emerge -pqv '=dev-util/boost-build-1.51.0' [ebuild U ] dev-util/boost-build-1.51.0 [1.49.0] USE="-examples -python {-test%}" Created attachment 328122 [details]
enviroment of boost-1.51.0
Created attachment 328124 [details]
build.log of boost-1.51.0 in english i hope
I have this here as well. It fails building 'b2' and the error spewed indicated a file is missing somewhere. However, going into /var/tmp/portage/boost-build-1.51.0/blah and running the same command by hand produces the 'b2' binary w/o issue Emerging dev-util/boost-build is known to failed when the LDFLAGS ends with a space, as in your case (from your emerge --info): LDFLAGS="-Wl,-O1 -Wl,--as-needed " I suggest your track this error in your make.conf. Your probably have a LDFLAGS="${LDFLAGS} ${SOME_UNDEFVAR}" somewhere. The default make.defaults in /usr/portage/profiles/... is the first definition for LDFLAGS on Gentoo. Alternatively, you could emerge it with: LDFLAGS="-Wl,-O1 -Wl,--as-needed" emerge -av boost-build and keep that in per-package ldflags (see the wiki: http://en.gentoo-wiki.com/wiki/Safe_LDFLAGS). > and keep that in per-package ldflags (see the wiki:
> http://en.gentoo-wiki.com/wiki/Safe_LDFLAGS).
Actually, /etc/portage/env is probably better for that.
Created attachment 328138 [details, diff]
Proposed patch to strip LDFLAGS
You are right. The first occurance of LDFLAGS in make.conf was LDFLAGS="${LDFLAGS} ". So I changed it as LDFLAGS="${LDFLAGS}" and all is ok. Thank you! The same is true of CFLAGS and CXXFLAGS, btw. The patch should, imho, deal with all three of these *** Bug 441866 has been marked as a duplicate of this bug. *** *** Bug 441866 has been marked as a duplicate of this bug. *** *** Bug 441866 has been marked as a duplicate of this bug. *** |