2005.0 and multilib

[Maedhros]

Because multilib isn't controlled by USE flags anymore, but the profile itself.

[Decibels]

Thanks, that explains it. Docs seems a little dated, at least the ones I had, so was a little worried about it.
But everything seemed to be going very well, so was thinking it was really being used, but not shown. Or
don't really need it.

[hjh]

My profile seems to strictly forbid me from emerging gcc or glibc with a "multilib" USE flag. As I watch the output of the gcc emerge I see the configure script selecting --disable-multilib.

I haven't been able to find a solution to this from what I have read and it prevents me from following some of the clearly excellent advice in this thread. I wonder if I should try a route suggested earlier of installing again on a new partition and building a multilib gcc from there?

Any useful suggestions would be appreciated.

Also, emerging portage I notice that it tells me I do not have a vaild multilib environment. Something is screwed but I don't know where to look.

[spielc]

that's a easy one :

to get a working gcc and glibc with multilib do the following (i assume you have either multilib in your useflags or use 2005.0):

Code: Select all

features="-sandbox" emerge gcc
emerge glibc
emerge portage (now portage shouldn't complain about a "not valid multilib environment"

I hope that helps you a bit with the solution of your problems!

[pallaert]

Just after changing from profile 2004.3 to 2005.0 doing:

Code: Select all

emerge --update --newuse --deep --pretend --verbose world

give me the following package to emerge:

Code: Select all

These are the packages that I would merge, in order:

Calculating world dependencies ...done!
[ebuild   R   ] sys-devel/gcc-3.4.3-r1  (-altivec) -bootstrap -boundschecking -build -debug +fortran -gcj -gtk -hardened -ip28 (-multilib)* -multislot (-n32) (-n64) +nls -nocxx -objc -static (-uclibc) 0 kB
[ebuild  N    ] app-emulation/emul-linux-x86-glibc-1000  0 kB

Is this normal that this 2 ebuilds want to be merged after the Gentoo's 2005.0 Upgrade guide (http://www.gentoo.org/proj/en/base/amd6 ... t=1&chap=1) said to do:

Code: Select all

...
emerge unmerge emul-linux-x86-glibc
emerge -upv system
emerge -uv system

I found strange emul-linux-x86-glibc have to be merged and that the Upgrade guide said to unmerge it...
For gcc, maybe this is due to the --newuse that detects that previous gcc was build with +multilib and that the new USE flags prevent to use multilib as it is done at profile level...

[spielc]

I found strange emul-linux-x86-glibc have to be merged and that the Upgrade guide said to unmerge it...
For gcc, maybe this is due to the --newuse that detects that previous gcc was build with +multilib and that the new USE flags prevent to use multilib as it is done at profile level...

the emul-linux-x86-glibc-1000 package is just a "dummy" package (this means that actually nothing gets installed when you emerge it)

all the "work" is done by emerging glibc now (this means that glibc is compiled twice if you have multilib and four times if you have nptl enabled too)

but it is correct yeah, if you wanna have a working multilib environment you need the dummy package too

[hjh]

You may have noted those instructions have been repeated many times in this and similar threads. My emerge of gcc with the -sandbox feature does not result in a multilib enabled gcc. So clearly it is not such an easy one.

[spielc]

You may have noted those instructions have been repeated many times in this and similar threads. My emerge of gcc with the -sandbox feature does not result in a multilib enabled gcc. So clearly it is not such an easy one.

Well maybe i misunderstood you but i thought you wanted to have a working multilib environment (with sandbox and the like) and you'll get that by issueing the commands i mentioned in my earlier post

[supermihi]

I'm doing a new, clean 2005.0 amd64 install. I also wondered about the

Code: Select all

(-multilib)

when emerging gcc. So I found this thread, and now I'm wondering: Do I need the emul-linux-libraries at all when I directly install from 2005.0? I'm a bit confused about all the 32/64 libraries, I tried to install the fritzcapi ISDN drivers from AVM which carry a precompiled, likely 32bit kernel module. Am I able to use this one at all? I have no internet access without ...

[spielc]

I'm doing a new, clean 2005.0 amd64 install. I also wondered about the

Code: Select all

(-multilib)

when emerging gcc. So I found this thread, and now I'm wondering: Do I need the emul-linux-libraries at all when I directly install from 2005.0? I'm a bit confused about all the 32/64 libraries, I tried to install the fritzcapi ISDN drivers from AVM which carry a precompiled, likely 32bit kernel module. Am I able to use this one at all? I have no internet access without ...

Multilib means that you have multiple versions of some libraries on your computer. As 2005.0's default profile forces multilib you can't go without the emul-packages besides portage won't let you do that anyway...

When you really want to go without multilib you can (i would not do it if i were you tho) cuz there is a 2005.0 profile that doesn't use multilib (i think it's called 2005.0-nomultilib).

