On Wed, 4 Nov 2015 22:44:58 +0100 Juan Luis Cano <[email protected]> wrote:
> Any help with this? Just to make sure if it's doable or not, if I > cannot easily specify a search directory for the linker I will have > to give up on some updates I was doing to the conda packages. They > might be in an unusable state now. I'd suggest you trying some experiments with <dolfin_install_dir>/share/dolfin/cmake/* and instant/codegeneration.py and eventually proposing a patch. In particular, DOLFIN_3RD_PARTY_LIBRARIES seems to be missing in DOLFINConfig.cmake since https://bitbucket.org/fenics-project/dolfin/commits/ee2f3ffdd8ba01162b475194f5d742e39766b7dc Jan > > Regards, > > Juan Luis Cano > > On 2015-10-28 08:39, Juan Luis Cano wrote: > > On 2015-10-27 23:27, Jan Blechta wrote: > >> [Please, keep fenics-support in CC.] > > [Sorry, my fault] > >> I'd try to look into files > >> > >> ~/.instant/cache|error/<module_dir>/CMakeFiles/_dolfin_compile_code_<hash>.dir/flags.make > >> ~/.instant/cache|error/<module_dir>/CMakeFiles/_dolfin_compile_code_<hash>.dir/link.txt > >> > >> to figure out what's wrong with linking. Also compile.log contains > >> at the end issued c++ command you should check. > > > > I think I now start to understand what's happening. While the > > contents of DOLFIN_3RD_PARTY_LIBARIES were > > > >> -- LIBS:/home/juanlu/.miniconda3/envs/fenics_test/lib/ > >> libboost_filesystem.so/home/juanlu/.miniconda3/envs/fenics_test/lib/libboost_program_options.so/home/juanlu/.miniconda3/envs/fenics_test/lib/libboost_system.so/home/juanlu/.miniconda3/envs/fenics_test/lib/libboost_thread.so/home/juanlu/.miniconda3/envs/fenics_test/lib/libboost_iostreams.so/home/juanlu/.miniconda3/envs/fenics_test/lib/libboost_timer.so/home/juanlu/.miniconda3/envs/fenics_test/lib/libslepc.so/home/juanlu/.miniconda3/envs/fenics_test/lib/libpetsc.so/home/juanlu/.miniconda3/envs/fenics_test/lib/libcholmod.a/home/juanlu/.miniconda3/envs/fenics_test/lib/libamd.a/home/juanlu/.miniconda3/envs/fenics_test/lib/libcamd.a/home/juanlu/.miniconda3/envs/fenics_test/lib/libcolamd.a/home/juanlu/.miniconda3/envs/fenics_test/lib/libccolamd.a/home/juanlu/.miniconda3/envs/fenics_test/lib/libsuitesparseconfig.a/home/juanlu/.miniconda3/envs/fenics_test/lib/libgfortran.so/home/juanlu/.miniconda3/envs/fenics_test/lib/libz.so/home/juanlu/.miniconda3/envs/fenics_test/lib/libmpichc x > > > > , the final command is > > > >> /home/juanlu/.miniconda3/envs/fenics_test/bin/c++ -fPIC > >> -std=c++11 -fopenmp -O2 -shared -o > >> _dolfin_compile_code_XXX.so > >> CMakeFiles/_dolfin_compile_code_XXX.dir/dolfin_compile_code_XXXPYTHON_wrap.cxx.o > >> -lboost_filesystem -lboost_program_options -lboost_system > >> -lboost_thread -lboost_iostreams -lboost_timer -lslepc -lpetsc > >> -Wl,-Bstatic -lcholmod -lamd -lcamd -lcolamd -lccolamd > >> -lsuitesparseconfig -Wl,-Bdynamic -lgfortran -lz -lmpichcxx > >> -lQtGui -lQtCore -lpython2.7 > > > > which have the right libraries, but is looking on the wrong paths. > > I would expect -L/home/juanlu/.miniconda3/envs/fenics_test/lib > > somewhere, which is where all the environment libraries are > > installed, specified to DOLFIN at building time: > > > > https://github.com/Juanlu001/fenics-recipes/blob/8c41adc/dolfin/build.sh#L22 > > > > Otherwise it's picking the system libraries and leading to errors. > > > > Juan Luis > > > >> Maybe Johannes would have some advice how to debug this. > >> > >> Jan > _______________________________________________ fenics-support mailing list [email protected] http://fenicsproject.org/mailman/listinfo/fenics-support
