public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "karlson2k at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/56279] Unwanted directory is added to include search path when building for MingGW with --native-system-header-dir Date: Sun, 10 Feb 2013 23:48:00 -0000 [thread overview] Message-ID: <bug-56279-4-6nCk5nZ0pl@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-56279-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56279 Evgeny Grin <karlson2k at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Target|i686-w64-mingw32, |i686-pc-mingw32, |x86_64-w64-mingw32 |i686-w64-mingw32, | |x86_64-w64-mingw32 --- Comment #2 from Evgeny Grin <karlson2k at gmail dot com> 2013-02-10 23:47:59 UTC --- Result on MinGW32 compiler (tried from mingw site or compiled from sources - results are the same): $ echo int main(){return 1;} | gcc.exe -v -E -x c - Using built-in specs. COLLECT_GCC=gcc.exe Target: mingw32 Configured with: ../gcc-4.7.2/configure --enable-languages=c,c++,ada,fortran,objc,obj-c++ --disable-sjlj-exceptions --with-dwarf2 --enable-shared --enable-libgomp --disable-win32-registry --enable-libstdcxx-debug --disable-build-poststage1-with-cxx --enable-version-specific-runtime-libs --build=mingw32 --prefix=/mingw Thread model: win32 gcc version 4.7.2 (GCC) COLLECT_GCC_OPTIONS='-v' '-E' '-mtune=i386' '-march=i386' t:/mingw32/bin/../libexec/gcc/mingw32/4.7.2/cc1.exe -E -quiet -v -iprefix t:\mingw32\bin\../lib/gcc/mingw32/4.7.2/ - -mtune=i386 -march=i386 ignoring nonexistent directory "t:\mingw32\bin\../lib/gcc/mingw32/4.7.2/../../../../mingw32/include" ignoring duplicate directory "t:/mingw32/lib/gcc/../../lib/gcc/mingw32/4.7.2/include" ignoring nonexistent directory "/mingw/include" ignoring duplicate directory "t:/mingw32/lib/gcc/../../include" ignoring duplicate directory "t:/mingw32/lib/gcc/../../lib/gcc/mingw32/4.7.2/include-fixed" ignoring nonexistent directory "t:/mingw32/lib/gcc/../../lib/gcc/mingw32/4.7.2/../../../../mingw32/include" ignoring nonexistent directory "/mingw/include" #include "..." search starts here: #include <...> search starts here: t:\mingw32\bin\../lib/gcc/mingw32/4.7.2/include t:\mingw32\bin\../lib/gcc/mingw32/4.7.2/../../../../include t:\mingw32\bin\../lib/gcc/mingw32/4.7.2/include-fixed End of search list. # 1 "<stdin>" # 1 "<command-line>" # 1 "<stdin>" int main(){return 1;} COMPILER_PATH=t:/mingw32/bin/../libexec/gcc/mingw32/4.7.2/;t:/mingw32/bin/../libexec/gcc/;t:/mingw32/bin/../lib/gcc/mingw32/4.7.2/../../../../mingw32/bin/ LIBRARY_PATH=t:/mingw32/bin/../lib/gcc/mingw32/4.7.2/;t:/mingw32/bin/../lib/gcc/;t:/mingw32/bin/../lib/gcc/mingw32/4.7.2/../../../../mingw32/lib/;t:/mingw32/bin/../lib/gcc/mingw32/4.7.2/../../../ COLLECT_GCC_OPTIONS='-v' '-E' '-mtune=i386' '-march=i386' Two "/mingw/include" in Posix format in GCC! In practice GCC try to use /mingw/include directory on current drive (in my case on drive T: ), but I may have a different MinGW version installed there.
prev parent reply other threads:[~2013-02-10 23:48 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-02-10 22:45 [Bug c/56279] New: " karlson2k at gmail dot com 2013-02-10 23:04 ` [Bug target/56279] " karlson2k at gmail dot com 2013-02-10 23:48 ` karlson2k at gmail dot com [this message]
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-56279-4-6nCk5nZ0pl@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: 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).