public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "georgjohann at web dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/39622]  New: Missing -isystem include-fixed when building canadian cross libgcc
Date: Fri, 03 Apr 2009 08:50:00 -0000	[thread overview]
Message-ID: <bug-39622-11621@http.gcc.gnu.org/bugzilla/> (raw)

The following is just a verbatim copy of
   http://gcc.gnu.org/ml/gcc-help/2009-04/msg00023.html
For details and possible patch follow the link.

--

I'd like to build a canadian cross configured with
  --host=i586-mingw32
  --build=i686-linux-gnu

Everything goes fine except building libgcc because limits.h cannot be found,
as include-fixed is not in include path.

The problem looks like this: For a native build, i.e. host=build,
libgcc/Makefile sets CC to
> CC = [target-gcc-build-dir]/./gcc/xgcc -B[target-gcc-build-dir]/./gcc/
but for host != build it is
> CC = [target-gcc]
without adding [target-gcc-build-dir]/./gcc/include-fixed
to the include directory search path my means of -isystem.
However, this directory contains the limits.h.


-- 
           Summary: Missing -isystem include-fixed when building canadian
                    cross libgcc
           Product: gcc
           Version: 4.3.3
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: bootstrap
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: georgjohann at web dot de
 GCC build triplet: i686-linux-gnu
  GCC host triplet: i586-mingw32
GCC target triplet: any


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39622


             reply	other threads:[~2009-04-03  8:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-03  8:50 georgjohann at web dot de [this message]
2010-03-11  2:00 ` [Bug bootstrap/39622] " monaka at monami-software dot com

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=bug-39622-11621@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).