2004.3->2005.0: glibc emerge error, long double (solved)

[Little Nemo]

I followed andrewd18's instructions, but skipped re-emerging glibc and gcc in step 2 and just emerged emul-linux-x86-glibc. I think that at some point my emul emerges got screwed up (but didn't affect me until now) so re-emerging that package got the right libraries going.

I also didn't need to re-emerge baselayout (I was current and had an /etc/env.d/04multilib).

I thought I had tried all possible combinations of going back and forth between the profiles, but in fact it just started working now after I applied your method: at the point where the sizeof problem occurred, I followed andrew18's instructions, but skipped glibc and gcc in step 2 as well as the entire step 4. Thanks!

I would still feel better if I knew what had gone wrong in the first place.

[My_World]

Little Nemo:
So you basically skipped:

Code: Select all

2) Re-emerged glibc and gcc. I also did the emuls again for good measure.
emerge glibc gcc  (emul removed cause you said you re-emerged it to fix the libs)

&

4) Emerged baselayout
emerge -v --oneshot baselayout 

Sorry for stating tthe obvious but I have tried since Friday to get this right and still no luck, just wanna make sure I'm 100% with you on what you did.

[Little Nemo]

Yes, that's it. From the point where the glibc compile failed with the sizeof error I followed andrew18 except for the steps you mentioned.

Some time before that, while still in a working 2004.3 environment I had made sure baselayout was okay and gcc 3.4.3 had compiled with multilib support and was actually activated (with gcc-config). Then I had compiled glibc again (under 2004.3), but all of that was a few days ago and a lot of desperate attempts earlier.

Good luck!

[My_World]

After three days of sitting infront of the PC and having seen the sun rise on two occasions I finally got the profile upgrade working.

Here, in detail, is what I did to get it working:
Firstly I switched back to the 2004.3 profile, making sure it was a COMPLETE switch! (Very important)

Code: Select all

rm /etc/make.profile
ln -s /usr/portage/profiles/default-linux/amd64/2004.3 /etc/make.profile
rm -fr /lib32 /usr/lib32 <-- If you followed the upgrade guide then this was made dirs and not symlinks

ln -s /emul/linux/x86/lib /lib32
ln -s /emul/linux/x86/usr/lib /usr/lib32  <-- This I think is very important, do not skip these two steps!

emerge emul-linux-x86-glibc emul-linux-x86-compat emul-linux-x86-baselibs  <-- I found this in another thread and thought it could do no harm in recompiling these, doesn't take long either

USE="multilib" FEATURES="-sandbox" emerge --oneshot gcc  <-- Making sure multilib is supported

http://forums.gentoo.org/viewtopic-p-22 ... ml#2202085

Assuming this works you can then emerge portage to get a 32bit sandbox and then follow the 2005.0 upgrade guide.

The above I also got from the same thread (click the link) and as I was desperate to get a fix, so, any goes!

Code: Select all

emerge portage

From here on in I followed the rest of the upgrade guide and everyting went flawlessly!

Code: Select all

rm /lib32 /usr/lib32
mkdir /lib32 /usr/lib32

