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/2236: config.if (gcc 2.95.2, possibly others) pukes if it can't find gl*bc
Date: Tue, 26 Nov 2002 12:46:00 -0000 [thread overview]
Message-ID: <20021119200602.10911.qmail@sources.redhat.com> (raw)
The following reply was made to PR bootstrap/2236; it has been noted by GNATS.
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: gcc-gnats@gcc.gnu.org
Cc:
Subject: Re: bootstrap/2236: config.if (gcc 2.95.2, possibly others) pukes
if it can't find gl*bc
Date: Tue, 19 Nov 2002 14:04:23 -0600 (CST)
---------- Forwarded message ----------
Date: Tue, 19 Nov 2002 10:42:40 -0800 (PST)
From: david parsons <orc@pell.portland.or.us>
To: bangerth@dealii.org
Cc: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
orc@pell.chi.il.us
Subject: Re: bootstrap/2236: config.if (gcc 2.95.2,
possibly others) pukes if it can't find gl*bc
bangerth@dealii.org wrote:
>
> Synopsis: config.if (gcc 2.95.2, possibly others) pukes if it can't find gl*bc
>
> State-Changed-From-To: open->feedback
> State-Changed-By: bangerth
> State-Changed-When: Tue Nov 19 07:58:44 2002
> State-Changed-Why:
> This is a rather old bootstrap error. Can you say whether this
> still happens with newer versions of gcc?
Yes.
orc@pell$ CC="cc -baout" ./configure
Configuring for a i686-pc-linux-gnuaout host.
Created "Makefile" in /home/orc/gcc-3.2 using "mt-frag"
Cannot find the GNU C library minor version number.
-david parsons "I don't even use gl*bc on my systems"
next reply other threads:[~2002-11-19 20:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-26 12:46 Wolfgang Bangerth [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-21 9:56 ehrhardt
2003-05-21 8:16 Dara Hazeghi
2002-11-27 7:14 Joseph S. Myers
2002-11-26 13:06 Wolfgang Bangerth
2002-11-26 12:46 bangerth
2002-11-26 2:26 bangerth
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=20021119200602.10911.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).