public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Chris Rankin <rankincj@yahoo.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: c++/4626
Date: Sat, 20 Oct 2001 13:16:00 -0000	[thread overview]
Message-ID: <20011020201602.14356.qmail@sourceware.cygnus.com> (raw)

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

From: Chris Rankin <rankincj@yahoo.com>
To: gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: c++/4626
Date: Sat, 20 Oct 2001 13:11:02 -0700 (PDT)

 My current workaround for this problem is to copy the
 following header files:
 
 stddef.h
 limits.h
 
 from /usr/lib/gcc-lib/i686-pc-linux-gnu/3.0.1/include/
 to /usr/i686-pc-linux-gnu/include/
 and so I suspect that at least one of those
 "duplicate" directories which cpp eliminates from the
 include-file search path really needs to be kept after
 all.
 
 Chris
 
 
 __________________________________________________
 Do You Yahoo!?
 Make a great connection at Yahoo! Personals.
 http://personals.yahoo.com


             reply	other threads:[~2001-10-20 13:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-20 13:16 Chris Rankin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-10-20 20:56 c++/4626 Chris Rankin
2001-10-19 20:56 c++/4626 Chris Rankin
2001-10-19 20:26 c++/4626 Chris Rankin

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=20011020201602.14356.qmail@sourceware.cygnus.com \
    --to=rankincj@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).