From: "Joseph S. Myers" <joseph@codesourcery.com>
To: "Mark Williams (MWP)" <mwp@internode.on.net>
Cc: Eric Christopher <echristo@redhat.com>,
gcc@gcc.gnu.org, Mark Mitchell <mark@codesourcery.com>,
DJ Delorie <dj@redhat.com>
Subject: Re: Error building 4.0.1-RC2
Date: Mon, 20 Jun 2005 10:56:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.61.0506201053530.6452@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20050620061224.GA22668@linux.comp>
On Mon, 20 Jun 2005, Mark Williams (MWP) wrote:
> >
> > >
> > > Yes i did... i always do and have never had a problem doing so before.
> > > I will try building in a different directory though and report back.
> >
> > http://gcc.gnu.org/install/configure.html
> >
> > To be honest I'm always surprised when it works at all.
>
> Ok, that fixed it, thanks.
>
> Maybe a warning should be included in the configure script that is shown when
> poeple do run configure from the gcc source root?
Bug 17383 is one of the more frequently reported issues with GCC 4.0.0,
but building in the source directory is not considered release-critical.
If someone wishes to submit a patch for that bug for 4.0 branch, I expect
it could be considered for 4.0.2 but might be too risky for 4.0.1 now.
--
Joseph S. Myers http://www.srcf.ucam.org/~jsm28/gcc/
jsm@polyomino.org.uk (personal mail)
joseph@codesourcery.com (CodeSourcery mail)
jsm28@gcc.gnu.org (Bugzilla assignments and CCs)
next prev parent reply other threads:[~2005-06-20 10:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-20 5:46 Mark Williams (MWP)
2005-06-20 5:50 ` Eric Christopher
2005-06-20 6:12 ` Mark Williams (MWP)
2005-06-20 10:56 ` Joseph S. Myers [this message]
2005-06-21 22:17 ` Eric Christopher
2005-06-21 22:24 ` DJ Delorie
2005-06-21 22:31 ` Eric Christopher
2005-06-21 22:44 ` Eric Christopher
2005-06-21 22:46 ` DJ Delorie
2005-06-22 14:06 ` Mark Mitchell
2005-06-23 1:09 ` Eric Christopher
-- strict thread matches above, loose matches on Subject: below --
2005-06-20 5:32 Mark Williams (MWP)
2005-06-20 5:41 ` Eric Christopher
2005-06-20 6:30 ` Ranjit Mathew
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=Pine.LNX.4.61.0506201053530.6452@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=dj@redhat.com \
--cc=echristo@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=mark@codesourcery.com \
--cc=mwp@internode.on.net \
/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).