← Back to team overview

dolfin team mailing list archive

Re: UMFPACK test

 

On Tue, Mar 11, 2008 Anders Logg wrote:
> On Tue, Mar 11, 2008 at 03:32:19PM +0100, Ilmar Wilbers wrote:
>> The atlas3-sse2-dev package does things differently from the normal
>> expected atlas. In umfpack.py we expect the atlas libraries to reside in
>> /usr/lib/atlas. This is the case with altas3-base-dev, but not with the
>> package you tried.
>>
>> Setting ATLAS_DIR does the trick. Alternatively, using atlas3-base-dev,
>> the library files are located at the expected location.
>
> ok, I fixed this by setting the symlink manually.
>
> I now have a similar problem with PETSc:
>
> `pkg-config --variable=compiler dolfin` -o demo main.o `pkg-config
> --cflags dolfin` `pkg-config --libs dolfin`
> /usr/bin/ld: warning: libpetscsnes.so, needed by
> /home/logg/local/lib/libdolfin.so, not found (try using -rpath or
> -rpath-link)
> /usr/bin/ld: warning: libpetscmat.so, needed by
> /home/logg/local/lib/libdolfin.so, not found (try using -rpath or
> -rpath-link)
> /usr/bin/ld: warning: libpetscvec.so, needed by
> /home/logg/local/lib/libdolfin.so, not found (try using -rpath or
> -rpath-link)
> /usr/bin/ld: warning: libpetscts.so, needed by
> /home/logg/local/lib/libdolfin.so, not found (try using -rpath or
> -rpath-link)
> /usr/bin/ld: warning: libpetsc.so, needed by
> /home/logg/local/lib/libdolfin.so, not found (try using -rpath or
> -rpath-link)
> /usr/bin/ld: warning: libpetscdm.so, needed by
> /home/logg/local/lib/libdolfin.so, not found (try using -rpath or
> -rpath-link)
> /usr/bin/ld: warning: libpetscksp.so, needed by
> /home/logg/local/lib/libdolfin.so, not found (try using -rpath or
> -rpath-link)
> /home/logg/local/lib/libdolfin.so: undefined reference to
> `VecGetArray_Private(_p_Vec*, double**)'
> /home/logg/local/lib/libdolfin.so: undefined reference to
> `MatView(_p_Mat*, _p_PetscViewer*)'
> /home/logg/local/lib/libdolfin.so: undefined reference to
> `KSPView(_p_KSP*, _p_PetscViewer*)'
> ...
>
>
> pkg-config --libs dolfin returns
>
>   -L/home/logg/local/lib -ldolfin -lxml2
>
> Did I miss something?

What does your dolfin.pc look like? Is it located somewhere in your
PKG_CONFIG_PATH variable? Or is it perhaps an old dolfin.pc file that is
used?

Johannes

> --
> Anders
>
>
>
>> ilmar
>>
>> Anders Logg wrote:
>> > On Tue, Mar 11, 2008 at 02:59:59PM +0100, Ilmar Wilbers wrote:
>> >
>> >> What does your /etc/ld.so.conf look like?
>> >>
>> >> I use atlas3-base-dev, and that works fine. It should work just as
>> fine
>> >> with atlas3-sse2-dev.
>> >>
>> >> I think the problem is the exact same as I raised earlier, where
>> adding
>> >> the PETSC_TS_LIB variable to petsc.py did the trick.
>> >>
>> >> Will look into this now. What does your /etc/ld.so.conf look like?
>> >>
>> >> ilmar
>> >>
>> >
>> > My /etc/ld.so.conf looks like this:
>> >
>> >   include /etc/ld.so.conf.d/*.conf
>> >   /usr/lib/atlas/sse2
>> >   /usr/lib/sse2
>> >   /usr/lib/atlas/sse
>> >   /usr/lib/sse
>> >   /usr/lib/atlas
>> >
>> > and my LD_LIBRARY_PATH is set to
>> >
>> >   /home/logg/local/lib
>> >
>> >
>> _______________________________________________
>> DOLFIN-dev mailing list
>> DOLFIN-dev@xxxxxxxxxx
>> http://www.fenics.org/mailman/listinfo/dolfin-dev
> _______________________________________________
> DOLFIN-dev mailing list
> DOLFIN-dev@xxxxxxxxxx
> http://www.fenics.org/mailman/listinfo/dolfin-dev
>




Follow ups

References