dolfin team mailing list archive

[Barry Smith <petsc-maint@xxxxxxxxxxx>]

>   If you use dynamic libraries with PETSc, then the load paths are compiled in (you can
> redirect them with command-line arguments, but this is the default). Thus, moving them
> from the directory into which the package installs them breaks the load. There a couple
> ways to fix this. I will think about it (since I have to leave for dinner now).

  Matt,

   This is very likely not the problem. When a --prefix is used the libraries are 
built with the correct paths for the dynamic libraries.

  Barry

On Tue, 5 Jul 2005, Matthew Knepley wrote:

> Faheem Mitha <faheem@xxxxxxxxxxxxx> writes:
> > Hi,
> >
> > I modified the PETSc build.
> >
> > However, I have now encountered another problem. Here are steps to reproduce:
> >
> > 1) Install PETSc using my Debian package.
> >
> > 2) Compile DOLFIN against this package, using
> >
> > ./configure --with-petsc-dir=/usr/lib/petsc-2.2.1
> >
> > 2) When I try running the demos (in src/demos) in the DOLFIN source tree, I get link errors, which appear to be that
> > something thinks that the PETSc libraries are still where they were built, namely
> >
> > /usr/local/src/petsc/petsc/petsc-2.2.1/debian/tmp/usr/lib/petsc-2.2.1/
> >
> > I'm not sure what is causing this problem or how to resolve it. The easist thing would be if one of the DOLFIN
> > developers could repeat the above steps to reproduce the problem.
> 
>   If you use dynamic libraries with PETSc, then the load paths are compiled in (you can
> redirect them with command-line arguments, but this is the default). Thus, moving them
> from the directory into which the package installs them breaks the load. There a couple
> ways to fix this. I will think about it (since I have to leave for dinner now).
> 
>      Matt
> 
> > Thanks.                                                         Faheem.
> >
> >
> > *************************************************************************
> > sarge1-root)faheem@io:/usr/local/src/dolfin/dolfin-0.5.7/src/demo/fem$ ./dolfin-fem
> > Reading mesh from file "tetrahedron.xml.gz".
> > Computing mesh connectivity:
> >    Found 4 nodes
> >    Found 1 cells
> >    Created 6 edges
> >    Created 4 faces
> >    Sorting mesh entities locally.
> > Initializing PETSc (ignoring command-line arguments).
> > --------------------------------------------------------------------------
> > Petsc Version 2.2.1, Patch 42, Released August, 18, 2004
> > See docs/changes/index.html for recent updates.
> > See docs/troubleshooting.html for hints about trouble shooting.
> > See docs/index.html for manual pages.
> > -----------------------------------------------------------------------
> > unknown on a linux-gnu named io by faheem Tue Jul  5 21:39:04 2005
> > Libraries linked from /usr/local/src/petsc/petsc/petsc-2.2.1/lib/libg_c++/linux-gnu
> > -----------------------------------------------------------------------
> > [0]PETSC ERROR: PetscInitialize_DynamicLibraries() line 64 in src/sys/src/dll/reg.c
> > [0]PETSC ERROR: Unable to open file!
> > [0]PETSC ERROR: Unable to locate PETSc dynamic library
> > /usr/local/src/petsc/petsc/petsc-2.2.1/debian/tmp/usr/lib/petsc-2.2.1/lib/libg_c++/linux-gnu/libpetsc
> >   You cannot move the dynamic libraries!
> >   or remove USE_DYNAMIC_LIBRARIES from ${PETSC_DIR}/bmake/$PETSC_ARCH/petscconf.h
> >   and rebuild libraries before moving!
> > [0]PETSC ERROR: PetscInitialize() line 446 in src/sys/src/objects/pinit.c
> > [0]PETSC ERROR: ClassRegLogGetClass() line 290 in src/sys/src/plog/classLog.c
> > [0]PETSC ERROR: Invalid argument!
> > [0]PETSC ERROR: Invalid object cookie 0!
> > [...]
> >
> >
> >
> 
>