From: lucio@proxima.alt.za
To: 9fans@cse.psu.edu
Subject: [9fans] GCC etc.
Date: Thu, 21 Feb 2008 22:46:51 +0200 [thread overview]
Message-ID: <6878c6ec53332c20fd6f7c51a164cf33@proxima.alt.za> (raw)
I have made small progress getting dhog's GCC to compile itself.
Briefly, I needed a "mv" that did not barf on a "-f" option, a copy of
"head" I stole from NetBSD and a fresh version of "gmake".
I used APE, a "mkfile" and the 3.81 sources of gmake to produce
"/386/bin/gnu/make" which is an improvement on the version in the
"gnubin" archives.
I'm not sure whether anyone would actually want the "gmake" at this
stage, or later when the exercise is more advanced. If you do, let me
know, I'll dump it on sources.
++L
PS: I'm stuck with a "too big" situation right now, I'll look into it
tomorrow. I'm proceeding to stage 2, hoping to get the entire "make
bootstrap" to complete before I'm confident I can release a fresh
archive and tackle a more recent release. If anyone actually knows
what was changed in GCC to produce the archive, I could use whatever
documentation can be sent my way.
next reply other threads:[~2008-02-21 20:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-21 20:46 lucio [this message]
2008-02-22 10:02 ` Icarus Sparry
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=6878c6ec53332c20fd6f7c51a164cf33@proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).