public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Pete Gonzalez <gonz@ratloop.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: other/8307: libstdc++ fails to compile because of fixincludes headers
Date: Sat, 15 Feb 2003 20:26:00 -0000	[thread overview]
Message-ID: <20030215202600.21369.qmail@sources.redhat.com> (raw)

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

From: Pete Gonzalez <gonz@ratloop.com>
To: gcc-gnats@gcc.gnu.org,gcc-bugs@gcc.gnu.org,nobody@gcc.gnu.org,
 gcc-prs@gcc.gnu.org,gonz@ratloop.com,Peter.Barada@motorola.com
Cc:  
Subject: Re: other/8307: libstdc++ fails to compile because of
  fixincludes headers
Date: Sat, 15 Feb 2003 15:20:42 -0500

 >I regularly build a GCC/Newlib/binutils toolchain and don't see this
 >problem. Are you configuring using the "--with-headers=..." option?
 
 Yes, but my environment is a bit unusual.  I am building an ARM
 cross-compiler under Cygwin, using a modified version of this kit:
 
          http://www.io.com/~fenix/devkitadv/
 
 I think this is just an unusual setup that hasn't been tested by
 whoever maintains the "fixincludes" code.  I don't think it's
 specific to Cygwin, because at one point I was able to reproduce
 the bug under Debian Linux.  If someone wants to volunteer to
 debug it, I could probably create a Makefile that reproduces the
 problem in one of those environments.
 
 Thanks,
 -Pete
 


             reply	other threads:[~2003-02-15 20:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-15 20:26 Pete Gonzalez [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-31 17:02 rearnsha
2002-10-21 22:26 gonz

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=20030215202600.21369.qmail@sources.redhat.com \
    --to=gonz@ratloop.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).