HELP - boost wants to downgrade glibc

Moriah

I am installing a new system, so I fetched the stage3 yesterday. I need lvm2, which needs boost, but boost tried to downgrade the already installed glibc, which sets off alarms:

Hu · Moderator Joined: 06 Mar 2007 Posts: 21593

That version of Boost requires a lower glibc at runtime. Use a newer version of Boost. Based on the ChangeLog message, I suspect that glibc 2.16 and later have header definitions that conflict with the ones in Boost 1.49.

VoidMage · Watchman Joined: 14 Oct 2006 Posts: 6196

Moriah · Posted: Fri May 03, 2013 4:19 am Post subject:

The problem is that 1.49.0-r2 is the most recent version of boost that shows up after emerge --sync:

jburns · Posted: Fri May 03, 2013 6:08 am Post subject:

Add dev-libs/boost and dev-util/boost-build to the file /etc/portage/package.accept_keywords.

krinn · Watchman Joined: 02 May 2003 Posts: 7470

It could happen if you use stage3 file that include an unstable glibc (the 2.16) so installing it you end up with an unstable glibc.
But once install, if you pickup the stable keyword in your make.conf boost stable will be selected, but that boost stable couldn't run with that unstable glibc, hence the "want downgrade".

If it's that, it is something to filebug, stage3 should only be made with stable package.

Moriah · Posted: Fri May 03, 2013 3:18 pm Post subject:

Good point. I maybe might have missed with the mouse when I selected the stage 3. From the http://mirror.mcs.anl.gov/pub/gentoo/releases/amd64/current-stage3/ site, I fetched stage3-x32-20130425.tar.bz2 when I probably wanted stage3-amd64-20130425.tar.bz2 :oops:

I think at this early stage of the game, the best thing to do is just start over -- especially since its just a kvm virtual machine anyway. There is no obvious way to repair this error that I can see.
_________________
The MyWord KJV Bible tool is at http://www.elilabs.com/~myword

Foghorn Leghorn is a Warner Bros. cartoon character.

Stinky_Foot · Posted: Tue May 14, 2013 12:48 pm Post subject:

I faced the same problem yesterday when I was trying to update my whole system. Got some messages of conflicting dependencies that I was trying to resolve masking some of them, but then the emerge always tried to emerge first glibc-2.15-r3 (whilst I have 2.17) and I got the error. Suddenly, after trying various alternatives without success, it came to me to put the "--exclude=glibc" variable into the command since my version of glibc is the latest available, it worked and I was able to do the updating (well, in parts because some packages still refuse to compile, but I think it is a different problem).
_________________
'I' means I, 'we' means we.

ulenrich · Veteran Joined: 10 Oct 2010 Posts: 1480

Stinky_Foot · Posted: Fri May 17, 2013 5:54 pm Post subject:

ulenrich · Veteran Joined: 10 Oct 2010 Posts: 1480

No,
glibc
is the only ebuild you simply cannot downgrade by using usual Gentoo methods.

But
current~unstable
is a working release!

krinn · Watchman Joined: 02 May 2003 Posts: 7470

The safest thing to do, is just stop this, as it will continue until you do take action.
You should drop the ~amd64 keyword and add your current glibc to package.unmask to prevent the "portage want downgrade glibc" but "portage doesn't want to do it" chicken/egg loop.

And then just wait, as soon as stable have a better version or revision as your unstable glibc, your tree will be back to full stable.

Stinky_Foot · Posted: Sat May 18, 2013 2:44 pm Post subject:

All right, I suspected that the only remedy was to wait... thanks for the replies, guys.
_________________
'I' means I, 'we' means we.

Hu · Moderator Joined: 06 Mar 2007 Posts: 21593

Stinky_Foot · Posted: Sat May 18, 2013 5:50 pm Post subject:

Now I'm confused, what I am supposed to do?
_________________
'I' means I, 'we' means we.

Hu · Moderator Joined: 06 Mar 2007 Posts: 21593

Stinky_Foot · Posted: Sat May 18, 2013 7:46 pm Post subject:

So, is something like:

Hu · Moderator Joined: 06 Mar 2007 Posts: 21593

krinn · Watchman Joined: 02 May 2003 Posts: 7470

frank1980 · Tux's lil' helper Joined: 19 Feb 2006 Posts: 103

I have the same problem. But I use ~arch from every beginning of using Gentoo. I found glibc-2.17 and boost-1.53 were in ~arch, I did an unusual way to upgrade the system. I used "emerge kdebase-meta glibc" instead of "emerge -uDN world". Now I have the latest glibc, but boost need older glibc. You know gentoo refuses downgrading glibc.

I can't do anything now, any hints? Thank you.

Hu · Moderator Joined: 06 Mar 2007 Posts: 21593

Please post the full output of emerge --pretend --verbose --deep --update --newuse --tree --unordered-display dev-libs/boost dev-util/boost-build.

lefsha · Posted: Mon Sep 16, 2013 10:30 pm Post subject:

frank1980,

Use boost 1.54.0 that will solve the problem. boost 1.53.0 is somehow broken.
_________________
Lefsha

frank1980 · Tux's lil' helper Joined: 19 Feb 2006 Posts: 103

Thanks lefsha and Hu. I found boost-1.54 are in hard mask situation, I decide to wait till it is unmasked by official.