The glibc 2.6 thread

devsk · Posted: Mon Aug 13, 2007 1:32 am Post subject:

any known gotchas left remaining with plain gcc-4.2 and glibc-2.6.1? I plan to up the kernel-headers to 2.6.21 and emerge glibc, but wanted to make sure before I do that.

Master Shake · Posted: Mon Aug 13, 2007 2:01 am Post subject:

As far as I know all the issues are nonissues now-a-days. My old problems of things dieing doesn't happen anymore.
_________________
System Specs:
64-bit gentoo linux
Q6600 @ 3.2Ghz
P35 Chipset
4 Gigs 800mhz 4-4-4-12
Nvidia GeForce 8800 GTX @ 630mhz

pussi · l33t Joined: 08 May 2004 Posts: 727 Location: Finland

i got quite weird error when installing glibc-2.6.1:

seren · Guru Joined: 27 Aug 2005 Posts: 448 Location: Wisconsin

maybe you should post that in a paludis thread, it doesn't look like a glibc problem, you can also ask in #paludis on freenode.

LostControl · Posted: Mon Aug 13, 2007 8:15 pm Post subject:

Hi,

I got the same error with paludis & glibc-2.6.1 too

_________________
http://www.jaqpot.net
http://www.fail2ban.org

kernelOfTruth · Posted: Mon Aug 13, 2007 8:30 pm Post subject:

that file is regenerated during

roderick · Posted: Mon Aug 13, 2007 8:47 pm Post subject:

glibc 2.6 and 2.6.1 (both recently upgated with full system/world rebuilds) worked flawlessly here under gcc 4.1.2 and 4.2.0 using portage.

So, I would think there is an issue with bash scripting under paludis or how it handles some environment variables, which maybe have gotten squashed. It would be nice to get a copy of an emerge --info on your system and also get a copy of the paludis environment to check and see what is happening. I saw a similar issue with paludis not working with cd some_dir/../other_dir which under normal bash, evaluates to cd other_dir. With paludis it was failing and nver getting to other_dir.

I could be wrong though. In any case, I would suggest opening a bug with the paludis devs to see if they can help.
_________________
If God were a pickle, I'd still say "no pickle on my burger".
http://roderick-greening.blogspot.com/

zxy · Posted: Tue Aug 14, 2007 10:02 am Post subject:

Well glibc-2.6.1 compiled fine here with gcc-4.2.0 and paludis-0.24.5.
_________________
Nature does not hurry, yet everything is accomplished.
Lao Tzu

Ssl · Apprentice Joined: 21 Feb 2003 Posts: 178 Location: Serbia

Got the same error as user pussi with paludis-0.24.5 and gcc-4.1.2 on glibc-2.6.1.
kernelOfTruth's fix doesn't make difference here.

roderick · Posted: Tue Aug 14, 2007 2:55 pm Post subject:

Can anyone with paludis and getting this error try it with portage's emerge to ensure it's not their system/setup
_________________
If God were a pickle, I'd still say "no pickle on my burger".
http://roderick-greening.blogspot.com/

pussi · l33t Joined: 08 May 2004 Posts: 727 Location: Finland

Ingmarv · Posted: Tue Aug 14, 2007 7:43 pm Post subject:

Fixed in paludis-0.24.6

Ssl · Apprentice Joined: 21 Feb 2003 Posts: 178 Location: Serbia

Ingmarv: Not fixed. Broken for me still with 0.24.6.

nikolavp1 · n00b Joined: 01 Feb 2007 Posts: 18

roderick · Posted: Wed Aug 15, 2007 2:18 pm Post subject:

Buddha001 · Tux's lil' helper Joined: 24 Nov 2005 Posts: 76

Does upgrading to glibc 2.6.1 from 2.5 require anything special (i.e. complete rebuild of all packages)? Or am I good to go after installing it?

roderick · Posted: Mon Oct 15, 2007 12:36 pm Post subject:

jkomar · Posted: Thu Oct 18, 2007 6:06 pm Post subject:

It seems glibc-2.6.1 builds fine with Paludis on amd64, but not on x86. I've had it fail on 2 of our x86 machines using Paludis, but it built and installed fine using Portage. It built fine on our amd64 machines using Paludis.

Jason
_________________
www.jbox.ca
www.flashinthepan.ca
stormfront Portage/Paludis overlay