RFC: Changing ELFOSABI_FREEBSD into ELFOSABI_SYSV/ELFOSABI_NONE

Petr Salinger Petr.Salinger at t-systems.cz
Wed Jan 4 09:56:38 UTC 2006


> > * Make changes to the kernel to execute ELFOSABI_SYSV as native.
> > * Make the Debian glibc to be able to execute both ELFOSABI_SYSV
> >   and ELFOSABI_FREEBSD. But only send the ELFOSABI_SYSV to upstream.
> > * Change binutils to use ELFOSABI_SYSV as default.

> > Even if there is a lot of drawbacks, I consider all of them as minor,
> > that's why I propose to change the OSABI in GNU/kFreeBSD.

> IMHO it's a good thing to try being "less weird" and use normal _SYSV 
> binaries, but should be done carefuly.

I agree, it will be cleaner.

> * Rebuilt all packages (it can be delayed, see below).
>
> Note that we don't break anything until we remove the compatibility
> stuff in glibc. However, users will have to upgrade their kernel before,
> or as the same time as the new glibc.

There might be problems with mixing shared libraries
and/or static libraries (object files) compiled for different OS/ABI.
This definitely needs a test.

I already went into some trouble, see 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=338603

Maybe rebuilt of all packages or carefull temporary hack
in binutils will be needed.

In the same time, we could change name of our default
program interpreter (ld.so). Its location should be unique
between all (at least Debian) ports.
See also http://www.linuxbase.org/futures/ideas/multiarch/index.html

What about /lib/ld-kfreebsd-i386.so.2 and /lib/ld-kfreebsd-amd64.so.2 ?

Petr




More information about the Glibc-bsd-devel mailing list