[1090] in SIPB_Linux_Development
Re: ELF migration. (Go lemmings go!)
daemon@ATHENA.MIT.EDU (Derek Atkins)
Fri Oct 6 15:07:39 1995
To: Erik Nygren <nygren@MIT.EDU>
Cc: "Theodore Ts'o" <tytso@MIT.EDU>, Jered J Floyd <jered@MIT.EDU>,
Derek Atkins <warlord@MIT.EDU>, eichin@MIT.EDU, linux-dev@MIT.EDU
In-Reply-To: Your message of "Fri, 06 Oct 1995 01:39:25 EDT."
<199510060539.BAA27188@foundation.mit.edu>
Date: Fri, 06 Oct 1995 15:05:21 EDT
From: Derek Atkins <warlord@MIT.EDU>
> Will people need to update the a.out shared library and thus gcc
> to upgrade to ELF. I remember H Lu's announcement saying that
> if you wanted to run 5.x you needed 4.7.x as the a.out libraries
> which in turn needed the new gcc. Is this true or not?
This is not true. I installed the minimal amount of ELF support on
my machine at home. I needed to:
install the ELF libc (5)
install updated ld.so, ld-linux.so, ldd, ldconfig
run ldconfig
Thats it. No changes to gcc. No changes to the a.out libc. No
changes to anything else.
I cannot _build_ ELF on this machine, but I can _run_ ELF, which
is enough.
> I think the best approach is to provide an install script which:
> 1) creates /lib/elf (optionally as a symlink into AFS for
> people really low on disk space)
> 2) installs the 5.x and elf X11 shared libs there
> 3) installs the new ld.so
> 4) updates ld.so.config to look in /lib/elf
This is 100% EXACTLY what I had in mind.
-derek
