Re: Error with using downloaded mpich and lammpi shared

["Matthew Knepley" <knepley@xxxxxxxxx>]

On 4/8/07, Ben Tay <zonexo@xxxxxxxxx> wrote:
> Hi,
>
> when trying to configure usign download-mpich=1, I got this error:
>    =================================================================================
>
>
>     Running configure on MPICH; this may take several
> minutes
>
>
> =================================================================================
>
>
>
>
>
>
> *********************************************************************************
>          UNABLE to CONFIGURE with GIVEN OPTIONS    (see configure.log for
> details):
> ---------------------------------------------------------------------------------------
> Error running configure on MPICH: Could not execute 'cd
> /lsftmp/g0306332/petsc-
> 2.3.2-p8-new/externalpackages/mpich2-1.0.4p1;./configure
> --prefix=/lsftmp/g0306332/petsc-2.3.2-p8-new/externalpackages/mpich2-1.0.4p1/ia64
> CC="/scratch1/g0306332/intel/cc/bin/icc  -fPIC -O "
> CXX="g++  -Wall -Wwrite-strings -O   -fPIC "
> F90="/scratch1/g0306332/intel/fc/bin/ifort  -fPIC -O  "
> F77="/scratch1/g0306332/intel/fc/bin/ifort  -fPIC -O  "
> --enable-sharedlibs=gcc --without-mpe --with-pm=gforker':
> Configuring MPICH2 version 1.0.4p1 with
> '--prefix=/lsftmp/g0306332/petsc-2.3.2-p8-new/externalpackages/mpich2-1.0.4p1/ia64'
> 'CC=/scratch1/g0306332/intel/cc/bin/icc  -fPIC -O '
> 'CXX=g++  -Wall -Wwrite-strings -O   -fPIC '
> 'F90=/scratch1/g0306332/intel/fc/bin/ifort  -fPIC -O  '
> 'F77=/scratch1/g0306332/intel/fc/bin/ifort  -fPIC -O  '
> '--enable-sharedlibs=gcc' '--without-mpe' '--with-pm=gforker' 'CFLAGS=-mp
> -DANSI -I/app1/ia64/imsl/imsl/cnl600/itanium/include'
> 'F90FLAGS=-w -nologo -fpp
> -I/app1/ia64/imsl/CTT6.0/include/linx64_i9
> -I/usr/local/mpich- 1.2.7p1/include' 'FFLAGS=-w -nologo -fpp
> -I/app1/ia64/imsl/CTT6.0/include/linx64_i9
> -I/usr/local/mpich-1.2.7p1/include'
> Executing mpich2prereq in
> /lsftmp/g0306332/petsc-2.3.2-p8-new/externalpackages/mpich2-
> 1.0.4p1/src/mpid/ch3 with
> Executing mpich2prereq in
> /lsftmp/g0306332/petsc-2.3.2-p8-new/externalpackages/mpich2-1.0.4p1/src/mpid/ch3/channels/sock
> sourcing /lsftmp/g0306332/petsc-2.3.2-p8-new/externalpackages/mpich2-
> 1.0.4p1/src/pm/gforker/mpich2prereq
> checking for gcc... /scratch1/g0306332/intel/cc/bin/icc
> -fPIC -O
> checking for C compiler default output file name... a.out
> checking whether the C compiler works... yes
> checking whether we are cross compiling... no
> checking for suffix of executables...
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether /scratch1/g0306332/intel/cc/bin/icc  -fPIC
> -O  accepts -g... yes
> checking for /scratch1/g0306332/intel/cc/bin/icc  -fPIC -O
> option to accept ANSI C... none needed
> checking for type of weak symbol support... pragma weak
> checking whether __attribute__ ((weak)) allowed... yes
>  checking for multiple weak symbol support... yes
> configure: error: The values of the environment variables F77
> (=/scratch1/g0306332/intel/fc/bin/ifort  -fPIC -O  ) and FC
> (=ifort) are not the same.  Unset one or both and rerun configure
> *********************************************************************************
>
>  it seems that the F77 and FC environment variables are different. I want to
> use (=/scratch1/g0306332/intel/fc/bin/ifort). How can I
> configure them?

Do not set any environment variables. Let configure control it.

>  If I use the lammpi which the sch provide, I got this error msg:
> ./config/configure.py --with-cc=icc --with-fc=ifort
> --download-f-blas-lapack=1 --download-hypre=1 --with-debugging=0
> --with-mpi-include=/app1/ia64/lammpi/include/
> --with-mpi-lib=/app1/ia64/lammpi/lib/libmpi.la
> --with-mpirun=/app1/ia64/lammpi/bin/mpirun --with-x=0
> --with-shared
>
> I also replace libmpi.la with libmpi.a but both cannot work.
>
>
> Shared libraries cannot be built using MPI provided.
> Either rebuild with --with-shared=0 or rebuild MPI with shared library
> support
>
> What's the extension for shared libraries for ia64 platform? Is it *.so?

I am fairly sure since it is 64-bit that the shared library is either
not PIC, or
we cannot build shared libraries for this system.

 Matt

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