Re: -= PROPOSAL =- Release sarge with amd64
Steve Langasek <vorlon@debian.org> writes:
> On Fri, Jul 16, 2004 at 11:38:37AM +0200, Goswin von Brederlow wrote:
>> Steve Langasek <vorlon@debian.org> writes:
>>
>> > On Fri, Jul 16, 2004 at 03:32:15AM +0200, Goswin von Brederlow wrote:
>> >> Also I think amd64 is compatible but not compliant to i386 and amd64
>> >> LSB. Meaning ia32 and amd64 LSB compliant programs will run on
>> >> pure64. But ia32 binaries (which you can't even build) or amd64
>> >> libraries from pure64 might not run on an ia32 compliant system
>> >> (library debs don't install into an lsb compliant palce on non
>> >> debian).
>
>> > Isn't the build-time specification of the linker path an important part
>> > of the LSB ABI? Has amd64 really addressed this?
>
>> Library path during building can be all over the place. They can be in
>> /lib, /usr/lib, /usr/X11R6/lib, /usr/local/lib, /opt/lib, ~/lib/ and
>> countles other places. Setting any kind of fixed path is unworkable.
>
> Um, what? I was asking about how amd64 is handling the locations of the
> runtime linkers (which is /lib/ld-linux.so et al.), which absolutely
> *does* have a fixed path because it's hard-coded into every executable.
> If the /lib <-> /lib64 causes a collision between /lib/ld-lsb.so and
> /lib64/ld-lsb.so, I don't see how you can claim that the amd64 port is
> "compatible [...] to i386 and amd64 LSB".
The ld.so names differ for ia32 and amd64. Hence they can reside in
the same directory with lib and lib64 being linked to the same dir.
We are lucky there. Both the ia32 and amd64 ld are reachable through
the fixed path the LSB requires (if ia32-libs is istalled to provide
the ia32 ld).
> --
> Steve Langasek
> postmodern programmer
MfG
Goswin
Reply to: