From: Joe Buck <jbuck@synopsys.COM>
To: janis187@us.ibm.com (Janis Johnson)
Cc: shannonk@cse.unsw.edu.au (Shannon Koh), gcc@gcc.gnu.org
Subject: Re: Successful Build of GCC 3.0.1
Date: Wed, 19 Sep 2001 11:18:00 -0000 [thread overview]
Message-ID: <200109191814.LAA15153@atrus.synopsys.com> (raw)
In-Reply-To: <20010919095219.A1301@us.ibm.com>
> On Wed, Sep 19, 2001 at 12:05:05PM +1000, Shannon Koh wrote:
> > Hi,
> >
> > I'm running WinLinux 2001 (currently identified as i386-redhat-linux-gnu),
> > which I've obtained from http://www.winlinux.net , and have successfully
> > built GCC 3.0.1 today.
>
> Thanks! I've added "i386-redhat-linux-gnu" to the GCC 3.0 build status
> page at http://gcc.gnu.org/gcc-3.0/buildstat.html .
You'll need to add more than that, Janet, since this system does not
correctly identify itself (it is not Red Hat, it is "WinLinux").
next prev parent reply other threads:[~2001-09-19 11:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-18 19:05 Shannon Koh
2001-09-19 9:50 ` Janis Johnson
2001-09-19 11:18 ` Joe Buck [this message]
2001-09-19 11:50 ` Joe Buck
2001-09-21 16:03 ` Janis Johnson
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=200109191814.LAA15153@atrus.synopsys.com \
--to=jbuck@synopsys.com \
--cc=gcc@gcc.gnu.org \
--cc=janis187@us.ibm.com \
--cc=shannonk@cse.unsw.edu.au \
/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).