From: David Leimbach <leimy2k@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Re: patch/list applied/ape-dumb-autohell-fixes
Date: Tue, 14 Feb 2006 07:53:33 -0800 [thread overview]
Message-ID: <3e1162e60602140753h6ab3b514i894a53d036339ab5@mail.gmail.com> (raw)
In-Reply-To: <43F0EA42.20406@lanl.gov>
[-- Attachment #1: Type: text/plain, Size: 942 bytes --]
>
> The reason I wanted to start with gcc 0.9, a few years ago, was that in
> the early days gcc would compile under just about any OS and C compiler
> -- the newer gcc's only seem to compile under gcc. So you start with gcc
> 0.9, get it to build under native plan 9, not APE, then bootstrap your
> way forward to current. I have no idea if this will work, but I did
> bootstrap gcc onto a lot of weird machines 15 years ago. It looks much
> harder, however, to drop gcc 4.0 onto a non-gcc-like C compiler and get
> it to go!
If this ever worked, this should still work right, just possibly with
several bootstrapped stages to get to that point.
I think the real danger in doing this is getting someone who wants to be a
GNU maintainer/defender of the Plan 9 platform. I've no interest to ever
look under the hood of the GNU compiler collection personally, but I can see
the value in having this available on Plan 9.
[-- Attachment #2: Type: text/html, Size: 1142 bytes --]
next prev parent reply other threads:[~2006-02-14 15:53 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7c5561c3fea402ccac05d5762e3d2aa7@plan9.bell-labs.com>
2006-02-13 16:17 ` uriel
2006-02-13 17:29 ` Russ Cox
2006-02-13 19:46 ` uriel
2006-02-13 15:19 ` Russ Cox
2006-02-13 19:51 ` Lyndon Nerenberg
2006-02-13 20:23 ` Ronald G Minnich
2006-02-13 20:44 ` Lyndon Nerenberg
2006-02-13 22:54 ` Ronald G Minnich
2006-02-14 15:57 ` David Leimbach
2006-02-13 20:21 ` Ronald G Minnich
2006-02-13 20:47 ` Steve Simon
2006-02-13 20:55 ` Paul Lalonde
2006-02-13 20:58 ` Steve Simon
2006-02-13 23:02 ` Ronald G Minnich
2006-02-13 21:07 ` andrey mirtchovski
2006-02-14 0:39 ` Latchesar Ionkov
2006-02-14 0:41 ` Paul Lalonde
2006-02-14 0:59 ` Latchesar Ionkov
2006-02-14 0:50 ` Joel Salomon
2006-02-14 0:53 ` Joel Salomon
2006-02-14 1:04 ` Latchesar Ionkov
2006-02-14 1:12 ` Joel Salomon
2006-02-14 9:47 ` Charles Forsyth
2006-02-14 11:37 ` Brantley Coile
2006-02-14 14:43 ` Ronald G Minnich
2006-02-14 10:12 ` Russ Cox
2006-02-14 15:10 ` Ronald G Minnich
2006-02-14 15:53 ` David Leimbach [this message]
2006-02-14 1:31 quanstro
2006-02-15 0:53 quanstro
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=3e1162e60602140753h6ab3b514i894a53d036339ab5@mail.gmail.com \
--to=leimy2k@gmail.com \
--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).