[mpich-discuss] try to install MPICH2 on SGI under local account

[Mei, Rui]

In regards to the 3rd point,  The building directory MPICH2-1.3a2 and the installation directory mpi are both under /u/home/rum06003/ on the SGI server. So they should bear the same time clock. I am not sure if I have understand your point 
clearly.  That SGI server is not mounted on my local machine, I usually ssh to that machine. So I do not know how to build it from 
my local machine /tmp and set the prefix to be /u/home/rum06003/mpi on that SGI machine.

Thank you for any suggestion or clarification.

Rui
________________________________________
From: mpich-discuss-bounces at mcs.anl.gov [mpich-discuss-bounces at mcs.anl.gov] On Behalf Of Pavan Balaji [balaji at mcs.anl.gov]
Sent: Wednesday, May 26, 2010 11:06 PM
To: mpich-discuss at mcs.anl.gov
Subject: Re: [mpich-discuss] try to install MPICH2 on SGI under local account

Aha. It looks like a timestamp issue. Your "make" is causing simplemake
to be re-executed, which should never happen unless the timestamp of the
Makefile.in is more recent than the Makefile.

There are a bunch of problems that need to be fixed here:

1. When the time stamps don't match for released versions, we should
just throw an error during make, instead of leading to such cryptic bugs.

2. You should not have to give the --with-atomic-primitives=no option
when using --with-device=ch3:sock.

3. For some reason you are getting incorrect time stamps for your files.

(1) and (2) are a problem with MPICH2, which I'll fix. (3) is a problem
with your setup. Are your files on an NFS server, or some other shared
file system? Can you make sure the time stamp on your login node (or
which ever node you are building MPICH2 on) is the same as your file
server? Alternatively, you can try building on a local file-system such
as /tmp. Your prefix can still be /u/home/rum06003/mpi.

  -- Pavan

On 05/26/2010 09:53 PM, Mei, Rui wrote:
> I first tried ./configure --prefix=/u/home/rum06003/mpi --with-device=ch3:sock 2>&1 | tee c1.txt and it gave me error (see c1.txt)
> and suggest to use --with-atomic-primitives=no option.
>
> So I then tried ./configure --prefix=/u/home/rum06003/mpi --with-atomic-primitives=no 2>&1 | tee c.txt (it's ok, see c.txt)
>
> Then I executed: make 2>&1 | tee m.txt (it gave error, see m.txt)
>
> At last I executed: make install 2>&1 | tee mi.txt (it also gave error, see mi.txt)
>
> And there is indeed a difference between Makefile.in an dMakefile.in.original.
>
> Thank you for any suggestion.
>
> Rui
> ________________________________________
> From: mpich-discuss-bounces at mcs.anl.gov [mpich-discuss-bounces at mcs.anl.gov] On Behalf Of Pavan Balaji [balaji at mcs.anl.gov]
> Sent: Wednesday, May 26, 2010 9:26 PM
> To: mpich-discuss at mcs.anl.gov
> Subject: Re: [mpich-discuss] try to install MPICH2 on SGI under local account
>
> On 05/26/2010 08:20 PM, Pavan Balaji wrote:
>> 3. Run configure using:
>>
>> % ./configure --prefix=/u/home/rum06003/mpi --with-device=ch3:sock 2>&1
>> | tee c.txt
>
> Small correction here. I'll need you to run both configure and make:
>
> % ./configure --prefix=/u/home/rum06003/mpi --with-device=ch3:sock 2>&1
> | tee c.txt
>
> % make
>
> ... then send me both Makefile.in and Makefile.in.original
>
> Thanks,
>
>   -- Pavan
>
> --
> Pavan Balaji
> http://www.mcs.anl.gov/~balaji
> _______________________________________________
> mpich-discuss mailing list
> mpich-discuss at mcs.anl.gov
> https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> mpich-discuss mailing list
> mpich-discuss at mcs.anl.gov
> https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss

--
Pavan Balaji
http://www.mcs.anl.gov/~balaji
_______________________________________________
mpich-discuss mailing list
mpich-discuss at mcs.anl.gov
https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss