public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: bootstrap/9889: installation gcc 3.2.2 fails on Solaris 2.8
Date: Thu, 13 Mar 2003 23:06:00 -0000 [thread overview]
Message-ID: <20030313230600.25394.qmail@sources.redhat.com> (raw)
The following reply was made to PR bootstrap/9889; it has been noted by GNATS.
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: Kinh Nguyen <xkinh@yahoo.com>
Cc: "Steven M. Christensen" <steve@smc.vnet.net>, <gcc-bugs@gcc.gnu.org>,
<gcc-gnats@gcc.gnu.org>
Subject: Re: bootstrap/9889: installation gcc 3.2.2 fails on Solaris 2.8
Date: Thu, 13 Mar 2003 17:05:11 -0600 (CST)
> I am using GCC version 2.8.1. When GCC compiles
> under sub directory
> ../sparc-sun-solaris2.8/libstdc++-v3 I believe it runs
> configure command. The configure program looks for
> Thead mode using the following statements:
> ------
> echo $ac_n "checking for thread model used by
> GCC""... $ac_c" 1>&6
> echo "configure:3868: checking for thread model used
> by GCC" >&5
> target_thread_file=`$CC -v 2>&1 | sed -n 's/^Thread
> model: //p'`
> echo "$ac_t""$target_thread_file" 1>&6
> ----------
> In the old version of GCC (version 2.8.1), gcc -v
> doesn't display line "Thread Mode" so configure
> program aborts.
configure should pick up the newly built gcc here, not the one that is
already installed (libstdc++ should be compiled by the just bootstrapped
compiler). I guess at the point where configure is invoked, some flag
should be passed, but I don't know anything about the libstdc++ build
machinery, to be honest.
W.
-------------------------------------------------------------------------
Wolfgang Bangerth email: bangerth@ticam.utexas.edu
www: http://www.ticam.utexas.edu/~bangerth/
next reply other threads:[~2003-03-13 23:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-13 23:06 Wolfgang Bangerth [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-15 7:27 ebotcazou
2003-05-09 23:06 Dara Hazeghi
2003-03-14 13:26 Kinh Nguyen
2003-03-14 8:16 Eric Botcazou
2003-03-13 21:36 Kinh Nguyen
2003-03-12 23:16 Steven M. Christensen
2003-03-12 23:06 ebotcazou
2003-03-12 22:08 bangerth
2003-03-12 14:36 Wolfgang Bangerth
2003-03-12 13:36 Kinh Nguyen
2003-03-07 0:22 bangerth
2003-02-28 18:16 xkinh
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=20030313230600.25394.qmail@sources.redhat.com \
--to=bangerth@ticam.utexas.edu \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).