public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: rodrigc@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
	rodrigc@gcc.gnu.org, steven.sabean@sun.com
Subject: Re: bootstrap/5167: gcc-3.0.2 fails to bootstrap on Solaris 2.6
Date: Tue, 01 Jan 2002 15:56:00 -0000	[thread overview]
Message-ID: <20020101235621.28905.qmail@sources.redhat.com> (raw)

Synopsis: gcc-3.0.2 fails to bootstrap on Solaris 2.6

State-Changed-From-To: open->feedback
State-Changed-By: rodrigc
State-Changed-When: Tue Jan  1 15:56:20 2002
State-Changed-Why:
    We have successful bootstrap reports on Solaris 2.6 here:
    http://gcc.gnu.org/gcc-3.0/buildstat.html
    
    Can you follow the instructions at:
    http://gcc.gnu.org/install/specific.html#*-*-solaris2*
    
    and set the CONFIG_SHELL environment variable to
    /bin/ksh and re-running the make?
    
    According the make.log file you submitted, there are
    other instances in the gcc build where libtool --tag
    is used without failure.  I suspect that in the boehm-gc
    part of the build, it is using the wrong libtool
    (ie. one installed on your system, instead of the one that
    is built with gcc).
    
    This problem may be occurring because of some incompatibilities
    in the gcc makefiles with the default Bourne shell on
    Solaris.
    
    Can you let me know if this helps?

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5167


             reply	other threads:[~2002-01-01 23:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-01 15:56 rodrigc [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-03-21 16:06 Steven Sabean
2002-03-21 15:46 Craig Rodrigues
2002-03-21 14:26 Steven Sabean
2002-03-03 10:49 rodrigc
2002-01-07 12:46 Steven Sabean
2001-12-20 11:46 steven.sabean

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=20020101235621.28905.qmail@sources.redhat.com \
    --to=rodrigc@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=steven.sabean@sun.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).