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

[Garrick Staples]

On Thu, Jul 08, 2010 at 06:04:42PM -0600, bugzilla-daemon at supercluster.org alleged:
> http://www.clusterresources.com/bugzilla/show_bug.cgi?id=70
> 
> Michael Jennings <mej at lbl.gov> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                  CC|                            |mej at lbl.gov
> 
> --- Comment #6 from Michael Jennings <mej at lbl.gov> 2010-07-08 18:04:42 MDT ---
> (In reply to comment #5)
> > linux/libmommach.a -L/opt/cray/job/default/lib64 -ljob  -lutil
> > ...
> > job_qs_upgrade.o  linux/libmommach.a -L/opt/cray/job/default/lib64
> > /usr/lib64/libjob.so -lcap -lpam -lutil ../lib/Libattr/libattr.a
> 
> This is because libjob requires libcap and libpam.  This really has nothing to
> do with torque itself.

Thank you for confirming this.

 
> 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.

The goofy thing is that job_create() is being looked at in two different places
in configure.ac: under the conditional "Enable Cray's CSA support" and the
non-conditional arch-specific MOMLIBS section.  Both were added by ataufer and
both in the same svn checkin. 

svn blame configure.ac:
  2463    ataufer dnl
  2463    ataufer dnl enable Cray's CSA support
  2463    ataufer dnl
  2463    ataufer AC_MSG_CHECKING([whether to build Cray's CSA support])
  2463    ataufer AC_ARG_ENABLE(csa,
  2463    ataufer     [  --enable-csa            enable Cray's CSA support],
  2463    ataufer     CSA=$enableval,CSA=no)   
  2463    ataufer AC_MSG_RESULT($CSA)
   794    garrick
  2463    ataufer case "$CSA" in
  2463    ataufer   yes) AC_DEFINE([ENABLE_CSA], 1, [Define to enable Cray's CSA support])
  3541    ataufer       MOMLIBS="$MOMLIBS -L/opt/cray/job/default/lib64 -lcsa"
  3541    ataufer       AC_CHECK_LIB([job], [job_create], ,
  3541    ataufer         [AC_MSG_ERROR([--enable-csa requires job library support])])
  2463    ataufer       ;;
  2463    ataufer   no) : ;;
  2463    ataufer   *) AC_MSG_ERROR([--enable-csa should be yes or no]) ;;
  2463    ataufer esac
  2463    ataufer
  2463    ataufer
...
  3541    ataufer dnl
  3541    ataufer dnl  Check for job_create function on Cray
  3541    ataufer dnl
  3541    ataufer     AC_CHECK_LIB([job], [job_create],
  3541    ataufer       [MOMLIBS="-L/opt/cray/job/default/lib64 -ljob $MOMLIBS"
  3541    ataufer         CFLAGS="$CFLAGS -DUSEJOBCREATE"])
   556   gstaples     ;;


grep for ENABLE_CSA and USEJOBCREATE from src/ to see what they do.

So, I ask those of you that know about these things... how does libcsa relate
to libjob? To which lib should we be linking? Do we default to enabling this
behaviour?


-- 
Garrick Staples, GNU/Linux HPCC SysAdmin
University of Southern California

Life is Good!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://www.supercluster.org/pipermail/torquedev/attachments/20100708/afde6443/attachment.bin