All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <Matthew.Wilcox@genedata.com>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: Alex deVries <adevries@thepuffingroup.com>,
	parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] It's finally sunk in: bye bye elf32
Date: Mon, 14 Jun 1999 10:42:28 +0200	[thread overview]
Message-ID: <19990614104228.F31472@mencheca.ch.genedata.com> (raw)
In-Reply-To: <199906131702.NAA28988@hiauly1.hia.nrc.ca>; from John David Anglin on Sun, Jun 13, 1999 at 01:02:58PM -0400

On Sun, Jun 13, 1999 at 01:02:58PM -0400, John David Anglin wrote:
> > So, I'm going to spend some time making the kernel build on HPUX.  I
> > know there's quite a few changes to make.  But I'll keep the elf
> > specific work, it'll help later on.
> 
> The discussion about the merits/limitations of SOM and ELF over the
> last couple of days has been extremely useful.  As Alex says, there is
> a lot of work to be done on the kernel before it is usable.  However,
> in the long run, the port must be a complete self contained system.
> That is, it must support a linker capable of generating executables
> and the kernel.

[...]

> If this does not work out, then we must fall back to ELF32 and devote
> enough effort to get elf32-hppa working at an acceptable level.

The long term goal is to support:

 * HP-UX binaries
 * parisc/elf32 Linux binaries
 * parisc/elf64 Linux binaries (on parisc 2.0 hardware)

The binfmt_som kernel support is necessary in both the short term (to
get a working shell for free) and long term which is why I decided to
do it first.  Once the kernel is built, we can then run the HPUX linker
on it, but we have a `small' bootstrap problem.  As Jeff says though,
it's worth throwing away the whole of parisc/elf32 and starting again
from scratch.  We were just hoping to not have to do that for a while..

-- 
Matthew Wilcox <willy@bofh.ai>
"Windows and MacOS are products, contrived by engineers in the service of
specific companies. Unix, by contrast, is not so much a product as it is a
painstakingly compiled oral history of the hacker subculture." - N Stephenson

      parent reply	other threads:[~1999-06-14  8:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-06-13  0:01 [parisc-linux] It's finally sunk in: bye bye elf32 Alex deVries
1999-06-13 17:02 ` John David Anglin
1999-06-14  6:29   ` Jeffrey A Law
1999-06-14  8:42   ` Matthew Wilcox [this message]

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=19990614104228.F31472@mencheca.ch.genedata.com \
    --to=matthew.wilcox@genedata.com \
    --cc=adevries@thepuffingroup.com \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=parisc-linux@thepuffingroup.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.