Glibc-2.20 Upgrade For Racy/Carolina

[battleshooter]

Put this together as some Carolina users wanted the latest Chrome.

Tested on different kernels ranging from 3.0.66 to 3.17, Racy (3.0.66 kernel), Carolina 1.1 (standard 3.2.13 Carolina kernel), Carolina 1.2 (3.17 kernel) running applications seem to be fine, but I have not tested compiling extensively.

Glibc, GCC, and Binutils have been compiled twice (2 pass).

As glibc is a core system element I would advise testing this on a non-essential Puppy install if you're not sure what you're doing. I haven't had any problems with it, but better safe than sorry.

It seems fully backwards compatible so any programs compiled with an older glibc will work, but anything compiled with the new glibc will not work with an older glibc.

Installation order:
GCC last.

Downloads
glibc-2.20.pet 27.7 MB
gcc-4.9.2.pet 35.8 MB
binutils-2.24.pet 11.5 MB

GCC dependencies:
gmp-6.0.0.pet 636 KB
mpc-1.0.2.pet 110 KB
mpfr-3.1.2.pet 469 KB

The make check results for GCC and glibc are attached if anyone needs to see them.

Racy 5.5:

Carolina 1.1:

Carolina 1.2 with 3.17 kernel:


6/11/14 Edited: Installation order

[mikeslr]

Hi Battleshooter,

I figured that since I asked for them the least I could do was try them out. Thanks, as always, for your hard work and dedication.
I downloaded all the pets in your post, exited Carolina and backed up its SaveFile, rebooted into Carolina and unloaded some SFSes so I could try things out.
Initially I had a problem installing the pets. One seemed to hang up the computer. But maybe I just didn't wait long enough for it to finish installing. They eventually installed by first installing those you've ID'd as dependencies, then binutils, then glibc, then gcc. The last was the one I think I had had a problem with. Then I rebooted without a problem. Before attempting to load or install Chromium, I tested some of my most frequently used apps. They worked. So next it was time to try the three versions of Chromium 37 I had previously downloaded.
The two by peebee, built for his LX Pups, found here, http://www.murga-linux.com/puppy/viewto ... 94e0fe24d2
loaded, but did not run. Trying either via terminal, reported:

# chromium
/usr/lib/chromium/chromium: error while loading shared libraries: libevent-2.0.so.5: cannot open shared object file: No such file or directory

I could not run ldd to see if anything else was missing. "Which chromium" took me to a wrapper script.

I next tried kost@s' Chromium 37, built for Slacko, found here: http://murga-linux.com/puppy/viewtopic.php?t=90983 which loaded but segfaulted.

Out of curiosity, I tried "registering" shinobar's google-chrome portable, although I don't recall which version of google-chrome it had built. It wouldn't register.

Which leads me to the question: Which version of Chromium did you use?

mikesLr

[Geoffrey]

@mikeslr

It works for me, battleshooter told me

If you want to test it, install everything, then Glibc last.

I'm posting this from Chromium 37, used chromium-37.0.2062.94.pet

palemoon-24.7.1.pet works too.

[mikeslr]

Hi Geoffrey,

With regard to my above post, when trying to install one of the pets seemed to hang the computer I decided it might be safer to combine all the pets into an SFS. In doing so, the pets merged with only one problem. I discovered that there are two filed named "dir" which conflict with each other. I guess I chose the wrong one to keep. But as that SFS didn't produce a viable Chromium with any of peebee's SFSes nor kost@s' pet --the one you used successfully-- which I also converted to an SFS, I went back and installed battleshooter's pets. But as I noted above, I installed gcc after glibc. My guess is that the conflicting "dir" files are in those pets, and the one in glibc must be the last installed.
I'll try again, remembering to install glibc last.

Thanks for the info.

mikesLr

[battleshooter]

Whoops, I appeared to have dropped the ball here. No more late night posts for battleshooter. (Yeah right.)

I didn't actually test Chrome Geoffrey told me 37 worked with the new glibc and I went "yay"! and then posted on the Carolina thread.

Err, so Geoffrey, did you use kost@s's or PeeBee's Chromium 37 pet?

Sorry about that mikeslr, I guess I wasn't dedicated enough to test properly

One seemed to hang up the computer.

