public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Dara Hazeghi <dhazeghi@yahoo.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: bootstrap/8207: Unable to Build GCC 3.2 with GLibC 2.3.1
Date: Thu, 08 May 2003 16:56:00 -0000	[thread overview]
Message-ID: <20030508165601.3859.qmail@sources.redhat.com> (raw)

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

From: Dara Hazeghi <dhazeghi@yahoo.com>
To: ZMan ZMan <x86zman@bigfoot.com>
Cc: gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Subject: Re: bootstrap/8207: Unable to Build GCC 3.2 with GLibC 2.3.1
Date: Thu, 8 May 2003 09:46:59 -0700 (PDT)

 --- ZMan ZMan <zoro6666@zahav.net.il> wrote:
 > Dara Hazeghi wrote:
 > 
 > >
 >
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-
 > 
 > > trail&database=gcc&pr=8207
 > >
 > > Hello,
 > >
 > > the issue reported in this PR is reportedly fixed
 > in 3.2.3. Could the  
 > > submitter please verify this? Thanks,
 > >
 > > Dara
 > >
 > >
 > Now it works flawlessly, but with GLibC 2.3.2 (don't
 > know about 2.3.1 !) 
 > & GCC 3.2.3,3.2.2 (and maybe 3.2.1 too - but as it
 > was months ago, i 
 > don't recall for sure)
 > 
 > Thanks for Tracking Old issues... :)
 
 Thanks for the response, sorry it took so long to get
 to your report. There are literally hundreds of open,
 unanalyzed bug reports which have had no response over
 the last 5 months :-( This bug can be closed then.
 
 Dara
 
 __________________________________
 Do you Yahoo!?
 The New Yahoo! Search - Faster. Easier. Bingo.
 http://search.yahoo.com


             reply	other threads:[~2003-05-08 16:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-08 16:56 Dara Hazeghi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-08 10:51 giovannibajo
2003-05-08 10:40 giovannibajo
2003-05-08  5:16 Dara Hazeghi
2002-10-12 10:16 x86zman

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=20030508165601.3859.qmail@sources.redhat.com \
    --to=dhazeghi@yahoo.com \
    --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).