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: c++/2576 Date: Mon, 28 May 2001 18:26:00 -0000 [thread overview] Message-ID: <20010529012600.7750.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR c++/2576; it has been noted by GNATS. From: rodrigc@gcc.gnu.org To: gcc-gnats@gcc.gnu.org, min@hotu.com, nobody@gcc.gnu.org, rodrigc@gcc.gnu.org Cc: Subject: Re: c++/2576 Date: 29 May 2001 01:20:06 -0000 Synopsis: header file type conflict State-Changed-From-To: open->closed State-Changed-By: rodrigc State-Changed-When: Mon May 28 18:20:06 2001 State-Changed-Why: Refer to the FAQ that comes with glibc 2.2.2: 2.34. When compiling C++ programs, I get a compilation error in streambuf.h. {BH} You are using g++ 2.95.2? After upgrading to glibc 2.2, you need to apply a patch to the include files in /usr/include/g++, because the fpos_t type has changed in glibc 2.2. The patch is at htt2.34. When compiling C++ programs, I get a compilation error in streambuf.h. {BH} You are using g++ 2.95.2? After upgrading to glibc 2.2, you need to apply a patch to the include files in /usr/include/g++, because the fpos_t type has changed in glibc 2.2. The patch is at http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=2576&database=gcc
reply other threads:[~2001-05-28 18:26 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20010529012600.7750.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: linkBe 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).