Parallel sockets or?

[bruce.labitt at autoliv.com]

"Shawn O'Shea" <shawn at eth0.net> wrote on 10/08/2009 01:27:57 PM:

> 
> The originators of psock were at cesnet.cz, there is a link to the 
library
> at http://www.cesnet.cz/project/qosip
> 
> The make doesn't finish.  Several compile errors.  I played about a bit,
> but did not make much headway...

> I was curious and downloaded this. I'm working on CentOS 5.3 (32-bit).
> 
> After untarring and doing a ./configure, when I try to make, very 
> early in the compile I got the following error (which I presume was 
> similar with your attempts):
>  gcc -DHAVE_CONFIG_H -I. -I. -I.. -g -O2 -MT pollall_cdrv.lo -MD -MP -
> MF .deps/pollall_cdrv.Tpo -c ptransfer/pollall_cdrv.c  -fPIC -DPIC -o 
> .libs/pollall_cdrv.o
> ptransfer/pollall_cdrv.c: In function 'ptransfer_pollall_send_block':
> ptransfer/pollall_cdrv.c:119: error: invalid lvalue in assignment
> make[2]: *** [pollall_cdrv.lo] Error 1
> make[2]: Leaving directory `/storage/home/shawn/psock-0.2a/psock'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/storage/home/shawn/psock-0.2a'
> make: *** [all] Error 2
> 
> I googled: error: invalid lvalue in assignment
> The first google result is this discussion thread:
> http://www.tek-tips.com/viewthread.cfm?qid=1353180&page=12
> 
> It is noted by the original poster later in the thread "[...] we 
> haven't had issues with it compiling and working until we moved to gcc 
4"
> He later notes " I have found referrences where the developers of gcc 
> dropped support for 'casting an l-value', they called it a 'bogosity'."
> 
> So it would appear this code is not "gcc4 friendly", so it either 
> needs to be fixed (suggestions on how to do this are presented in the 
> thread), or use a gcc3.x compiler. RH/CentOS provide such in the 
> compat-gcc-34 (and C++ in compat-gcc-34-c++) packages.
> 
> Using that compiler, I can build without issue (ie: the following 
> completes without error: CC=gcc34 ./configure && make)

> -Shawn

Very cool!  Yes, I got the very same errors.  Hmm, my google-fu is not as 
great as yours, I am very grateful for your discovery.  I shall check this 
out.  Apparently there were no macro "wrap" errors either?  (re: macro 
question)

-Bruce

******************************
Neither the footer nor anything else in this E-mail is intended to or constitutes an <br>electronic signature and/or legally binding agreement in the absence of an <br>express statement or Autoliv policy and/or procedure to the contrary.<br>This E-mail and any attachments hereto are Autoliv property and may contain legally <br>privileged, confidential and/or proprietary information.<br>The recipient of this E-mail is prohibited from distributing, copying, forwarding or in any way <br>disseminating any material contained within this E-mail without prior written <br>permission from the author. If you receive this E-mail in error, please <br>immediately notify the author and delete this E-mail.  Autoliv disclaims all <br>responsibility and liability for the consequences of any person who fails to <br>abide by the terms herein. <br>
******************************