From: Andrew Haley <aph-gcc@littlepinkcloud.COM>
To: "Bill McEnaney" <bill@rkirkpat.net>
Cc: gcc-help@gcc.gnu.org
Subject: Re: building gcc 4.2.0
Date: Thu, 31 May 2007 17:38:00 -0000 [thread overview]
Message-ID: <18015.1682.529158.807205@zebedee.pink> (raw)
In-Reply-To: <20070531170619.E44A071A4E@saratoga.rkirkpat.net>
Bill McEnaney writes:
> Gcc 4.2.0's C compiler works, but while Tamino built gcc, "he"
> complained about something recursive. From what I've read on the
> web, the complaint is about Java. Does anybody know what I need to
> do to make each part of gcc 4.2.0 build cleanly?
It should build as it is. Let us know if anything fails.
Andrew.
next prev parent reply other threads:[~2007-05-31 17:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-31 17:32 Bill McEnaney
2007-05-31 17:38 ` Andrew Haley [this message]
2007-05-31 17:49 Bill McEnaney
2007-05-31 23:06 ` Andrew Haley
2007-05-31 23:16 Bill McEnaney
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=18015.1682.529158.807205@zebedee.pink \
--to=aph-gcc@littlepinkcloud.com \
--cc=bill@rkirkpat.net \
--cc=gcc-help@gcc.gnu.org \
/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).