public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: rodrigc@gcc.gnu.org
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: bootstrap/4281: GLIBC 2.2.4 does not match with GCC 2.95.3 on compile time
Date: Sat, 01 Dec 2001 20:06:00 -0000	[thread overview]
Message-ID: <20011202040600.16662.qmail@sourceware.cygnus.com> (raw)

The following reply was made to PR bootstrap/4281; it has been noted by GNATS.

From: rodrigc@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org,
  k997@korea.com, nobody@gcc.gnu.org
Cc:  
Subject: Re: bootstrap/4281: GLIBC 2.2.4 does not match with GCC 2.95.3 on compile time
Date: 2 Dec 2001 04:03:42 -0000

 Synopsis: GLIBC 2.2.4 does not match with GCC 2.95.3 on compile time
 
 State-Changed-From-To: open->closed
 State-Changed-By: rodrigc
 State-Changed-When: Sat Dec  1 20:03:41 2001
 State-Changed-Why:
     This is a known problem.  gcc 2.95.3 will not compile
     with gcc 2.96 + glibc 2.2.4 under Redhat 7.1.
     
     What you need to do is install the kgcc package which
     comes with Redhat Linux.  That is an older version of gcc.
     Compile gcc 2.95.3 with kgcc on Redhat Linux 7.1 and you
     should be fine.
     
     See:
     http://archive.linuxfromscratch.org/mail-archives/blfs-support/2001/09/0317.html
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=4281&database=gcc


             reply	other threads:[~2001-12-02  4:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-01 20:06 rodrigc [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-12-01 20:03 rodrigc

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=20011202040600.16662.qmail@sourceware.cygnus.com \
    --to=rodrigc@gcc.gnu.org \
    --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).