libc update progress?

Andreas Hauser andy at splashground.de
Sun May 1 13:57:54 PDT 2005


joerg wrote @ Sat, 30 Apr 2005 20:55:36 +0200:
> On Sat, Apr 30, 2005 at 06:39:43PM +0000, Rahul Siddharthan wrote:
> > 
> > Joerg Sonnenberger <joerg at xxxxxxxxxxxxxxxxx> wrote:
> > >Please, not another compat. We can build them as tarball
> > >and put that on the webside, or even as package for use with pkg_add.
> > 
> > One of the big advantages FreeBSD has over Linux is that old binaries
> > don't break when you upgrade libc.  No pkg-add'ing or RTFM'ing or
> > any voodoo needed.  Let's not change that.  Many DragonFly users are
> > former FreeBSD users. 
> 
> I don't remove the old libc and I'm not going to do that. It will
> be moved away from /usr/lib into /usr/lib/compat or so, but not yet.
> If you install a new world, you don't have the old libs, which means
> you can't simply use e.g. gobsd's packages. That's what the compat
> package is meant for. This is the same way as FreeBSD handles it BTW.

Btw. i have both libc.so.4 and libc.so.5 packages on ftp.fortunat.net.

libc.so.4 with gcc2 (not many):
http://ftp.fortunaty.net/DragonFly/inofficial/ports-packages-libc.so.4-gcc2/

libc.so.4 with gcc34 (not updated anymore)
http://ftp.fortunaty.net/DragonFly/inofficial/ports-packages-libc.so.4-gcc34/

libc.so.5 with gcc34 (maintained):
http://ftp.fortunaty.net/DragonFly/inofficial/ports-packages-libc.so.5-gcc34/

Andy





More information about the Kernel mailing list