From: Mike Stump <mrs@apple.com>
To: Robert Dewar <dewar@adacore.com>
Cc: Nathan Sidwell <nathan@codesourcery.com>,
j_f@laposte.net, Zack Weinberg <zack@codesourcery.com>,
list gcc <gcc@gcc.gnu.org>
Subject: Re: native gcc for vxworks
Date: Tue, 07 Dec 2004 21:37:00 -0000 [thread overview]
Message-ID: <9846F6F9-3CC8-40BC-BA5A-2FA14B118587@apple.com> (raw)
In-Reply-To: <41B55331.1080506@adacore.com>
On Dec 6, 2004, at 10:52 PM, Robert Dewar wrote:
> I trust the small here is meant with a sense of irony, since this would
> in practice be many person years of work I would guess.
No, it isn't that hard, probably take a few weeks.
cygwin is a lot of work, not because of gcc, but because of the 1000s
of other software packages it compiles.
next prev parent reply other threads:[~2004-12-07 21:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-02 21:16 jf
2004-12-02 22:14 ` Zack Weinberg
2004-12-06 15:07 ` Jean-François Morcillo
2004-12-06 15:11 ` Nathan Sidwell
2004-12-06 15:34 ` Jean-François Morcillo
2004-12-07 6:52 ` Robert Dewar
2004-12-07 21:37 ` Mike Stump [this message]
2004-12-08 1:00 ` Robert Dewar
2004-12-08 1:09 ` Mike Stump
2004-12-08 1:27 ` DJ Delorie
2004-12-08 19:58 ` jf
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=9846F6F9-3CC8-40BC-BA5A-2FA14B118587@apple.com \
--to=mrs@apple.com \
--cc=dewar@adacore.com \
--cc=gcc@gcc.gnu.org \
--cc=j_f@laposte.net \
--cc=nathan@codesourcery.com \
--cc=zack@codesourcery.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).