From: "Paul J.Y. Lahaie" <pjlahaie@atlsci.com>
To: hppa-linux@puffingroup.com
Subject: [hppa-linux] egcs / binutils x-compiler status
Date: Tue, 09 Feb 1999 18:34:04 -0500 [thread overview]
Message-ID: <36C0C5EC.D2057CEC@atlsci.com> (raw)
Earlier today I managed to get my first hppa-elf binary generated.
I'm currently in the position to attempt patching the egcs build
environment to properly handle
both libmilli.a (which I believe for cross-compiling purposes should be
libgcc1.a)
and crt0.o which is required to define $global$ and $START$ symbols. I
hope to
have everything wrapped up tonight or tomorrow so everyone can start
building
hppa-elf binaries (especially kernel bins :-) ).
If anyone wants to give me any pointers on how to go about putting
those
things in the egcs build tree, feel free, it would be greatly
appreciated.
Also, since I didn't patch the ld scripts in the way MkLinux did,
I'm not
sure what the status of the resulting bins will be. I'm attempting to
stray
the least from the standard hppaelf target, which I believe will be a
win in
the future.
- Paul
----------------------------------------------------------------------
To unsubscribe: send e-mail to hppa-linux-request@puffingroup.com with
`unsubscribe' as the subject.
reply other threads:[~1999-02-09 23:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=36C0C5EC.D2057CEC@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.