public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: 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
Date: Tue, 26 Nov 2002 12:46:00 -0000	[thread overview]
Message-ID: <20021119195857.8411.qmail@sources.redhat.com> (raw)

Synopsis: config.if (gcc 2.95.2, possibly others) pukes if it can't find gl*bc

State-Changed-From-To: feedback->analyzed
State-Changed-By: bangerth
State-Changed-When: Tue Nov 19 11:58:57 2002
State-Changed-Why:
    Still happens.

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


             reply	other threads:[~2002-11-19 19:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-26 12:46 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 Wolfgang 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=20021119195857.8411.qmail@sources.redhat.com \
    --to=bangerth@dealii.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=orc@pell.chi.il.us \
    /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).