2005.0, glibc and multilib - is this right? [solved]

bendy · Last edited by bendy on Mon May 30, 2005 11:08 am; edited 1 time in total

Hi,

I am running an AMD64 system, multilib 2005.0 profile. I did an emerge -ud world yesterday and something unexpected happened.

The upgrade brought in a new package emul-linux-x86-glibc. Following this, my 32 bit binary UT2004 doesn't work.

Now, I thought I didn't need the emul-linux-x86-glibc package when running a multilib 2005.0 system, and indeed have been getting on fine without for a couple of months.

So, I unmerged emul-linux-x86-glibc and was about re-emerge glibc, but:

Maedhros · Posted: Mon May 30, 2005 10:11 am Post subject:

Multilib isn't controlled by USE flags any more, but by the system profile. As long as your /etc/make.profile symlink isn't pointing to the "no-multilib" profile, you're using multilib by default. What was the version number of emul-linux-x86-glibc? I think there was a dummy ebuild created for compatability purposes that didn't actually install anything, so you might want to check that it isn't that that's installed.
_________________
No-one's more important than the earthworm.

bendy · Posted: Mon May 30, 2005 10:24 am Post subject:

Ahhhh, dummy ebuild you say?

Well, it wants to install emul-linux-x86-glibc-1000, so maybe it's me that's the dummy.....

bendy · Posted: Mon May 30, 2005 11:09 am Post subject:

Sure enough, it turns out that I am the dummy. UT2004 didn't work because of the nvidiactl permission thing that I thought a had fixed a while ago....