Woof -- I suck. How did I miss that?
It explains why the tm tree is missing from the nightly (its configure
script failed, so it was ignored). Fixed in SVN now; it should be in
the nightly tomorrow.
On Feb 21, 2005, at 4:07 AM, Ricky Tang wrote:
> Hello Jeff,
>
>
> The boot/tm tree is mysteriously missing in that nightly snapshot...
>
> [shtang_at_precision shtang]$ ls -al lam-7.2b1r10061/share/ssi/boot
> total 56
> drwx------ 7 shtang shtang 4096 Feb 20 15:22 .
> drwx------ 8 shtang shtang 4096 Feb 20 15:22 ..
> drwx------ 2 shtang shtang 4096 Feb 20 15:22 base
> drwx------ 4 shtang shtang 4096 Feb 20 15:22 bproc
> drwx------ 4 shtang shtang 4096 Feb 20 15:22 globus
> -rw------- 1 shtang shtang 918 Feb 20 15:00 Makefile.am
> -rw------- 1 shtang shtang 24068 Feb 20 15:03 Makefile.in
> drwx------ 4 shtang shtang 4096 Feb 20 15:22 rsh
> drwx------ 4 shtang shtang 4096 Feb 20 15:22 slurm
> [shtang_at_precision shtang]$
>
>
> After install SVN and checkout the tree, run autogen, configure script
> of tm module is broken:
>
> checking if need special C compiler/linker flags... none needed
> checking for C optimization flags... -O
> ./configure: line 4974: syntax error near unexpected token `)'
> ./configure: line 4974: ` { (exit 1); exit 1; }; } )'
>
> Seems that there is an extra close parenthesis in the line?
> AC_MSG_ERROR([*** Cannot find working libpbs.]) )
>
>
> Best Regards,
> Ricky
>
>
> On Fri, 2005-02-18 at 09:00 -0500, Jeff Squyres wrote:
>> On Feb 17, 2005, at 11:37 PM, Ricky Tang Siu Hong wrote:
>>
>>> May I request to add a switch to configure script of ssi/boot/tm
>>> module?
>>>
>>> On our x86_64 installation we put tm library in somewhere like
>>> /usr/torque/lib64, but the LAM only searchs at /usr/torque/lib.
>>
>> Actually, I'd prefer if our configure script just checked both places
>> -- that way there's no need for a new configure switch (when a script
>> can be smart enough and then the user doesn't have to worry about
>> something extra, that's a Good Thing). I don't have a 64 bit Torque
>> installation to try this out, however. Can you try the following
>> patch
>> (I've committed this to SVN; it'll be in tomorrow's nightly snapshot):
>>
>> Index: configure.stub
>> ===================================================================
>> --- configure.stub (revision 10059)
>> +++ configure.stub (working copy)
>> @@ -51,14 +51,23 @@
>> AC_CHECK_LIB(nsl, main, ,)
>>
>> #
>> -# need to find libpbs
>> +# Sometimes the TM library will be in $prefix/lib, sometimes it will
>> +# be in $prefix/lib64. Try them both.
>> #
>> -if test ! -z "$TMDIR"; then
>> +if test -n "$TMDIR" -a -d "$TMDIR/lib"; then
>> + LDFLAGS_orig="$LDFLAGS"
>> LDFLAGS="$LDFLAGS -L$TMDIR/lib"
>> fi
>> +AC_CHECK_LIB(pbs, tm_init, HAPPY=1, HAPPY=0)
>>
>> -AC_CHECK_LIB(pbs, tm_init, ,
>> +if test "$HAPPY" = "0" -a -n "$TMDIR" -a -d "$TMDIR/lib64"; then
>> + LDFLAGS="$LDFLAGS_orig -L$TMDIR/lib64"
>> + AC_CHECK_LIB(pbs, tm_finalize, HAPPY=1, HAPPY=0)
>> +fi
>> +
>> +if test "$HAPPY" = "0"; then
>> AC_MSG_ERROR([*** Cannot find working libpbs.]) )
>> +fi
>>
>> #
>> # done with boot tm configure.stub
>>
>>
> --
> Ricky Tang
> Cluster Technology Limited
> Center of Large Scale Computation
> shtang_at_[hidden]
>
> _______________________________________________
> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
>
--
{+} Jeff Squyres
{+} jsquyres_at_[hidden]
{+} http://www.lam-mpi.org/
|
