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.
Great, that would be very helpful. I'd really like to go straight to 2.3.0 but I'm sure your experience with BuildSystem in 2.2.1 would be very helpful toward that end!
Ok. I'm attaching the debian directory (as a tar.gz) to this email.This should work out of the box if you drop it into the PETSc 2.2.1, and will likely work with small modifications on 2.3. The rules file is probably the only interesting thing there.
FYI, I know almost nothing about BuildSystem, but I don't see why the person compiling should be an expert in it. Also, I don't really see why they didn't use something like scons if they wanted to use a Python build system, but I've said that before.
If you want me to do something else, like upload PETSc 2.2.1 packages somewhere, let me know.
BTW, I can't remember if I mentioned this already, but our research group (Durham, NC) is looking for a combination sysadmin/software developer. If you know anyone who might be interested, ask them to contact me. Thanks.
Faheem.
debian.tar.gz
Description: Binary data
