public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "dave berk" <dave.brk@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: gcc 4.1.1 include order
Date: Thu, 19 Oct 2006 20:30:00 -0000	[thread overview]
Message-ID: <c1263ca0610191330i51ecc959qa0d1ef469b33f498@mail.gmail.com> (raw)

Recently I compiled gcc 4.1.1 with minGW in windows according to the
instructions here.

Now, when I try to compile a test file that includes float.h I get the
following errors:
error: '_clear87' was not declared in this scope
error: '_control87' was not declared in this scope

I tried to run the file the -v -H flags:
E:\temp>g++ -v -H main.cpp
Using built-in specs.
Target: mingw32
Configured with: ../gcc-4.1.1 /configure --with-gcc --with-gnu-ld
--with-gnu-as --host=mingw32 --target=mingw32 --prefix=/mingw
--enable-threads --disable-nls --enable-languages=c,c++
--disable-win32-registry --disable-shared --without-x
Thread model: win32
gcc version 4.1.1
c:/mingw/bin/../libexec/gcc/mingw32/4.1.1/cc1plus.exe -quiet -v
-iprefix c:\mingw\bin\../lib/gcc/mingw32/4.1.1/ -H main.cpp -quiet
-dumpbase main.cpp -auxbase main -version -o
C:\DOCUME~1\Dave\LOCALS~1\Temp/ccqWaaaa.s
ignoring nonexistent directory "/mingw/include"
ignoring nonexistent directory "C:/MinGW/mingw32/include"
ignoring nonexistent directory "/mingw/include"
#include "..." search starts here:
#include <...> search starts here:
c:/mingw/bin/../lib/gcc/mingw32/4.1.1/include
C:/MinGW/include/c++/4.1.1
C:/MinGW/include/c++/4.1.1/mingw32
C:/MinGW/include/c++/4.1.1/backward
C:/MinGW/include
C:/MinGW/lib/gcc/mingw32/4.1.1/include
End of search list.

 What seems to happen is that gcc searches the gcc system files first
and not the "C:/MinGW/include". anyone knows why?
and how can I change the order of the included files?

Dave

                 reply	other threads:[~2006-10-19 20:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=c1263ca0610191330i51ecc959qa0d1ef469b33f498@mail.gmail.com \
    --to=dave.brk@gmail.com \
    --cc=gcc-help@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).