public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Paolo Carlini <pcarlini@unitus.it>
To: paolo@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: libstdc++/9408: std::string input operator waits for EOF
Date: Thu, 23 Jan 2003 09:26:00 -0000	[thread overview]
Message-ID: <20030123092600.23612.qmail@sources.redhat.com> (raw)

The following reply was made to PR libstdc++/9408; it has been noted by GNATS.

From: Paolo Carlini <pcarlini@unitus.it>
To: gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: libstdc++/9408: std::string input operator waits for EOF
Date: Thu, 23 Jan 2003 10:17:29 +0100

 Kelly Fitz wrote:
 
 > I expect the behavior you describe, but that is not the behavior I see.
 
 >  as --traditional-format -V -Qy -o moo.o moo.s
 > GNU assembler version 2.10.91 (i386-redhat-linux) using BFD version  
 > 2.10.91.0.2
 
 
 Hi,
 
 looks like your binutils are quite old (the current version is 
 2.13.2.1), and I suspect, glibc too.
 The latter, in particular, is probably the culprit, since, for 
 glibc2.2.5 and 2.3.x, there are hundreds of succesful installations 
 around I'm aware of, certainly not experiencing the problem.
 
 Could you possibly upgrade your glibc package and/or double check on a 
 system similar to yours but equipped with a more recent glibc?
 
 Thanks, Paolo.
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9408
 


             reply	other threads:[~2003-01-23  9:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-23  9:26 Paolo Carlini [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-24  9:53 paolo
2003-01-23  9:16 Paolo Carlini
2003-01-22 23:36 Kelly Fitz
2003-01-22 22:22 paolo
2003-01-22 21:56 kfitz

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=20030123092600.23612.qmail@sources.redhat.com \
    --to=pcarlini@unitus.it \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=paolo@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).