public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: neil@gcc.gnu.org
To: anonymous@sourceware.cygnus.com, gcc-bugs@gcc.gnu.org,
gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, rodrigc@gcc.gnu.org,
q@ping.be
Subject: Re: other/3342: Build 3.0 on Linux-glibc1 fails: undefined reference to `_IO_2_1_stdout_'
Date: Mon, 07 Jan 2002 04:13:00 -0000 [thread overview]
Message-ID: <20020107121317.31592.qmail@sources.redhat.com> (raw)
Synopsis: Build 3.0 on Linux-glibc1 fails: undefined reference to `_IO_2_1_stdout_'
State-Changed-From-To: feedback->closed
State-Changed-By: neil
State-Changed-When: Mon Jan 7 04:13:16 2002
State-Changed-Why:
No feedback.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=3342
next reply other threads:[~2002-01-07 12:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-07 4:13 neil [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-08-18 9:47 rodrigc
2001-06-21 11:26 anonymous
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=20020107121317.31592.qmail@sources.redhat.com \
--to=neil@gcc.gnu.org \
--cc=anonymous@sourceware.cygnus.com \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc-gnats@gcc.gnu.org \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@gcc.gnu.org \
--cc=q@ping.be \
--cc=rodrigc@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).