It does seem to take awhile to install GCC in particular as it's quite large. I'm not really sure which order of pet installation is correct now. The order you installed them in sounds like the same order I currently install them in. As Geoff mentioned, I did tell him to install glibc last, but I've actually been installing glibc before GCC now because GCC is dependent on the new glibc and that seems to work for me. But why is that a problem for you Mike? I thought eventually it worked out?

I decided it might be safer to combine all the pets into an SFS.

Mike I have to say I don't think an SFS for glibc/GCC/binutils would work. In my experience SFSs don't overwrite. It's why I can't include FFMPEG in any SFS as it doesn't overwrite the existing FFMPEG. So if you tried to upgrade glibc like that, it would be unable to overwrite the existing glibc.

My guess is that the conflicting "dir" files are in those pets

I looked it up and it seems /usr/share/info/dir

part of the info documentation system. Packages must add entries to this file and not overwrite it

But that doesn't work because it's a pet... hmmm. Still, it doesn't seem important as it's only documentation so I don't think it's a source of conflict.

Thanks for all the help with testing guys.

[watchdog]

I'm testing only the glibc upgrade in my frugal install of wary 5.3 original. All seems to work. Tried in puppy4 series but the kernel 2.6.30.5 is too old. I beg your pardon for my ignorance: should gcc and other pets upgrade the devx stuff? Not tried.

[battleshooter]

I'm testing only the glibc upgrade in my frugal install of wary 5.3 original. All seems to work

Awesome! That makes sense as Racy is "Wary on steroids", but I didn't think to test that too, thanks for that

Tried in puppy4 series but the kernel 2.6.30.5 is too old

Yeah, 2.6.32 is the rock bottom kernel limit that this glibc will work with so Wary just made it.

I beg your pardon for my ignorance: should gcc and other pets upgrade the devx stuff?

Yes, but obviously it doesn't change the contents of the SFS. Whenever you run a fresh Pup install and load devx you'll need to reinstall the pets to upgrade GCC.

[dejan555]

Tried in puppy4 series but the kernel 2.6.30.5 is too old.

There's a 2.19 glibc compiled on dpup with that same kernel version here
I've never tried installing it on 4.x or installing it from pet though but I made a package anyway because whenever I change glibc I do it by replacing it in sfs and to avoid possible system lockups like someone mentioned.

@battleshooter
Do you meen that it doesn't work on older kernel because this particular package is compiled against 2.6.32 or glibc doesn't support older ones anymore generally? Because that would mean that I wouldn't be able to update to newer anymore. 2.19 is pretty recent for now though and I'll probably be keeping it for a while.

EDIT: Found out it's really the minimum kernel version that it will compile for.

[watchdog]

I'm testing only the glibc upgrade in my frugal install of wary 5.3 original. All seems to work

Awesome! That makes sense as Racy is "Wary on steroids", but I didn't think to test that too, thanks for that

I wrote too soon. I have found at least one problem: the latest googletalk plugin does not work in my frugal glibc upgraded install. I have installed an old version. Some odd behaviour in jwm and xorgwizard. More testing needed but it can work.

[watchdog]

Tried in puppy4 series but the kernel 2.6.30.5 is too old.

There's a 2.19 glibc compiled on dpup with that same kernel version here

More testing needed but your upgrade is working in a frugal install of puppy 4.31. The same problem as for glibc 2.20 in wary: the later googletalk plugins make the browser to crash and I have to use an old version. The error at crash of browser is something like:

Code: Select all

