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: Tony Theodore
Subject: Re: [Mingw-cross-env-list] Qt 4.7 (help wanted)
Date: Wed, 2 Jun 2010 20:53:18 +1000

On 2 June 2010 20:12, Mark Brand <address@hidden> wrote:
>
>> How can we influence that search order? Is it possible to pass
>> some corresponding ./configure options to GCC in src/gcc.mk?
>>
>> How did the Qt people do that? Did they patch GCC to get that
>> behaviour? Does the GCC contain some special handling in the
>> paths when it is built for mingw? If so, why don't _we_ trigger
>> that special handling, too?
>>
>
> 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.

Tony

Attachment: specs
Description: Binary data


reply via email to

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