Hi,
[Sorry for the messed up subject line, but I guess I'll better
continue with it rather than starting a new thread ...]
> > Something different:
> > Why are there both
> > /home/mingw-w64/lib/gcc/x86_64-pc-mingw32/4.4.0/include/float.h
> > /home/mingw-w64/x86_64-pc-mingw32/include/float.h
> > (at least in the linux 32-bit package I'm using for cross-compilation)
> > with only the last containing prototypes for _finite and a couple
> > of other functions, but the first being the one that's found and used
> > by the compiler?
> Normally the local version should be used. There are some small but
> important difference between the gcc version and our.
Sorry, I don't understand, which one you mean by local version...
Anyway, the way the built-in include paths are set up, it's the one
in lib/gcc/x86_64-pc-mingw32/4.4.0/include that's used by default.
Is that good or bad?
> > It's causing the current compile failure of wxWidgets (trunk) visible
> > on that daily rebuild page (at least until the next recompile, I've
> > added a hack to my local mingw-w64-headers to work around
> > that problem)...
>
> I missed to change implementation files necessary by prototype changes I
> did. Thanks for telling me that.
> Committed revision 451.
Huh? What did I tell? I'm lost ...
Regards,
Stefan
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
