[torquedev] [Bug 70] libcap-devel and pam-devel apparently required to build TORQUE 2.5 beta
garrick at usc.edu
Thu Jul 8 14:17:16 MDT 2010
On Thu, Jul 08, 2010 at 02:00:18PM -0600, bugzilla-daemon at supercluster.org alleged:
> --- Comment #5 from Troy Baer <tbaer at utk.edu> 2010-07-08 14:00:18 MDT ---
> (In reply to comment #1)
> > Can you send the output? I don't know why either library would be required to
> > link pbs_mom.
> I may have mistyped earlier -- it's libcap-devel that now seems to be required,
> *not* libpcap-devel.
Well, same mystery, different library.
> /bin/sh ../../libtool --tag=CC --mode=link gcc -g -O2 -D_LARGEFILE64_SOURCE
> linux/libmommach.a -L/opt/cray/job/default/lib64 -ljob -lutil
The options that torque is passing to libtool are what I would expect.
> gcc -g -O2 -D_LARGEFILE64_SOURCE -DUSEJOBCREATE -o .libs/pbs_mom catch_child.o
> job_qs_upgrade.o linux/libmommach.a -L/opt/cray/job/default/lib64
> /usr/lib64/libjob.so -lcap -lpam -lutil ../lib/Libattr/libattr.a
So libtool is expanding -ljob to /usr/lib64/libjob.so and adding -lcap -lpam. I
don't know why.
Can you send me your generated config.log and libtool? I'll take a look but I
suspect this is something on your system that is adding those libs and not
something that we can control in torque.
I suspect that your libjob.so requires libcap and libpam and libtool is just
doing the right thing.
You might edit your generated libtool and remove "-lcap -lpam" and see what
> [reconfiguring with --disable-pam and rebuilding results in exactly the same
> behavior as above]
Right, because our PAM support has nothing to do with this.
Garrick Staples, GNU/Linux HPCC SysAdmin
University of Southern California
Life is Good!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
Url : http://www.supercluster.org/pipermail/torquedev/attachments/20100708/bc3a02b4/attachment-0001.bin
More information about the torquedev