Inconsistency detected by ld.so: dl-open.c: 678: _dl_open: Assertion `_dl_debug_initialize (0, args.nsid)->r_state == RT_CONSISTENT' failed!

I used to upgrade glibc with the debian package libc6-2.11.3-4: this upgrade does not break the last googletalk.

[battleshooter]

the later googletalk plugins make the browser to crash and I have to use an old version

I've never had much luck with googletalk plugin. When ever I tested it, it would usually crash the whole browser so I'm not much help there considering I didn't have it going on a good day.

Found out it's really the minimum kernel version that it will compile for.

Yeah,

The minimum Linux kernel version that this version of the GNU C Library
can be used with is 2.6.32.

[battleshooter]

In regards to installation order of the glibc pets, I've tested it several times, and it seems as long as GCC is last installed, the installation should not hang. First post edited accordingly.

[Robert123]

Late to the party on this but running Racy Barebones and did upgrade. Fine so far.

Updated link for upgrade as link in first post is no longer working.
https://archive.org/download/Russoodles ... tleshooter

[Robert123]

Works in Wary 5.5 too.

[greengeek]

There's a 2.19 glibc compiled on dpup with that same kernel version here
I've never tried installing it on 4.x or installing it from pet though but I made a package anyway because whenever I change glibc I do it by replacing it in sfs

Hi Dejan - do you mean that you are able to install a glibc upgrade by loading an sfs? If i understood you correctly - could you post a link to an sfs or describe a HowTo for the method to build such an sfs?
cheers!

[sindi]

The Palemoon item mentions Battleships's glibc upgrade for wary so I came here, but the link for glibc pet appears no longer to work (with the Seamonkey in Wary 5.5 or Palemoon 27.9.4 in Lupu2016).

I would love to upgrade racy, wary, puppy 4.31 with 2.6 kernel, and lupu 2016 to try to get Palemoon 28 working with them. (libstdc++ upgrade also needed at least for pre-lupu puppies). I have one laptop with nvidia video that won't display readably with anything newer than lupu with 2.6 kernel.

[perdido]

Put this together as some Carolina users wanted the latest Chrome.

Tested on different kernels ranging from 3.0.66 to 3.17, Racy (3.0.66 kernel), Carolina 1.1 (standard 3.2.13 Carolina kernel), Carolina 1.2 (3.17 kernel) running applications seem to be fine, but I have not tested compiling extensively.

Glibc, GCC, and Binutils have been compiled twice (2 pass).

As glibc is a core system element I would advise testing this on a non-essential Puppy install if you're not sure what you're doing. I haven't had any problems with it, but better safe than sorry.

It seems fully backwards compatible so any programs compiled with an older glibc will work, but anything compiled with the new glibc will not work with an older glibc.

Installation order:
GCC last.

Downloads
glibc-2.20.pet 27.7 MB
gcc-4.9.2.pet 35.8 MB
binutils-2.24.pet 11.5 MB

GCC dependencies:
gmp-6.0.0.pet 636 KB
mpc-1.0.2.pet 110 KB
mpfr-3.1.2.pet 469 KB

The make check results for GCC and glibc are attached if anyone needs to see them.

Racy 5.5:

Carolina 1.1:

Carolina 1.2 with 3.17 kernel:


6/11/14 Edited: Installation order

This reply is to supply new links to the PET packages listed in the original post because original links are dead. Same exact packages - updated links.
The packages have been archived at archive.org by the puppy archive guru ally.

Downloads
glibc-2.20.pet 27.7 MB - https://archive.org/download/Russoodles ... c-2.20.pet
gcc-4.9.2.pet 35.8 MB - https://archive.org/download/Russoodles ... -4.9.2.pet
binutils-2.24.pet 11.5 MB - https://archive.org/download/Russoodles ... s-2.24.pet

GCC dependencies:
gmp-6.0.0.pet 636 KB - https://archive.org/download/Russoodles ... -6.0.0.pet
mpc-1.0.2.pet 110 KB - https://archive.org/download/Russoodles ... -1.0.2.pet
mpfr-3.1.2.pet 469 KB - https://archive.org/download/Russoodles ... -3.1.2.pet


.

[Mike Walsh]

Nice one, perdido. That's needed doing for a while.

Some time ago, I put all these items together in a tarball, along with installation instructions, simply to make the process simpler for anyone who wants to take advantage of it. You can find it here:-

https://drive.google.com/file/d/1uyjN1F ... sp=sharing

It's certainly made my own Racy 5.5 a hell of a lot more 'usable'.....and still totally viable as a 'daily driver'. I'd recommend this upgrade to any user of Racy/Wary/Carolina.


Mike.

[sindi]

ls /lib/lib*2.10.1* lists 18 libraries and ls /lib/lib*2.20* lists 19.
Is it safe to delete the 2.10.1 (original) libraries?

Is there anything else to delete after the glibc 2.20 upgrade?
I see lots of locale stuff that I doubt I will use.

Racy kernel panics on DELL Inspiron 1521.

[Mike Walsh]

@ sindi:-

Unless you're extremely 'hard-pressed' for space, I would not advise deleting the older glibc stuff. Some of the 'mastered-in' default apps, etc., are still looking for the older items.

I tried removing them myself, once upon a time, and was left with an install of Racy that refused to function properly.....so; in a nutshell.....NO.

Not if you want a functional Puppy. (*shrug*)


Mike.