At least you solved it, thats what counts!

Steve Traylen wrote:
> On Tue, Aug 22, 2006 at 11:55:29AM +0100 or thereabouts, Steve Traylen wrote:
>   
>> Hi 
>>
>>   Trying to build maui-3.2.6p16 against torque-devel-2.1.2-1cri on 
>>   ScientificLinux4 (RHEL4 clone) it fails with 
>>     
>
> Sorry, I answered my own question 10 seconds after sending this. 
> As well torque-devel torque-client must be installed to give
> you the required libtorque.so.0.
>
>  Steve
>   
>> gcc -I../../include -I../../include       -DLINUX   -D__MPBS       -O2 -g 
>> -pipe -m32 -march=i386 -mtune=pentium4  -c LLI.c
>> gcc Server.o UserI.o SDR.o LLI.o -o ../../bin/maui -L../../lib     -ltorque 
>> -lmoab -lmcom       -lm
>> ../../lib/libmoab.a(MPBSI.o)(.text+0xdb): In function `MPBSProcessEvent':
>> /home/traylens/redhat/BUILD/maui-3.2.6p16/src/moab/MPBSI.c:477: undefined 
>> reference to `rpp_fd'
>> ../../lib/libmoab.a(MPBSI.o)(.text+0x153):/home/traylens/redhat/BUILD/maui-3.2.6p16/src/moab/MPBSI.c:505:
>>  undefined reference to `rpp_fd'
>> ../../lib/libmoab.a(MPBSI.o)(.text+0x679): In function `__MPBSSystemQuery':
>> /home/traylens/redhat/BUILD/maui-3.2.6p16/src/moab/MPBSI.c:1123: undefined 
>> reference to `pbs_disconnect'
>>
>>
>>   The same thing on ScientificLinux3 (RHEL3 clone) builds okay at this stage
>>
>>   gcc Server.o UserI.o SDR.o LLI.o -o ../../bin/maui -L../../lib     
>> -ltorque -lmoab -lmcom       -lm
>>
>>
>>   torque was rebuilt on both operating systems with 
>>
>>   $ rpmbuild -ba --with homedir=/var/spool/pbs ~/redhat/SPECS/torque.spec
>>
>>
>>   Any ideas? 
>>
>>  Steve
>> -- 
>> Steve Traylen
>> work email:  [EMAIL PROTECTED]
>> personal email: [EMAIL PROTECTED]
>> jabber: xmpp://[EMAIL PROTECTED]
>> _______________________________________________
>> mauiusers mailing list
>> [email protected]
>> http://www.supercluster.org/mailman/listinfo/mauiusers
>>     
>
>   
_______________________________________________
mauiusers mailing list
[email protected]
http://www.supercluster.org/mailman/listinfo/mauiusers

Reply via email to