RE: [Plib-devel] [Fwd: [TuxKart-users] I have a compilation problem]

[Norman V. <nh...@ca...>]

Steve Baker writes:
>
>Norman Vine wrote:
>>  >
>> >> /usr/include/plib/sg.h:842: `FLT_MAX' undeclared (first use
>> >this function)
>> >

<snip>

>> 
>> I believe the rationale behind this is that float.h is very
>> compiler and machine specific and by doing it this way
>> gcc can support cross-compiling and native-compiling
>> on the same host :-)
>
>Yep - that make sense - so the compiler should know where the
>magic include directory is.  In your case it knows to look
>in i686-pc-cygwin/2.95.2 - and in my case, it knows about
>
>/usr/lib/gcc-lib/i486-suse-linux/2.95.2/include/float.h
>
>...but how does it know that this is a SuSE Linux machine?

The machine type and version of the compiler is hardwired wired
in at compile time.  

strings /bin/gcc.exe > jnk
head -n 2 jnk    // Not sure if these are always the first two strings
2.95.2
i686-pc-cygwin

and gcc uses these to find the actual compiler tools
and libc ect based on their path

>Our friend over on TuxKart-users (who is unfortunately
>not a programmer) is getting complaints that you and I
>don't see.

Isn't this problem solved if we just add  to <sg.h>
#include <float.h>

ANSII guarantees that the compiler will be able to find <float.h>

Cheers

Norman