[hjh]

OK I should be more specific. I HAVE issued those commands but they have not produced the expected result. This was the reason for my post. Given that the fix is not working in this case I wondered if anyone else had encountered the same problem and could perhaps assist me in looking for the problem. Thanks for your suggestion.

I just noticed the following at the end of my re-emerge of gcc (with USE=multilib and FEATURES=-sandbox):

/usr/bin/gcc-config: line 1: /etc/env.d/gcc/x86_64-pc-linux-gnu: No such file or directory
* /usr/bin/gcc-config: Profile does not exist or invalid setting for /etc/env.d/gcc/x86_64-pc-linux-gnu
* Switching to x86_64-pc-linux-gnu-3.4.3 compiler... [ ok ]

[hjh]

anyone? anyone? Bueller? anyone?

[spielc]

OK I should be more specific. I HAVE issued those commands but they have not produced the expected result. This was the reason for my post. Given that the fix is not working in this case I wondered if anyone else had encountered the same problem and could perhaps assist me in looking for the problem. Thanks for your suggestion.

I just noticed the following at the end of my re-emerge of gcc (with USE=multilib and FEATURES=-sandbox):

/usr/bin/gcc-config: line 1: /etc/env.d/gcc/x86_64-pc-linux-gnu: No such file or directory
* /usr/bin/gcc-config: Profile does not exist or invalid setting for /etc/env.d/gcc/x86_64-pc-linux-gnu
* Switching to x86_64-pc-linux-gnu-3.4.3 compiler... [ ok ]

well what does gcc-config -l say?? what's the output of gcc-config <number of fresh emerged gcc>?

[hjh]

[1] x86_64-pc-linux-gnu-3.3.4
[2] x86_64-pc-linux-gnu-3.4.3 *
[3] x86_64-pc-linux-gnu-3.4.3-hardened
[4] x86_64-pc-linux-gnu-3.4.3-hardenednopie
[5] x86_64-pc-linux-gnu-3.4.3-hardenednossp


Thanks for staying with me on this one. I currently have the 2004.3 profile. I was forced to recompile gcc and glibc earlier due to a glitch with xorg which was eventually resolved but has perhaps borked the profile setup somehow.

Let me re-iterate, when I check the flags that the configuration step of the emerge process picks up for gcc, it specifically invokes --disable-multilib. Without a multilib gcc I can't emerge a multilib portage. Emerge specifically comments on this when I try.

Thankfully none of this is stopping me from doing the work that I need to do. It just bugs me though!!!

Cheers

J.

[spielc]

Okey this looks alright...

I guess you tried to emerge portage again?

/usr/bin/gcc-config: line 1: /etc/env.d/gcc/x86_64-pc-linux-gnu: No such file or directory
* /usr/bin/gcc-config: Profile does not exist or invalid setting for /etc/env.d/gcc/x86_64-pc-linux-gnu
* Switching to x86_64-pc-linux-gnu-3.4.3 compiler... [ ok ]

this shouldn't be a real problem if you are able to compile/emerge other things without problems but it was important that you were able to compile gcc with multilib and -sandbox. I would really try to go for another emerge portage as it looks like the emerge of gcc with multilib went fine (USE=multilib FEATURES=-sandbox emerge gcc if that was the command you issued and the emerge finished without compile error you should be ready to go...)

[hjh]

* No valid multilib environment found!
* Building without multilib support. If
* you want to have multilib support,
* emerge gcc with "multilib" in your
* useflags.


