Summary: | dev-libs/boost asks for glibc downgrade (2.16 → 2.15) on x32 profile | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Alex Mtx <vertexSymphony> |
Component: | [OLD] Development | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | kripton, pinkbyte |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 393673 |
Description
Alex Mtx
2012-12-10 14:37:15 UTC
Well, as you've already keyworded glibc, the natural next step would be to keyword boost and and then see if anything else needs to be keyworded by 'emerge -upvD @world' and/or revdep-rebuild. You use ~arch glibc, so IMO you should use ~arch boost too, as have already said earlier (In reply to comment #1) > Well, as you've already keyworded glibc, the natural next step would be to > keyword boost and and then see if anything else needs to be keyworded by > 'emerge -upvD @world' and/or revdep-rebuild. Actually I didn't keyword glibc by myself, actually the profile was the one doing it: ================================================= Sylbit linux # cat /usr/portage/profiles/arch/amd64/x32/package.keywords # Copyright 1999-2012 Gentoo Foundation # Distributed under the terms of the GNU General Public License v2 # $Header: /var/cvsroot/gentoo-x86/profiles/arch/amd64/x32/package.keywords,v 1.10 2012/12/06 06:26:14 vapier Exp $ # We need newer versions of toolchain packages. ~sys-apps/sandbox-2.6 amd64 ~sys-devel/gcc-4.7.1 amd64 ~sys-libs/glibc-2.16.0 amd64 ================================================= I forgot to keyword boost-build too (dummy me), but still the issue remains of default glibc (as marked by the profile) not being compatible with a package. maybe keywording boost and boost-build in the profile up to 1.52 could be an option to keep things compiling ... but on the other hand that also pulls in boost 1.52 bugs CCing toolchain maintainers(do not really know who is responsible for x32 profile) You cannot use stable keywords for x32. Please go to ~amd64. (In reply to comment #5) that's not really true. stable keywords for x32 work fine, ignoring general gcc-4.7 and glibc-2.16 issues. but even then, stage building and most stable packages now work with glibc-2.16/gcc-4.7. (In reply to comment #5) > You cannot use stable keywords for x32. Please go to ~amd64. That's really discouraging for me ... Telling me to go all unstable (even with unrelated software) because of 1 package failing to get along with the version of libc doesn't look good for me ... because I kept installing the things I needed and havent found one single problem for the "stable" versions of packages. if x32 had the requirement of newer packages on certain areas, a keyword counting on the version (<=) could be put in place and the whole system kept "stable". The solution for me was raising the boost/boost-build version by keywording it (checking the bugtracker before to see if there's a deal-breaker for me; thankfully not), but it was nice to drop the notice here to see if things could be made more smooth to other people. |