cp /emul/linux/x86/lib32/libsandbox.so /lib32
cp /emul/linux/x86/usr/lib32/libc.so /usr/lib32
cp /emul/linux/x86/usr/lib32/libpthread.so /usr/lib32
cp /emul/linux/x86/usr/lib32/*crt*.o /usr/lib32
env-update

emerge -v --oneshot baselayout

rm /etc/make.profile
ln -s /usr/portage/profiles/default-linux/amd64/2005.0 /etc/make.profile

emerge -v --oneshot '>=sys-libs/glibc-2.3.4.20041102'
emerge unmerge emul-linux-x86-glibc
emerge -upv world
emerge -uv world

Well, I'm just glad that is over, now I can catch up on some sleep!

[ngyahloon]

Hi,

This thread has been really useful for me. Just wanna add my experience a bit. Basically all the steps are corrent and workable. Just pay attention to all the versioning of the package to be update:

Code: Select all

'>=sys-devel/gcc-3.4.3'
'>=sys-apps/portage-2.0.51-r9'
'>=sys-devel/gcc-config-1.3.9'
'>=sys-devel/distcc-2.18.3-r1'
'>=linux-headers-2.6.8.1-r4'
'>=emul-linux-x86-glibc-2.3.4.20041102'
'>=sys-libs/glibc-2.3.4.20041102'

Everything was ok for me except for linux-headers. I didn't realise my system was still using version 2.6 something where as to upgrade to 2005.0 profile, you need at least version 2.8. So I kept getting some error compiling sigreturn.o. After ensuring all software have the correct version, it was pretty smooth.

[AngelM]

A lot of thanks.

Finally it works now.

Yiepieh

[JLP]

I have followed the instructions from My_World and now I have succesfuly upgraded to 2005.0 profile. Thanks!

[mattjgalloway]

My_World - thanks for that howto!

What I would add is that you should follow the 2005.0 migration guide but make sure that when it says to emerge anything, that you do it. I thought that just because I'd already had it emerged it'd be ok - that's what was throwing me off! For me it was the portage recompile that My_World pointed out that I needed!

[tscolari]

i see that you had this problem while migrating from 2004.3 to 2005.0
but ive just untared the stage3 from the 2005.0 livecd and was trying to re-compile glibc and got the same error!

What should i do to fix this?

[TheJoker]

My_World and everybody else,

Thanks for everything.

When I reverted back to 2004.3 I restarted the "By hand" section from the first point; by emerging gcc, from there on it's worked just fine.
http://forums.gentoo.org/viewtopic-p-22 ... ml#2294693

Don't use the "The easy way", it wasn't for me

Cheers!

J

[tscolari]

i see that you had this problem while migrating from 2004.3 to 2005.0
but ive just untared the stage3 from the 2005.0 livecd and was trying to re-compile glibc and got the same error!

What should i do to fix this?

i shall move to the 2004.3 profile to re emerge then?
im just waiting know what to do to install it here, my computer is OS less by now

[tscolari]

Just want to know a question, can a ldflags setted in make.conf cause this error in the configure?
I ask because if it can, i will give another try in installing stage1 from stage3, otherwise i will try a stage1 install only :/

[peter96362930]

I'm following My_World's instructions but I'm still getting the "sizeof" error when I try and emerge glibc. I noticed that when I run

Code: Select all

cp /emul/linux/x86/lib32/libsandbox.so /lib32

that libsandbox.so doesn't exist. Does that indicate what I'm doing wrong?

[MagicTom]

I'm following My_World's instructions but I'm still getting the "sizeof" error when I try and emerge glibc. I noticed that when I run

Code: Select all

cp /emul/linux/x86/lib32/libsandbox.so /lib32

that libsandbox.so doesn't exist. Does that indicate what I'm doing wrong?

I had the same problem. (I think it is beacause I wasn't using multilib before switching to 2005.0, but I'm not sure about it.)
I did as it I didn't notice it, and I only got an error when trying to compile glibc, this famous problem with "sizeof long double"... However, I managed to compile it without having libsandbox.so. If you have the same error, try this:

Code: Select all

FEATURES="-sandbox" USE="multilib" emerge -v --oneshot '>=sys-libs/glibc-2.3.4.20041102'

Once you have switched to 2005.0 (rm /etc/make.profile && ln -s blah blah...) and compiled glibc correctly, re-emerge portage, this will create /lib32/libsandbox.so.

That's what I did (spent my evening getting this 2005.0 working), and I'm now emerging system... Time to go to bed (2:34am here in France )

[peter96362930]

MagicTom,

Thanks for the hint. Unfortunately, it didn't work for me. I'll have to stick with 2004.3 for the time being.

[KeBl3Sk]

I was experiencing the missing libsandbox.so problem, following My_World's steps got it fixed.

Thanks

I wonder what was the root cause of this.

[isolationism]

Bumping because I ran into the exact same problem and my_world's solution fixed it, too.

Maybe something to this effect should be added to the "official" 2004.3 => 2005.0 documentation so other people won't be wasting their time as I have beating my head against the desk wondering what I did wrong?

And, to my_world: Thank you.

[isolationism]

As it turns out this worked perfectly for one of my systems but not the other. I have no idea why this might have happened. I followed precisely the same instructions my_world posted in both cases, but one of the PCs fails while building glibc-2.3.4.20041102 which is infuriating as it must be one of the longest ebuilds you can run on an amd64 system. This is the error I get:

Code: Select all

/var/tmp/portage/glibc-2.3.4.20041102-r1/work/build-x86-i686-pc-linux-gnu-nptl/nptl/libpthread.so: undefined reference to `errno@GLIBC_PRIVATE'
/var/tmp/portage/glibc-2.3.4.20041102-r1/work/build-x86-i686-pc-linux-gnu-nptl/nptl/libpthread.so: undefined reference to `__libc_dl_error_tsd@GLIBC_PRIVATE'
/var/tmp/portage/glibc-2.3.4.20041102-r1/work/build-x86-i686-pc-linux-gnu-nptl/nptl/libpthread.so: undefined reference to `__resp@GLIBC_PRIVATE'
/var/tmp/portage/glibc-2.3.4.20041102-r1/work/build-x86-i686-pc-linux-gnu-nptl/nptl/libpthread.so: undefined reference to `h_errno@GLIBC_PRIVATE'
collect2: ld returned 1 exit status
make[2]: *** [/var/tmp/portage/glibc-2.3.4.20041102-r1/work/build-x86-i686-pc-linux-gnu-nptl/nscd/nscd] Error 1
make[2]: Leaving directory `/var/tmp/portage/glibc-2.3.4.20041102-r1/work/glibc-2.3.3/nscd'
make[1]: *** [nscd/others] Error 2
make[1]: Leaving directory `/var/tmp/portage/glibc-2.3.4.20041102-r1/work/glibc-2.3.3'
make: *** [all] Error 2

Anybody have any suggestions at all? I also tried following these instructions:

http://forums.gentoo.org/viewtopic-p-21 ... ml#2196245

... Although they're nearly identical with a few exceptions. I've tried on four separate attempts to compile sys-libs/glibc-2.3.4.20041102-r1 now and they've all failed. I'm willing to entertain any suggestions anyone might have on the matter as I really want this server upgraded to 2005.0. Thanks in advance!

[apryan]

iso,
I'm getting the same errors you are. Gonna try the "hard way" atm and see if that works.

[isolationism]

Well, I've gone about it the "hard" way a bunch of times, going back and forth between 2004.3 and 2005.0 and I'm still getting the same error compiling glibc-2.3.4.20041102-r1 described above (having to do with libpthread.so). apryan, have you had better luck?

Edit: Finally, I got glibc to compile. I started with this ticket:

http://bugs.gentoo.org/show_bug.cgi?id=90091

... Copied the displayed list of "stale" files, and removed them. This is an oldish installation, after all -- it's been around for probably 5-6 months now, or thereabouts.

Next, I looked for old copies of libpthreads.so. Inexplicably, there was one in /bin/ of all places. Well, duh. This was probably the culprit -- What software would have done that? So I removed it and linked it back to libpthread-0.10.so in /lib then followed my_world's guide all over again. Success!

[eradicator]

Additionally, now that sandbox and portage are split from eachother in ~amd64, you should reemerge sys-apps/sandbox instead of sys-apps/portage to get the 32bit sandbox if you're in ~arch. portage itself is now just the python code. Unfortunately, we haven't been able to update the Makefile because of some infrastructure problems.

[satanskin]

I've been following My_World's guide exactly and it was working up unitl emerging glibc. I did

Code: Select all

emerge -v --oneshot '>=sys-libs/glibc-2.3.4.20041102'

and let it go overnight. When I came back today I got this error again (which I have been getting frequently lately):

/var/tmp/portage/glibc-2.3.4.20041102-r1/work/build-x86-i686-pc-linux-gnu-nptl/nptl/libpthread.so: undefined reference to `h_errno@GLIBC_PRIVATE'
collect2: ld returned 1 exit status
make[2]: *** [/var/tmp/portage/glibc-2.3.4.20041102-r1/work/build-x86-i686-pc-linux-gnu-nptl/nscd/nscd] Error 1
make[2]: Leaving directory `/var/tmp/portage/glibc-2.3.4.20041102-r1/work/glibc-2.3.3/nscd'
make[1]: *** [nscd/others] Error 2
make[1]: Leaving directory `/var/tmp/portage/glibc-2.3.4.20041102-r1/work/glibc-2.3.3'
make: *** [all] Error 2


EDIT: I fixed it. Adding USE="-nptl" to the beginning fixed it. Now just have to reemerge everything with nptl again.

[NismoC32]

I have some problems with the 2005.0 profile.
I used the Gentoo 2005.0 LiveCD to install gentoo. Everyting went fine until I was going to uppgrade the glibc library.
So I searched this forum for a possible solution and ended up with this tread.
I switched to 2004.3 and there was no problem with installing the latest glibc.
When I switched back I was unable to use the emerge command, all I get is:

>>> emerge (1 of 1) app-editors/joe-3.2 to /
* It appears you have switched to the 2005.0 profile without following
* the upgrade guide. Please see the following URL for more information:
* http://www.gentoo.org/proj/en/base/amd6 ... -amd64.xml

I switched back to 2004.3 and followed the instructions on this page but without any improvment and I now don't
have a clue to whats wrong.

What could bee wrong ?

[brankob]

This is why I sometimes hate Gentoo.

With this kind fo problem, there is no way for ordinary user to help himself. All he gets is a choice between a rigid script or a equally rigid manual transition, consisting just of actual steps, without an explanation about the role of packages involved.

Without this, if anything goes wrong, user can ponder, which (if any / only one) of N steps was wrong.
It would be nice to know a bit more about gcc and intimately coupled libraries etc, but this would obviously break some internal code of conduct in Gentoo
.
Heere is a script and if that doesn't work, GFY.

It's interesting that I already made transition to 2005.0 profile some month or more ago after quite some trials/errors and I thought "Phew. O.K. it wa s painfull, but transiental- I did it once, there will be no more, right ?"


It would be very nice from developers just to hear why exactly is this transition such a pain, if nothing else...

[scottf]

I got bit by the 2004.3 to 2005.0 profile upgrade problem too. I tried running the 2004.3-2005.0upgrade.sh upgrade script and all seemed fine until the final step 'emerge -uv system' when I found out I couldn't compile 64bit executables anymore. It turns out that I had actual directories for /usr/lib and /usr/lib64. After copying the /usr/lib64 files to /usr/lib and making a link from /usr/lib64 to /usr/lib and reverting to the previous profile, I was able to manually go though the update.

Hope this helps someone else.