public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "guardia at sympatico dot ca" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/19607] New: Build fails on MSYS/MingGW because of incorrect SYSTEM_HEADER_DIR
Date: Mon, 24 Jan 2005 17:30:00 -0000	[thread overview]
Message-ID: <20050124173042.19607.guardia@sympatico.ca> (raw)

On MSYS, the system headers are found in /mingw/include ... I made a modified
gcc/config/i386/t-mingw32 adding:

NATIVE_SYSTEM_HEADER_DIR = /mingw/include

And it works here.

Also, the configure script needs to be started with a relative path or the
"srcdir" anyway needs to be relative or gengtype will fail. This problem is
documented in bug #16024 (gengtype doesn't crash here, but it still fails not
finding a path)

-- 
           Summary: Build fails on MSYS/MingGW because of incorrect
                    SYSTEM_HEADER_DIR
           Product: gcc
           Version: 4.0.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: bootstrap
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: guardia at sympatico dot ca
                CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: i686-pc-mingw32
  GCC host triplet: i686-pc-mingw32
GCC target triplet: i686-pc-mingw32


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


             reply	other threads:[~2005-01-24 17:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-24 17:30 guardia at sympatico dot ca [this message]
2005-01-24 17:31 ` [Bug bootstrap/19607] " guardia at sympatico dot ca
2005-06-09 18:13 ` fxcoudert at gcc dot gnu dot org
2005-06-09 20:41 ` dannysmith at users dot sourceforge dot net
2005-06-09 20:44 ` guardia at sympatico dot ca
2005-06-09 21:47 ` fxcoudert at gcc dot gnu dot org
2005-06-10  3:03 ` dannysmith at users dot sourceforge dot net
2005-06-10  3:15 ` guardia at sympatico dot ca
2005-08-06 11:19 ` fxcoudert at gcc dot gnu dot org
2005-08-23  1:53 ` pinskia at gcc dot gnu dot org

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=20050124173042.19607.guardia@sympatico.ca \
    --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).