plib-users

[Plib-users] Compiling issues on MacOS X 10.5

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

Dear all,

I'm trying to compile PLIB on my MacPro (MacOS X 10.5.4), but  
unfortunately I can't use DarwinPorts since the firewall installed by  
my institution is continuously blocking it. I've therefore tried to  
compile the libraries manually, but after the configuration I gets an  
error during the compiling phase which starts in this way:

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.

Many many thanks,
Fabio

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

[Stuart M. <stu...@bl...>]

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.

Fabio Ruini wrote:
> Dear all,
>
> I'm trying to compile PLIB on my MacPro (MacOS X 10.5.4), but  
> unfortunately I can't use DarwinPorts since the firewall installed by  
> my institution is continuously blocking it. I've therefore tried to  
> compile the libraries manually, but after the configuration I gets an  
> error during the compiling phase which starts in this way:
>
> 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.
>
> Many many thanks,
> Fabio
> -------------------------------------------------------------------------
> 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=/
> _______________________________________________
> plib-users mailing list
> pli...@li...
> https://lists.sourceforge.net/lists/listinfo/plib-users
>
>
>   

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

[Fay J. F Dr C. U. 46 S. <joh...@eg...>]

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.

John F. Fay
Technical Fellow
Jacobs Technology TEAS Group
850-883-1294 

-----Original Message-----
From: pli...@li...
[mailto:pli...@li...] On Behalf Of Stuart
McDonald
Sent: Wednesday, July 16, 2008 12:09 PM
To: PLIB Users
Subject: Re: [Plib-users] Compiling issues on MacOS X 10.5

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.

Fabio Ruini wrote:
> Dear all,
>
> I'm trying to compile PLIB on my MacPro (MacOS X 10.5.4), but  
> unfortunately I can't use DarwinPorts since the firewall installed by

> my institution is continuously blocking it. I've therefore tried to  
> compile the libraries manually, but after the configuration I gets an

> error during the compiling phase which starts in this way:
>
> 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.
>
> Many many thanks,
> Fabio
>
------------------------------------------------------------------------
-
> 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=/
> _______________________________________________
> plib-users mailing list
> pli...@li...
> https://lists.sourceforge.net/lists/listinfo/plib-users
>
>
>   



------------------------------------------------------------------------
-
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=/
_______________________________________________
plib-users mailing list
pli...@li...
https://lists.sourceforge.net/lists/listinfo/plib-users

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.

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

[Fay J. F Dr C. U. 46 S. <joh...@eg...>]

An "unsigned int" is always available ... if it is called "unsigned
int".  But Windows doesn't have "stdint.h", at least not in its default
include path (I just tried it).

Certainly it seems silly, but unfortunately thanks to Windows it is
necessary.

John F. Fay
Technical Fellow
Jacobs Technology TEAS Group
850-883-1294 

-----Original Message-----
From: pli...@li...
[mailto:pli...@li...] On Behalf Of
mat...@ma...
Sent: Wednesday, July 16, 2008 1:02 PM
To: PLIB Users
Subject: Re: [Plib-users] Compiling issues on MacOS X 10.5

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.

------------------------------------------------------------------------
-
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=/
_______________________________________________
plib-users mailing list
pli...@li...
https://lists.sourceforge.net/lists/listinfo/plib-users

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.

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

[Fay J. F Dr C. U. 46 S. <joh...@eg...>]

Fabio,

	I'm pretty sure the messages are harmless.  The "js" and "pw"
libraries are designed to build and run on many different operating
systems, and the systems are so different that the code for each
operating system goes into its own ".cxx" file.  So, for example,
"jsWindows.cxx" will have the "js" code to run on Windows and the
"jsLinux.cxx" file will have the "js" code to run the same things on
Linux.  As long as one of your "js" files has built and has defined
symbols (and I see you didn't get a warning for "jsMacOSX.o") you should
be in good shape.  The same holds true for "pw".

John F. Fay
Technical Fellow
Jacobs Technology TEAS Group
850-883-1294 

-----Original Message-----
From: pli...@li...
[mailto:pli...@li...] On Behalf Of Fabio
Ruini
Sent: Wednesday, July 16, 2008 12:52 PM
To: PLIB Users
Subject: Re: [Plib-users] Compiling issues on MacOS X 10.5

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.

------------------------------------------------------------------------
-
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=/
_______________________________________________
plib-users mailing list
pli...@li...
https://lists.sourceforge.net/lists/listinfo/plib-users

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

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

Great! :-)

thank you very much for your help, John.

Everything look right now. The libraries and the includes in fact have  
been copied by the make install on the right places (I was looking for  
them in /usr/local/lib and /usr/local/include, while they're instead  
in /usr/lib and /usr/include).

I'm going to make some test.

Cheers,
Fabio


On 16 Jul 2008, at 19:17, Fay John F Dr CTR USAF 46 SK wrote:

> Fabio,
>
> 	I'm pretty sure the messages are harmless.  The "js" and "pw"
> libraries are designed to build and run on many different operating
> systems, and the systems are so different that the code for each
> operating system goes into its own ".cxx" file.  So, for example,
> "jsWindows.cxx" will have the "js" code to run on Windows and the
> "jsLinux.cxx" file will have the "js" code to run the same things on
> Linux.  As long as one of your "js" files has built and has defined
> symbols (and I see you didn't get a warning for "jsMacOSX.o") you  
> should
> be in good shape.  The same holds true for "pw".
>
> John F. Fay
> Technical Fellow
> Jacobs Technology TEAS Group
> 850-883-1294