[torquedev] [Bug 70] libcap-devel and pam-devel apparently required to build TORQUE 2.5 beta

Troy Baer tbaer at utk.edu
Thu Jul 8 18:50:05 MDT 2010

On Thu, 2010-07-08 at 20:30 -0400, Troy Baer wrote:
> On Thu, 2010-07-08 at 18:04 -0600, bugzilla-daemon at supercluster.org
> wrote:
> > Michael Jennings <mej at lbl.gov> changed:
> > It used to be that --disable-csa would prevent "-L/opt/cray/job/default/lib64
> > -ljob" from being added to $MOMLIBS.  This is no longer the case, and on any
> > system that has a libjob (even if it's not a Cray) with a job_create()
> > function, libjob will be linked.  There seems to no longer be an option to
> > prevent this.
> I'm going to guess that this change was a side effect of the following
> entry in CHANGELOG:
> 2.4.6
> ...
>   b - split Cray job library and CSA functionality since CSA is dependant on job
>       library but job library is not dependant on CSA
> ...
> However, something very much like (if not identical to) libjob on the
> Cray XTs has been part of SGI's ProPack since 2007 or so, so I'm
> confused as to why this is labeled as a Cray-specific thing.  (Not to
> mention the whole why-can't-I-turn-it-off thing...)

That being said, perhaps the right thing to do is have the configure
script check for the presence of libcap and pam devel libraries before
turning on libjob support (which presumably includes 

Troy Baer, HPC System Administrator
National Institute for Computational Sciences, University of Tennessee
Phone:  865-241-4233
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : http://www.supercluster.org/pipermail/torquedev/attachments/20100708/f51940cd/attachment.bin 

More information about the torquedev mailing list