[solved] guide to profile 17.1 fails several lib32 reemerge

Vrenn · Guru Joined: 15 Dec 2004 Posts: 327

I followed the news guide up to point 11.
emerge -1v /lib32 /usr/lib32

Then several Ebuilds (up to 20 of 80) failed and the big reemerge could only be processed by several --skipfirst (be sure to skip the right one)

Considering the ebuilds I wrote down (oldscool with pencil :-)

)the order, emerge wants to proceed looks lightly messed up.

So I emerged manually (emerge --oneshot) ebuilds in following order:
glib
systemd (wanted first, broke without glib?)
libcroco
atk
gdk-pixbuf
at-spi2-core
at-spi2-atk

Suddenly I had a circular dependeny of harfbuzz and freetype (russia solved this ;-)

)
USE="-harfbuzz" emerge -O1 freetype #so without the harfbuzz useflag
emerge -O1 harfbuzz freetype #now with the harfbuzz useflag

going on...
fontconfig
cairo

got lazy and let emerge -1v /lib32 /usr/lib32 do the job again:
libXft
pango
librsvg
gtk+-3
gtk+-2

This should be the right order

At last I deleted as point 12. told me the old symlinks.

I believe glib/systemd and freetype/harfbuzz did messed point 11 of the profile 17.1 upgrade guide and hope, I could help others who fear to break something getting some of dependency conflicts of this type.

PS: As noted on guide a emerge -e @world might do the job too...
_________________
With nice greetings
Vrenn

marco.difresco · Apprentice Joined: 29 Jul 2011 Posts: 170

STrRedWolf · n00b Joined: 02 Sep 2002 Posts: 72

Having a similar one here:

x11-libs/libva-vdpau-driver
dev-libs/glib
media-libs/graphene
x11-libs/libX11
x11-libs/libXext

...then all x11-libs started having problems. I traced it back to rebuilding xcb-proto, then libxcb, libX11. Then one more time with emerge -1v /lib32 /usr/lib32...

dev-libs/glib:
checking for LIBMOUNT... no
configure: error: *** Could not find libmount

Some google-fu says this is in util-linux... re-emerge that... try again... libpcre was missing... Re-emerge that... now it's compiling.

What I would do if you encounter an emerge problem:

Look at the log to see where it broke. Most of the time, it's a required library that the package checked for and failed on.
Re-emerge that library. Some are in non-obvious packages (libmount is in util-linux). If that broke, go to step 1. Sometimes, it's a hidden dependency that holds everything up. (Yak shaving here)
Re-emerge the build that broke. It should build now, but some (glib) may need a few more items.
If you have others that you need to re-emerge, re-emerge those now.
Retry the emerge -1v /lib32 /usr/lib32

Edit: Had libv4l also break, but this time it hit bug 616608 in the build. Doing emerge --resume --skipfirst twice (once for this, once for ffmpeg) then rerunning emerge -1v /lib32 /usr/lib32 did the trick.

I think we need a better tool than just one-shot emerge, if it's going to trip on dependencies.