public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@sunsite.dk>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] PROPOSED: 32/64 bit coexistance
Date: Tue, 18 Sep 2001 08:54:35 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590698805201@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805193@msgid-missing>

>>>>> "David" = David Mosberger <davidm@hpl.hp.com> writes:

>>>>> On Mon, 17 Sep 2001 10:02:14 -0600, Doug Beattie <dbb@caldera.com> said:
Doug> Your reponse is welcome and invited.  The LSB and FHS groups are
Doug> trying to better address the coexistance of 32 and 64 bit in the
Doug> 64 bit Itanium environment.

Doug> Please review the following proposal and respond to the
Doug> "lsb-spec@lists.linuxbase.org" and
Doug> "lsb-discuss@lists.linuxbase.org" mail lists.

David> When will people learn that for Linux, source compatibility is
David> just as important as binary compatibility?  For IA-64 Linux,
David> the decision was made that native libraries go into /lib etc
David> and that legacy libraries go somewhere else
David> (/usr/i386-*-linux/lib, commonly).

Not to mention that ld.so has already been fixed to handle searching
through library directories containing libraries for a different
architecture than ld.so is running on itself. Hence the whole point of
ia32 binaries being unable to cope with ia64 binaries in /lib is
completely useless.

It would have been extremely nice if the people who decided to write
this standard had started out by asking the people who did the
implementation work how the architecture really works and what
experience has been gained in these areas already.

Jes


  parent reply	other threads:[~2001-09-18  8:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-17 16:02 [Linux-ia64] PROPOSED: 32/64 bit coexistance Doug Beattie
2001-09-17 16:53 ` David Mosberger
2001-09-18  8:54 ` Jes Sorensen [this message]
2001-09-18  9:03 ` Lenz Grimmer
2001-09-18  9:03 ` Andreas Jaeger
2001-09-18  9:12 ` Ulrich Drepper

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-linux-ia64-105590698805201@msgid-missing \
    --to=jes@sunsite.dk \
    --cc=linux-ia64@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox