From: "Paul J.Y. Lahaie" <pjlahaie@atlsci.com>
To: hppa-linux@puffingroup.com
Subject: Re: [hppa-linux] egcs and binutils cross compiling
Date: Fri, 19 Feb 1999 08:48:32 -0500 [thread overview]
Message-ID: <36CD6BB0.CF02D28A@atlsci.com> (raw)
In-Reply-To: m10Dmte-0007U1C@the-village.bc.nu
Alan Cox wrote:
>
> > Also, Paul is changing the ELF header structure significantly between
> > mklinux and *real* linux, so we're getting close to having to just abandon
> > all of mklinux.
>
> Write an mklinux binary loader bfore you do that. Having a mostly functional
> user space while doing kernel hacks, and being able to use mklinux to mend
> the result of failed native kernels is a large win
The current idea is that we will make the kernel data structures as
close to HP-UX as possible so future HP-UX compatibility is possible.
If we go the MkLinux binary loader route then we'll be stuck making our
kernel structures MkLinux like or writing an emulation layer. I'm no
ELF expert, but at least the MkLinux stuff seems easy, the
binary is mapped from beginning to end. Sections aren't mapped at
different addresses (as other archs seem to do).
- Paul
----------------------------------------------------------------------
To unsubscribe: send e-mail to hppa-linux-request@puffingroup.com with
`unsubscribe' as the subject.
next prev parent reply other threads:[~1999-02-19 13:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-18 15:40 [hppa-linux] egcs and binutils cross compiling Jason Eckhardt
1999-02-19 7:15 ` Alex deVries
1999-02-19 10:10 ` Alan Cox
1999-02-19 13:48 ` Paul J.Y. Lahaie [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-02-21 16:26 Smith, Todd
1999-02-20 17:29 Smith, Todd
1999-02-20 17:51 ` Paul J.Y. Lahaie
1999-02-18 7:00 Alex deVries
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=36CD6BB0.CF02D28A@atlsci.com \
--to=pjlahaie@atlsci.com \
--cc=hppa-linux@puffingroup.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.