On Wed, Oct 31, 2012 at 05:34:20PM +0000, Garth N. Wells wrote: > On Wed, Oct 31, 2012 at 4:57 PM, Anders Logg <l...@simula.no> wrote: > > On Wed, Oct 31, 2012 at 09:34:06AM +0000, Garth N. Wells wrote: > > > >> Not using Dorsal, I don't know. I do not add the paths of my > >> home-baked libraries to LD_LIBRARY_PATH, but rely on CMake to 'bake > >> in' the library paths (rpath). I like this because I can be sure which > >> libs are being linked in, rather than random bits and pieces that lie > >> in the system paths. > >> > >> What error do you get from Dorsal? > > > > I don't get the errors from Dorsal. The error is when I build > > everything except DOLFIN with Dorsal, then build DOLFIN against that > > build with cmake.local. > > > > What happens then is Python applications (not C++ which are working > > fine) fail with this error: > > > > Try building DOLFIN with the MPI compiler wrappers.
ok, I will try that. > It looks like the MPI libs that you built cannot find each other. I've > found that I do have to add the path of some shared libs to get the > Python module to link correctly. Maybe it works with RPATH=OFF > because it picks up system installed MPI libs (which are usually > installed if you have other packages installed, e.g. ParaView). No, the Dorsal build script will explicitly (ask to) remove any mpi libs on the system. I don't have any MPI other than the one installed by Dorsal. -- Anders _______________________________________________ Mailing list: https://launchpad.net/~dolfin Post to : dolfin@lists.launchpad.net Unsubscribe : https://launchpad.net/~dolfin More help : https://help.launchpad.net/ListHelp
