mingw-cross-env-list
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Mingw-cross-env-list] Qt 4.7 (help wanted)


From: Mark Brand
Subject: Re: [Mingw-cross-env-list] Qt 4.7 (help wanted)
Date: Wed, 02 Jun 2010 13:24:11 +0200
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.4) Gecko/20100527 SUSE/3.1rc1-3.1 Thunderbird/3.1


This problem has been driving me crazy, and I'm not the only one it seems.
 I'm sure I don't understand all the issues, but here is a quick summary:

-We are in good company. There are many reports in various places about
this.
-The mingw32 cross RPMs from opensuse have the same "problem" with float.h.
-Undefined symbols _clear87 and _control87 are commons symptoms of this
problem, especially when building Qt.
-No standard solution as far as I can tell.
-I still don't understand how Qt managed to build GCC 4.4 with the mingw
include directory first.
-I spent too much time trying without success to build GCC 4.5 with the
mingw include directory first. ):
Hi Mark,

I know what you mean, --with-sysroot and --with-local-prefix really
sound like they are what you want. The closest I could get was using a
spec file as outlined here:

http://www.mingw.org/wiki/SpecsFileHOWTO

$i686-pc-mingw32-cpp -v -specs=specs</dev/null
Using built-in specs.
Reading specs from specs
[...]
#include "..." search starts here:
#include <...> search starts here:
 /Users/tonytheodore/dev/mingw-cross-env/usr/i686-pc-mingw32/include
 /Users/tonytheodore/dev/mingw-cross-env/usr/lib/gcc/i686-pc-mingw32/4.5.0/include
 /Users/tonytheodore/dev/mingw-cross-env/usr/lib/gcc/i686-pc-mingw32/4.5.0/include-fixed
End of search list.

I've attached the modified spec file I used, the most important option
is -nostdinc. The only section I changed is the *cpp. I'd didn't get
to figuring out how to generate the file and putting it in the right
spot to be found automatically.


That look like a good way to do that, if that's really what should be done. What about my doubts about whether reordering the search path is the correct approach?

-It's probably correct to have the gcc include directory *before* the mingw include directory anyway.

regards,
Mark

reply via email to

[Prev in Thread] Current Thread [Next in Thread]