On Mon, 15 Aug 2005, Faheem Mitha wrote:
On Mon, 15 Aug 2005, Adam C Powell IV wrote:
I'm only generating 'shared' libraries, and not (yet) packaging Python
bindings (didn't even know they exist).
Well, the official PETSc Python bindings (I think) require the 'dynamic'
libraries in order to compile. I'm CCing this to someone who can either
confirm or deny this.
You could also check this with the PETSc people.
The bottom line is that some things expect the PETSc 'dynamic' bindings
available in order to work.
BTW, the option for compiling I used was
./config/configure.py -PETSC_DIR=`pwd` --prefix=$(CURDIR)/debian/tmp/usr/lib
--with-dynamic=0 --with-X
The option for switching off dynamic is --with-dynamic=0.
I was told that the Python bindings for 2.3 are broken (you might want to
check with the PETSc people about that), so don't worry about enabling
these 'dynamic' libaries, whatever they are. Using the --with-dynamic=0
option is probably the easiest way to do that.
Faheem.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
