On Thu, Sep 11, 2008 at 8:53 AM, John Peterson <jwpeterson@...> wrote:
> On Thu, Sep 11, 2008 at 8:42 AM, Rafael Santos Coelho
> <rafaelsantoscoelho@...> wrote:
>> Hi all,
>> I'm having a hard time trying to install libMesh 0.6.3-rc1 with MPICH
>> 1.2.7p1. Here's what I do:
>> 1) Build MPICH firstly, outside of PETSc 2.3.3
>> 2) Build PETSc afterwards using the following commands:
>> $ export PETSC_DIR=$PWD
>> $ export PETSC_ARCH=linux-gnu-dbg
>> $ ./configure --prefix=$PWD --with-cc=gcc --with-fc=0 --with-cxx=g++
>> --with-mpi-compilers=0 --with-shared=1 --with-debugging=1 --with-mpi
>> --with-mpi-dir=/home/rafael/mpich-1.2.7p1 --download-c-blas-lapack=1
>> make all test
>> 3) Build libMesh at last:
>> $ ./configure --prefix=$PWD --enable-everything
>> --with-mpi=/home/rafael/mpich-1.2.7p1 --with-cxx=mpicxx --with-cc-mpicc
>> $ make
> This is a little different than the way I normally configure. Be sure
> PETSC_DIR is set and try:
> CXX=mpicxx CC=mpicc ./configure --enable-everything
and of course, if PETSc was built with a Fortran compiler be sure to
provide that to libmesh's configure step as well, e.g. F77=mpif77.
> And post the output of configure here if you still can't get things working.
>> Now, everything seems to be going well, but then, in the end, I get these
>> Building bin/amr
>> g++: /home/rafael/libmesh-0.6.3-rc1/lib/i686-pc-linux-gnu_opt/libmesh.so:
>> linker input file unused because linking not done
> This sounds like you have a naked "-L" somewhere in your link line.
> If you do make echo you can look at the linker flags but there are a
> lot of them and it may be hard to spot the bad part immediately.