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, george@navi.com.ua,
	nobody@gcc.gnu.org
Subject: Re: c/7431: Compile glibc-2.2.5
Date: Fri, 25 Oct 2002 07:05:00 -0000	[thread overview]
Message-ID: <20021025140528.1639.qmail@sources.redhat.com> (raw)

Synopsis: Compile glibc-2.2.5

State-Changed-From-To: open->closed
State-Changed-By: bangerth
State-Changed-When: Fri Oct 25 07:05:27 2002
State-Changed-Why:
    I cannot compile the file, since it is not preprocessed and
    some headers are missing. But c/7464 says that the reports are
    duplicates, so refer to that one.
    
    George, if you think the reports are about something 
    different, please send preprocessed sources and the report
    can be reopened.

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


             reply	other threads:[~2002-10-25 14:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-25  7:05 bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-07-29  4:36 george

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=20021025140528.1639.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=george@navi.com.ua \
    --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).