3 ms·
I remember using Linux with libc.so.4 & .5 (which were not based on glibc code). libc 4 used a pre-ELF scheme called a.out, and libc 5 used ELF. When Linux di
by rwmj 5y ago
I remember using Linux with libc.so.4 & .5 (which were not based on glibc code). libc 4 used a pre-ELF scheme called a.out, and libc 5 used ELF. When Linux distros started to adopt GNU libc 2.x, the soname was 6 (to be obviously higher than previous versions) and they promised the new ELF symbol versioning scheme which meant that the version number would never have to change again. So here we are.
- marcodiego 5y agoI've been using linux since late 90's and the only related thing I remember was to have to install an "old" libc to be able to run kylix. Do you have more info on this event? Seems to have completely vanished from my memory.
- rwmj 5y agoI guess you may not remember the a.out to ELF transition, which was a "Big Bang" event. Before ELF, shared libraries did not use position independent code and so load addresses had to be globally coordinated (with extra space left for a library to grow in size!). That was libc.so.4 (old libc, a.out) -> libc.so.5 (old libc, ELF) and Linux 1.2. I don't recall if there were libc < 4. Google says this happened in around 1995. The libc.so.5 (old libc, ELF) to libc.so.6 (glibc 2.0) transition happened a little later in 1997.
- marcodiego 5y agoI remember the a.out to elf transition because the first distro I used had Doom in its repos. When I installed it complained that a.out format wasn't supported anymore. IIRC I tried kylix in 1999. It still requiring libc5 is strange. Well... those were not best inprise/borland days indeed.
- yjftsjthsd-h 5y ago> I remember using Linux with libc.so.4 & .5 (which were not based on glibc code). What libc implementation was that, then? I thought glibc was the first to support Linux.
- asveikau 5y agoThis hasn't been a thing since the late 90s. Linux used to use a fork of an earlier, pre-linux gnu libc. Glibc2 was a big release where upstream gnu libc was what Linux distros used for the first time. Despite being version 2.0, they set the so version to 6 because the Linux specific fork had reached version 5. That is why libc6 is synonymous with glibc2. Here is what I found on Google trying to confirm these memories: https://lwn.net/Articles/417848/ https://lwn.net/Articles/417848/ There were other examples from the gnu world where an experimental fork ends up with rapid development and then gets superseded by an upstream release. Egcs vs gcc is another I remember from that time period.
- rwmj 5y agoSo apparently Linux libc (ie. soname 4 & 5) was a fork of glibc 1.0: https://man.archlinux.org/man/glibc.7#Linux_libc https://man.archlinux.org/man/glibc.7#Linux_libc