Using existing mpich for new built

[Matthew Knepley]

When you rebuild, you use the same option, --download-mpich and it will do the
correct thing.

  Matt

On 5/4/07, Ben Tay <zonexo at gmail.com> wrote:
> Hi,
>
> I just compiled a shared version of PETSc. I realised that I've forgotten to
> add --download-hypre=1 in the configure. Hence I need to rebuilt the PETSc.
> Initially I had used --download-mpich=1 to built the mpich.
>
> Before the "make all test", I got:
>
> ...
>
> MPI:
>   Includes:
> ['/nfs/lsftmp/g0306332/petsc-2.3.2-p8/externalpackages/mpich2-1.0.4p1/atlas3/include']
>   Library:
> ['/nfs/lsftmp/g0306332/petsc-2.3.2-p8/externalpackages/mpich2-1.0.4p1/atlas3/lib/libmpich.a',
> ' libnsl.a', 'librt.a']
>
> ...
>
> I tried to "reuse" this library for the new built but it failed. It says
>
>          UNABLE to CONFIGURE with GIVEN OPTIONS    (see configure.log for
> details):
> ---------------------------------------------------------------------------------------
> Shared libraries cannot be built using MPI provided.
> Either rebuild with --with-shared=0 or rebuild MPI with shared library
> support
>
> My option is
> --with-mpi-include=/nfs/lsftmp/g0306332/petsc-2.3.2-p8/externalpackages/mpich2-1.0.4p1/atlas3/include
> --with-mpi-lib=/nfs/lsftmp/g0306332/petsc-2.3.2-p8/externalpackages/mpich2-1.0.4p1/atlas3/lib/libmpich.a
>
> I also changed libmpich.a to libmpich.so but the same error occurs. Is there
> any way I can use the mpich which I built earlier.
>
> Thanks.


-- 
The government saving money is like me spilling beer. It happens, but
never on purpose.