Pushed this change.
Satish
On Thu, 10 Mar 2011, Barry Smith wrote:
> > Perhaps we can have configure - not abort if 'mpiexec' not found?
>
> Sounds good. Have it not abort. perhaps a warning message? perhaps not no
> warning message needed.
>
> Barry
>
> >
> > Satish
> >
> > -
> >
On Mar 10, 2011, at 8:54 PM, Satish Balay wrote:
> On Thu, 10 Mar 2011, Barry Smith wrote:
>
>>
>> On Mar 10, 2011, at 4:46 PM, fabien delalondre wrote:
>>
>>> Hi,
>>>
>>> Which argument should I pass to pass to compile petsc on hopper II with
>>> superlu_dist, hypre and mumps (download) ? W
On Thu, 10 Mar 2011, Barry Smith wrote:
>
> On Mar 10, 2011, at 4:46 PM, fabien delalondre wrote:
>
> > Hi,
> >
> > Which argument should I pass to pass to compile petsc on hopper II with
> > superlu_dist, hypre and mumps (download) ? Without external package
> > --with-mpi=0 works fine but t
attaching the configure file that worked with petsc-dev. I haven't
tried petsc-31
Satish
On Thu, 10 Mar 2011, fabien delalondre wrote:
> Hi,
>
> Which argument should I pass to pass to compile petsc on hopper II with
> superlu_dist, hypre and mumps (download) ? Without external package
> --with
Hi,
Which argument should I pass to pass to compile petsc on hopper II with
superlu_dist, hypre and mumps (download) ? Without external package
--with-mpi=0 works fine but then the external packages complain about it (no
mpi specified). I tried to use and also modify the arch-cray-xt5-opt.py
confi
On Mar 10, 2011, at 4:46 PM, fabien delalondre wrote:
> Hi,
>
> Which argument should I pass to pass to compile petsc on hopper II with
> superlu_dist, hypre and mumps (download) ? Without external package
> --with-mpi=0 works fine but then the external packages complain about it (no
> mpi sp
