Rajeev --
I'm interested in fixing this in the LAM code base so that future users
don't have this problem. Those line numbers for me seem to be in the
middle of logic blocks -- can you confirm that [4304, 4382] are the
correct line numbers for the ROMIO configure that ships with LAM/MPI?
Thanks!
On May 18, 2005, at 1:42 PM, Rajeev Thakur wrote:
>
>
>
> Rossen,
> You need to delete lines 4304--4382 (both included). I just
> deleted
> them, ran configure in the top-level directory, and it created a
> Makefile in
> the romio directory.
>
> Rajeev
>
>> Date: Wed, 18 May 2005 19:36:03 +0900
>> From: Rossen Apostolov <rpa_at_[hidden]>
>> Subject: LAM: Re: Configuring ROMIO problem
>> To: lam_at_[hidden]
>> Message-ID: <428B1A93.6030002_at_[hidden]>
>> Content-Type: text/plain; charset=ISO-2022-JP
>>
>> I had the problem configuring ROMIO described here
>> http://www.lam-mpi.org/MailArchives/lam/2005/05/10455.php ,
>> i.e. the configure script gets stuck when performing
>> checks for lockd.
>> I uncommented the corresponding lines 4307~4378 ( for lam-7.0.6),
>> as Rajeev recommened, and configuration passed.
>>
>> But then make failed saying
>> ......
>> make[2]: Entering directory `/misc/home/pi/rossen/src/lam-7.1.1/romio'
>> make[2]: *** No targets specified and no makefile found. Stop.
>> ...........
>> Same for lam-7.1.1.
>>
>> So, disabling the lockd checks resulted in skipping configuration for
>> ROMIO altogether...? How can this be fixed?
>>
>> Thanks,
>> Rossen
>
> _______________________________________________
> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
>
--
{+} Jeff Squyres
{+} jsquyres_at_[hidden]
{+} http://www.lam-mpi.org/
|