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

[Fabio R. <fab...@gm...>]

Hello all,

first of all thank you very much for your answers.

I've tried to modify SSGLoadFLT.cxx changing line 185 with the  
following:
#if defined(WIN32) || defined(__APPLE__)

Now the compiling process works, even after a while I get this messages:

rm -f libplibjs.a
ar cru libplibjs.a js.o jsLinux.o jsLinuxOld.o jsMacOS.o jsMacOSX.o  
jsWindows.o jsBSD.o jsNone.o
ranlib: file: libplibjs.a(jsLinux.o) has no symbols
ranlib: file: libplibjs.a(jsLinuxOld.o) has no symbols
ranlib: file: libplibjs.a(jsMacOS.o) has no symbols
ranlib: file: libplibjs.a(jsWindows.o) has no symbols
ranlib: file: libplibjs.a(jsBSD.o) has no symbols
ranlib: file: libplibjs.a(jsNone.o) has no symbols
ranlib libplibjs.a
ranlib: file: libplibjs.a(jsLinux.o) has no symbols
ranlib: file: libplibjs.a(jsLinuxOld.o) has no symbols
ranlib: file: libplibjs.a(jsMacOS.o) has no symbols
ranlib: file: libplibjs.a(jsWindows.o) has no symbols
ranlib: file: libplibjs.a(jsBSD.o) has no symbols
ranlib: file: libplibjs.a(jsNone.o) has no symbols

Furthermore, when the compiling reaches the end I get this other  
messages (a part from a lot of warnings):

rm -f libplibpw.a
ar cru libplibpw.a pw.o pwX11.o pwWindows.o pwMacOSX.o
ranlib: file: libplibpw.a(pw.o) has no symbols
ranlib: file: libplibpw.a(pwX11.o) has no symbols
ranlib: file: libplibpw.a(pwWindows.o) has no symbols
ranlib libplibpw.a
ranlib: file: libplibpw.a(pw.o) has no symbols
ranlib: file: libplibpw.a(pwX11.o) has no symbols
ranlib: file: libplibpw.a(pwWindows.o) has no symbols
make[2]: Nothing to be done for `all-am'.
make[1]: Nothing to be done for `all-am'.

The library seems to be created (I can find libplibpw.a within the pw  
subfolder, weighting only 48kb), but it isn't copied to the proper  
folder (which, if I'm not wrong, should be /usr/local/lib) when I do  
the make install.

I'm not expert about compiling libraries, but the messages returned by  
the make don't sound so good to me...

Cheers,
Fabio


On 16 Jul 2008, at 18:09, Stuart McDonald wrote:

> 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.
>
>   Cheers,
>
> Stuart.