On Thu, Nov 5, 2015 at 2:12 PM, tschroeder <tschroe...@daad-alumni.de> wrote:
> Ok, thank you. > > The configuration now seems to have the optional include directories: > > > libmesh_optional_INCLUDES........ : -I/usr/include/eigen3 -I/usr/include > -I/home/tobias/PETSc/petsc-install//include > -I/home/tobias/PETSc/petsc-install//arch-linux2-c-debug/include > -I/home/tobias/PETSc/petsc-install/include > > libmesh_optional_LIBS............ : -L/lib -lhdf5 -Wl,-rpath,/lib -lz > -ltbb -ltbbmalloc -Wl,-rpath,/home/tobias/PETSc/petsc-install//lib > -L/home/tobias/PETSc/petsc-install//lib -lpetsc > -L/home/tobias/PETSc/petsc-install/lib -lflapack -lfblas -lX11 -lpthread > -lssl -lcrypto -lmpifort -lgfortran -lquadmath -lm -lmpicxx -lstdc++ > -Wl,-rpath,/home/tobias/PETSc/petsc-install/lib -lmpi -lgcc_s -ldl > -Wl,-rpath,/usr/lib -L/usr/lib -L/usr/lib/gcc/x86_64-redhat-linux/4.8.2 > -Wl,-rpath,/usr/lib/gcc/x86_64-redhat-linux/4.8.2 > > > > However, this path looks strange to me (it has a double // ): > > -I/home/tobias/PETSc/petsc-install//include > This should not matter at all, it may have happened if your $PETSC_DIR environment variable had a trailing forward slash. -- John ------------------------------------------------------------------------------ _______________________________________________ Libmesh-users mailing list Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
