On 03/21/2011 11:13:36 AM, walt wrote: > On 03/21/2011 02:19 AM, Helmut Jarausch wrote: > > Hi, > > > > probably, portage-2.2.0_alpha28 has broken my system. > > > > I have reinstalled a binary version of portage-2.2.0_alpha27, but > ... > > > > For many packages, portage installs libraries into /usr instead of > > /usr/lib64 or /usr/lib32 > > > > Probably, the function get_libdir > > (defined in /usr/portage/eclass/multilib.eclass) > > returns an empty string. > > Seems that some important definitions are stored in > /usr/portage/profiles/features/multilib/make.defaults and for some > reason they are not being honored. > > That file should be sourced during every emerge, depending on your > selected portage profile. What "does eselect profile list" say? > Is the selected profile the correct one? > > Maybe using the -d flag with emerge will give you a hint where things > are going wrong.
Thanks, Walt. /usr/portage/profiles/features/multilib/make.defaults looks OK The selected profile is default/linux/amd64/10.0/desktop which is OK, as well. I should have mentioned that after installing portage-2.2.0_alpha28 the search path included /usr/portage/bin which doesn't exist. I have no idea where this came from. The debugging run revealed that the 'multilib' USE flag got lost. I've just emerged a package both on my machine and a very similar machine but which hasn't been updated the last few days. Diffing the two log files showed that the multilib USE flag isn't in effect on my machine (only). I've compared /etc/make.conf on both machines and there isn't any difference. So, it looks like a broken profile here. What to do about that? Thanks, Helmut.