The above is the output from emerge portage. "--disable-multilib" is clearly flagged in the gcc compile. I can keep emerging it until the cows come home but somewhere, somehow the configure script is deciding that multilib is not for gcc. If you do "USE=multilib FEATURES=-sandbox emerge -pv gcc" it will show multilib in parentheses which I believe indicates that this flag is not permitted under the current profile.

Options would appear to include the following:

- hope somebody can diagnose the issue, implement a fix and then switch to 2005 profile

- backup all necessary files and configs and blow it all away and do a clean install from 2005 CD

- install my existing 2004.3 distro again in a new partition, compile gcc with multilib, fix portage on the existing system and try to switch that to 2005 profile

- leave it as it currently is and do nothing until things are broken enough to compromise stability or my ability to get work done

Thanks for you efforts.

[spielc]

* No valid multilib environment found!
* Building without multilib support. If
* you want to have multilib support,
* emerge gcc with "multilib" in your
* useflags.


The above is the output from emerge portage. "--disable-multilib" is clearly flagged in the gcc compile. I can keep emerging it until the cows come home but somewhere, somehow the configure script is deciding that multilib is not for gcc. If you do "USE=multilib FEATURES=-sandbox emerge -pv gcc" it will show multilib in parentheses which I believe indicates that this flag is not permitted under the current profile.

Options would appear to include the following:

- hope somebody can diagnose the issue, implement a fix and then switch to 2005 profile

- backup all necessary files and configs and blow it all away and do a clean install from 2005 CD

- install my existing 2004.3 distro again in a new partition, compile gcc with multilib, fix portage on the existing system and try to switch that to 2005 profile

- leave it as it currently is and do nothing until things are broken enough to compromise stability or my ability to get work done

Thanks for you efforts.

Two things just came to my mind:

first: what profile is your /etc/make.profile pointing to?? You changed the profile back to 2004.3 after you found out the 2005.0-script isn't working? If NOT change the simlink /etc/make.profile back to the 2004.3 profile and recompile gcc with USE=multilib FEATURES=-sandbox emerge gcc

Second: did you recompile glibc after you reemerged gcc?? If not try that followed by emerge portage

[Kuhrscher]

HJH: A long time ago I had the same problem. So don't give up

Please try to boot using a 2004.3-livecd, chroot into your environment and reemerge portage and gcc and portage (again). If portage complains about missing multilib, just ignore it a this moment.

Code: Select all

USE=multilib emerge --oneshot portage

Code: Select all

USE=multilib FEATURES=-sandbox emerge --oneshot gcc

Code: Select all

USE=multilib emerge --oneshot portage

[dmpogo]

As I understand,

in 2005.0 multilib is forced not in the way that the option is always set.
It is forced in a way that there is NO SUCH OPTION AT ALL, while multilib functionality is built in.
As the result, packages which check this option come back with (-multilib), since they
cannot even find such option. And it does not show in emerge info

[hjh]

spielc - profile is 2004.3 and correctly setup as far as I can tell. Yes, I have re-emerged glibc and attempted to then emerge portage.

Kurscher - nice suggestion. I tried this but it did not change anything. Same problem as above.

As an aside, I briefly found myself in a situation where none of gcc, portage and glibc would compile, the latter with the dreaded "long double" error. I regained the ability to compile these things when I switched to the "hardened" version of the compiler. This used to be the default but there was some issue with the hardened profile for an xorg-x11 update. I wonder if the actual switch to the non-hardened profile was not completely or properly made. Still, the wondering doesn't really prompt me with a solution for the current problem. How am I to get a multilib-enabled gcc and portage?

I've seen some comments about re-emerging the toolchain when making updates to things like glibc. Might this be pertinent to my current situation?

[hjh]

Well....somewhat cautiously I might claim success. I don't truly know the reason for the issue but problems with my gcc setup I think are a root cause. I switched back to gcc-3.3.4 which is multilib enabled on my system. I was then able to follow the directions of "my world" in the "Glibc-long double" thread and manually migrated to the 2005 profile. I will attempt to move back to gcc3.4.x in the future. I will wait and see now whether everything is indeed operating as it should.

Thanks for the suggestions.