public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ryan Johnson <ryan.johnson@cs.utoronto.ca>
To: Dennis Clarke <dclarke@blastwave.org>
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:25:00 -0000	[thread overview]
Message-ID: <50AD1C8D.2050400@cs.utoronto.ca> (raw)
In-Reply-To: <fb7396bd25f3.50accac2@blastwave.org>

On 21/11/2012 12:36 PM, Dennis Clarke wrote:
> gmake[4]: Entering directory `/usr/local/build/gcc-4.7.2_SunOS5.10_sparcv9.002/lto-plugin'
> /opt/csw/bin/bash ./libtool --tag=CC --tag=disable-static  --mode=compile gcc -m64 -g -DHAVE_CONFIG_H -I. -I../../gcc-4.7.2/lto-plugin  -I../../gcc-4.7.2/lto-plugin/../include -DHAVE_CONFIG_H -I/usr/local/include -Wall -g -fkeep-inline-functions -c -o lto-plugin.lo ../../gcc-4.7.2/lto-plugin/lto-plugin.c
> ./libtool: line 519: CDPATH: command not found
> ./libtool: line 923: libtool: ignoring unknown tag disable-static: command not found
> libtool: Version mismatch error.  This is libtool 2.2.7a, but the
> libtool: definition of this LT_INIT comes from an older release.
> libtool: You should recreate aclocal.m4 with macros from libtool 2.2.7a
> libtool: and run autoconf again.
> gmake[4]: *** [lto-plugin.lo] Error 63
> gmake[4]: Leaving directory `/usr/local/build/gcc-4.7.2_SunOS5.10_sparcv9.002/lto-plugin'
> gmake[3]: *** [all] Error 2
> gmake[3]: Leaving directory `/usr/local/build/gcc-4.7.2_SunOS5.10_sparcv9.002/lto-plugin'
> gmake[2]: *** [all-stage1-lto-plugin] Error 2
> gmake[2]: *** Waiting for unfinished jobs....

> So here we see some complaint about libtool of all things.
That's a pretty actionable error message... which I have to assume you 
did not act on before posting, based on available information.

Please perform basic debuggery before spamming the list. Even if it 
turns out to be a gcc problem, it takes longer to compose the message 
than to fix things like this, and delivering a compiled list of 
workarounds at the end is far more useful to everyone (including you if 
you ever need to do this again) than a bunch of screen dumps showing 
basic error messages.

Ryan

P.S. This message and the previous hint pretty strongly that you've got 
some messed up paths and/or package installs that have little or nothing 
to do with gcc, other than perhaps the latter requiring non-braindead 
versions of grep/sed/etc.

  reply	other threads:[~2012-11-21 18:25 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 [this message]
2012-11-21 18:17     ` Ryan Johnson
2012-11-21 18:24       ` Dennis Clarke
  -- 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=50AD1C8D.2050400@cs.utoronto.ca \
    --to=ryan.johnson@cs.utoronto.ca \
    --cc=dclarke@blastwave.org \
    --cc=ebotcazou@adacore.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=iant@google.com \
    --cc=jwakely.gcc@gmail.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).