From: andrey mirtchovski <andrey@lanl.gov>
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: Mon, 13 Feb 2006 14:07:50 -0700 [thread overview]
Message-ID: <D87B7B6D-9747-418D-AD4F-B1E42FAD1892@lanl.gov> (raw)
In-Reply-To: <43F0EA42.20406@lanl.gov>
>
> I've always had the hope that we could somehow bootstrap some
> version of the gcc toolchain, get liberty up, and ease into it that
> way -- but not under APE! Try to find a way to do a native plan 9
> version of gnu tools. The reason is simple: I have lots of interest
> in Plan 9, but the code bases for the apps all need GCC/G++. This
> is a huge barrier.
>
ftp.gnu.org has 1.42 as the earliest:
# cc -g -o gccnew gcc.o version.o obstack.o alloca.o
# gccnew -v
gcc version 1.42
#
*waves at uriel*
next prev parent reply other threads:[~2006-02-13 21:07 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 [this message]
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
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=D87B7B6D-9747-418D-AD4F-B1E42FAD1892@lanl.gov \
--to=andrey@lanl.gov \
--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).