Re: [Plib-users] Compiling issues on MacOS X 10.5

[<mat...@ma...>]

i am not that familiar with plib.  having unsigned int type def'ed to 
uint if UL_WIN32 seems silly.   an unsigned int is always availiable, i 
dont see how that is dependent on the userland.

and if an exact int is need (32 bits, loose definition of int), then use 
stdint.h, that has been added to the standard and avaliable for years.

#ifdef HAVE_STDINT_H  // assuming autoconf
   #include <stdint.h>
   typedef uint32_t uint
#endif

matt

On Wed, 16 Jul 2008, Fay John F Dr CTR USAF 46 SK wrote:

> While that might make it work in the present case, it is most
> emphatically NOT a good general fix.  Most platforms do define "uint"
> somewhere else, and taking out the "#ifdef" would break PLIB on those
> platforms.  A more general solution would be to find where MacOS X
> 10.5.4 defines "uint" and include that definition.
>
>
> Never tried this, but as you can see from the error the problem is it
> doesn't know what a uint is.
>
> It's typedef'ed to unsigned int in the ssgLoadFLT source, but with an
> ifdef UL_WIN32.
>
> Just take out the #ifdef will make it work for you. No idea if that's a
> proper fix i.e. would work on every platform.
>
>> ssgLoadFLT.cxx: In function 'void _swab32(const void*, void*, int)':
>> ssgLoadFLT.cxx:185: error: 'uint' was not declared in this scope
>> ssgLoadFLT.cxx:185: error: 's' was not declared in this scope
>> ssgLoadFLT.cxx:185: error: expected primary-expression before ')'token
>> ssgLoadFLT.cxx:185: error: expected `;' before 'src'
>> ssgLoadFLT.cxx:186: error: 'd' was not declared in this scope
>> ssgLoadFLT.cxx:186: error: expected primary-expression before ')'token
>> ssgLoadFLT.cxx:186: error: expected `;' before 'dst'
>> ssgLoadFLT.cxx:188: error: expected `;' before 't'
>> [...]
>>
>> It looks like - even if the ./configure didn't return me any error -
>> I'm missing some dependencies. Anyway, I can't understand which one.
>> Perhaps some of you has already experienced a similar issue trying to
>
>> compile PLIB on Mac and therefore you could provide me with some
>> findings?
>>
>> I've also tried to write to Darrell Walisser, as suggested into the
>> README.mac file included into the sources package, but the address
>> published there looks to be not used anymore.