On Thu, Oct 8, 2009 at 5:06 PM, <bruce.lab...@autoliv.com> wrote: > "Shawn O'Shea" <sh...@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 > > > > That was my error. > > > 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 > > It really completes without error? Not for me... :( > > With a 64 bit system, with gcc-3.4 (Ubuntu 8.10 on x86_64) I had to edit > atomicptr.h from "__i86_64__" to "__x86_64__", since the system reports > itself as x86_64 rather than i86_64 > This causes the make to die unless the change is made. > > So again out of sheer curiosity, I installed an Ubuntu 8.10 amd64 desktop default install in VMware Fusion. I installed gcc 3.4 (apt-get install gcc-3.4), untarred, configured (CC=gcc-3.4 ./configure) and make. I get this: gcc-3.4 -DHAVE_CONFIG_H -I. -I. -I.. -g -O2 -MT file.lo -MD -MP -MF .deps/file.Tpo -c file.c -fPIC -DPIC -o .libs/file.o In file included from ../psock/file.h:30, from file.c:35: ../psock/atomicptr.h:38:2: warning: #warning Running architecture is unapproved, please refer psock/atomicptr.h
followed by a slew of warnings and errors. It would seem by the nature of that message that the architecture (amd64 aka x86_64) is not supported. Compiling it 32-bit works fine on the same VM (apt-get install libc6-dev-i386 lib32gcc1 to get the necessary 32-bit build pieces and tell confogure and gcc to build 32-bit with CC=gcc-3.4 CFLAGS='-m32' ./configure). Make completes fine. -Shawn > Then I compiled using > > CC=gcc-3.4 ./configure && make > > I got tons of errors with system_file_ops.c, probably due to the #define > wrap(f) wrap_#f statement > > Then I editted the statement in system_file_ops.c to #define wrap(f) > wrap_##f > > Now I get lots of errors for undefined functions that are "mentioned" in > the struct psock_file_ops. That at least makes sense - no definition = > compile error. There is a TODO which glibly states: "rest in the same > manner" :) > > Is that your experience, or did everything compile to completion with no > errors??? > > This library certainly looks far from complete to me... Or I am missing > something big? > > Thanks! > -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> > ****************************** >
_______________________________________________ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
