The problem was that the environment variable PETS_ARCH was not correctly set. I could compile and run all the tests in make check. Sorry for all the problems.
Now I would like to install it with VTK. I have version 6.1 installed in my computer. I have the options --enable-vtk --with-vtk-include=/usr/local/include/vtk-6.1' '--with-vtk-lib=/usr/local/lib/ in the configure command line. The directory /usr/local/lib is where the vtk libraries are. However, it looks like Libmesh is asking me for different library names. For example, it cannot find -lvtkIO, but in that directory I have libraries such as: libvtkIOAMR-6.1.so, libvtkIOEnSight-6.1.so, and many more with same initial letters libvtkIO*. Is it because of the VTK version? Similar issues happen with the other vtk libraries that cannot find. configure:32183: checking for main in -lvtkIO configure:32202: /home/miguel/petsc-3.4.4/arch-linux2-c-debug/bin/mpicxx -o conftest conftest.cpp -lvtkIO -lvtkCommon -lvtkFiltering -L/lib -lhdf5 -Wl,-rpath,/lib -Wl,-rpath,/usr/local/lib/ -L/usr/local/lib/ -lvtkIO -lvtkCommon -lvtkFiltering >&5 /usr/bin/ld: cannot find -lvtkIO /usr/bin/ld: cannot find -lvtkCommon /usr/bin/ld: cannot find -lvtkFiltering /usr/bin/ld: cannot find -lvtkIO /usr/bin/ld: cannot find -lvtkCommon /usr/bin/ld: cannot find -lvtkFiltering collect2: error: ld returned 1 exit status configure:32202: $? = 1 configure: failed program was: Thanks in advance. Miguel On Thu, May 15, 2014 at 11:57 AM, John Peterson <[email protected]>wrote: > > > > On Thu, May 15, 2014 at 10:46 AM, Miguel Angel Salazar de Troya < > [email protected]> wrote: > >> I have seen in the configure output this message >> >> checking /home/miguel/petsc-3.4.4/include/petscversion.h usability... yes >> checking /home/miguel/petsc-3.4.4/include/petscversion.h presence... yes >> checking for /home/miguel/petsc-3.4.4/include/petscversion.h... yes >> <<< Warning: configuring in serial - no MPI in PETSC config >>> >> >> This might be the problem. I don't understand why PETSc is not configured >> in parallel even though I ran tests in parallel after the installation. I >> wil try to fix this. I just wanted to leave this clarification here. >> > > > libmesh *should* work with a no-MPI PETSc, but probably not if you specify > the MPI compiler scripts as your compilers! > > We could probably do a better job of detecting this situation, but it's so > weird it's probably not worth it. > > Is the issue that you installed a no-MPI PETSc through an Ubuntu package? > > -- > John > -- *Miguel Angel Salazar de Troya* Graduate Research Assistant Department of Mechanical Science and Engineering University of Illinois at Urbana-Champaign (217) 550-2360 [email protected] ------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
