public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: hp@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, hp@gcc.gnu.org,
nobody@gcc.gnu.org, peb@mppmu.mpg.de
Subject: Re: bootstrap/8122: severe build problems for i586-pc-linux-gnulibc1
Date: Thu, 24 Oct 2002 16:58:00 -0000 [thread overview]
Message-ID: <20021024235822.12422.qmail@sources.redhat.com> (raw)
Synopsis: severe build problems for i586-pc-linux-gnulibc1
Responsible-Changed-From-To: unassigned->hp
Responsible-Changed-By: hp
Responsible-Changed-When: Thu Oct 24 16:58:22 2002
Responsible-Changed-Why:
(Wow, a 2.4.x kernel but using glibc1 headers!)
I have a fix applied to main trunk,
and will nag the 3.2 release maintainer.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8122
next reply other threads:[~2002-10-24 23:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-24 16:58 hp [this message]
2003-03-11 16:56 ebotcazou
2003-03-11 17:36 Hans-Peter Nilsson
2003-03-11 22:56 Eric Botcazou
2003-03-11 23:36 Hans-Peter Nilsson
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=20021024235822.12422.qmail@sources.redhat.com \
--to=hp@gcc.gnu.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=peb@mppmu.mpg.de \
/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).