public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Dennis Clarke <dclarke@blastwave.org>
To: Ryan Johnson <ryan.johnson@cs.utoronto.ca>
Cc: Eric Botcazou <ebotcazou@adacore.com>,
	gcc-help@gcc.gnu.org, iant@google.com, jwakely.gcc@gmail.com
Subject: Re: gcc 4.7.2 fails to bootstrap in stage 1
Date: Wed, 21 Nov 2012 18:24:00 -0000	[thread overview]
Message-ID: <fba9fcfd4fba.50acd5ff@blastwave.org> (raw)
In-Reply-To: <50AD1AA7.3020407@cs.utoronto.ca>


> > So I think the issue may be in the GNU stack that I have built, 
> though I know not where.
> You might try looking in config.log, which would contain the actual 
> error message and could easily point to something mundane (like a 
> broken 
> sed or grep).

I doubt it is grep .. we fixed that thing yesterday : 

http://lists.gnu.org/archive/html/bug-grep/2012-11/msg00012.html

I only point this out because GNU stack items are broken all over the place regardless if 
you look at grep or flex or libtool or whatever. One has to wonder really. 

Dennis 

  reply	other threads:[~2012-11-21 18:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-21  2:35 Dennis Clarke
2012-11-21  8:07 ` Eric Botcazou
2012-11-21 16:41   ` Dennis Clarke
2012-11-21 17:36     ` Dennis Clarke
2012-11-21 18:25       ` Ryan Johnson
2012-11-21 18:17     ` Ryan Johnson
2012-11-21 18:24       ` Dennis Clarke [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-11-17 22:02 A not so stellar result on Solaris 10 Dennis Clarke
2012-11-17 23:41 ` Eric Botcazou
2012-11-20  6:07   ` gcc 4.7.2 fails to bootstrap in stage 1 Dennis Clarke
2012-11-20  8:31     ` Eric Botcazou
2012-11-20 17:47       ` Dennis Clarke

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=fba9fcfd4fba.50acd5ff@blastwave.org \
    --to=dclarke@blastwave.org \
    --cc=ebotcazou@adacore.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=iant@google.com \
    --cc=jwakely.gcc@gmail.com \
    --cc=ryan.johnson@cs.utoronto.ca \
    /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).