From: C H Forsyth <forsyth@vitanuova.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: Ada for Plan9 yet?
Date: Mon, 12 May 2003 17:58:30 +0100 [thread overview]
Message-ID: <7f2c511ffa24a8d09c5e9650bb7ff5c5@vitanuova.com> (raw)
In-Reply-To: <4a4de33a.0305120603.68409800@posting.google.com>
i believe you'd need to push Ada rather than pull it to port it,
since the Ada front end is written in Ada. in other words, i believe
you need a working GNAT cross-compiling for Plan 9 on
some other system to bootstrap it. that makes it trickier,
unless the cross-compilation environment for Plan 9 from Unix
is in the Plan 9 gcc package.
next prev parent reply other threads:[~2003-05-12 16:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-09 15:38 [9fans] " Mário Amado Alves
2003-05-12 8:56 ` [9fans] " Douglas A. Gwyn
2003-05-12 9:23 ` boyd, rounin
2003-05-12 15:16 ` Mário Amado Alves
2003-05-12 15:42 ` boyd, rounin
2003-05-12 15:15 ` Mário Amado Alves
2003-05-12 15:44 ` boyd, rounin
2003-05-12 16:58 ` C H Forsyth [this message]
2003-05-12 16:58 ` boyd, rounin
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=7f2c511ffa24a8d09c5e9650bb7ff5c5@vitanuova.com \
--to=forsyth@vitanuova.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).