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

Michael Jennings mej at lbl.gov
Thu Jul 8 19:16:36 MDT 2010

On Thursday, 08 July 2010, at 20:50:05 (-0400),
Troy Baer wrote:

> 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 

That makes invalid assumptions about the dependencies of libjob (which
could change out from under torque at any time).

The tricky part here is that AC_CHECK_LIB() (or what I believe it uses
under the hood, AC_TRY_LINK()) will succeed because libcap and libpam
are both shared library dependencies of libjob which will be found by
the linker at runtime.  Neither of these autoconf macros use libtool
to link, which is really where the problem comes in (trying to pull in
-lcap and -lpam at link time directly rather than letting the
dependencies built into the .so do their job).  So I doubt there's a
reasonable solution within torque.

Did you check for libjob.la as I recommended?  If so, and if it's
there, remove those two libraries from it (or remove that file
altogether).  This is really a packaging/distribution problem, because
libjob.la should only be present if (e.g.) libjob-devel is present,
and libjob-devel MUST require libcap-devel and libpam-devel to
preserve the link-time dependencies the .la file defines.


Michael Jennings <mej at lbl.gov>
Linux Systems and Cluster Engineer
High-Performance Computing Services
Bldg 50B-3209E      W: 510-495-2687
MS 050C-3396        F: 510-486-8615

More information about the torquedev mailing list