changes to PETSc-dev bmake system and library locations

2007-06-11 Thread Todd Munson
I just downloaded the new updates and tried configuring the development version and get the following python errors...It may be a problem on my side. I'll try with a new clone of the repository... akita % ./config/configure.py --with-c++

changes to PETSc-dev bmake system and library locations

2007-06-11 Thread Matthew Knepley
Maybe you have an old BuildSystem? Matt On 6/11/07, Todd Munson tmunson at mcs.anl.gov wrote: I just downloaded the new updates and tried configuring the development version and get the following python errors...It may be a problem on my side. I'll try with a new clone of the

changes to PETSc-dev bmake system and library locations

2007-06-11 Thread Todd Munson
I had configured and built petsc-dev prior to updating to the new configuration system. That did not work...once the update happens things get screwed up and nothing in the build system works. Maybe the BuildSystem module was old, but I would figure that it should get updated when you check for

changes to PETSc-dev bmake system and library locations

2007-06-11 Thread Lisandro Dalcin
On 6/8/07, Barry Smith bsmith at mcs.anl.gov wrote: Goal: Support the GNU; config/configure.py; make; make install model including all external packages PETSc builds for you. After make install PETSC_ARCH should not be needed. Barry, I really do not like this... this approach does not

changes to PETSc-dev bmake system and library locations

2007-06-11 Thread Satish Balay
On Mon, 11 Jun 2007, Lisandro Dalcin wrote: On 6/8/07, Barry Smith bsmith at mcs.anl.gov wrote: Goal: Support the GNU; config/configure.py; make; make install model including all external packages PETSc builds for you. After make install PETSC_ARCH should not be needed. Barry, I

changes to PETSc-dev bmake system and library locations

2007-06-11 Thread Lisandro Dalcin
On 6/11/07, Satish Balay balay at mcs.anl.gov wrote: On Mon, 11 Jun 2007, Lisandro Dalcin wrote: There is nothing sepcial about having all installs inside a single PETSC_DIR. in the prefix model - the user specifies prefix just like any other package. For eg: --prefix=/usr/local

changes to PETSc-dev bmake system and library locations

2007-06-11 Thread Satish Balay
On Mon, 11 Jun 2007, Satish Balay wrote: However you can still have multiple configure installs by specifying different 'prefix' for each configure. I believe this is how autoconf/gnu install model is supporsed to work. I should add that one motivation to support gnu/autoconf? 'make insall'

changes to PETSc-dev bmake system and library locations

2007-06-11 Thread Satish Balay
On Mon, 11 Jun 2007, Lisandro Dalcin wrote: On 6/11/07, Satish Balay balay at mcs.anl.gov wrote: There is nothing sepcial about having all installs inside a single PETSC_DIR. in the prefix model - the user specifies prefix just like any other package. For eg: --prefix=/usr/local

changes to PETSc-dev bmake system and library locations

2007-06-11 Thread Lisandro Dalcin
On 6/11/07, Satish Balay balay at mcs.anl.gov wrote: I should add that one motivation to support gnu/autoconf? 'make insall' model as closly as possible - is to make it easy for 'packagers' [deb,rpm etc..] to package PETSc OK, this make sense... I'll try this when I have some free time, I've

changes to PETSc-dev bmake system and library locations

2007-06-11 Thread Lisandro Dalcin
I think 'conf/variables' needs a bit more of work. I am not sure about what to do, the problem is here: PETSC_LIB_DIR = ${PETSC_DIR}/${PETSC_ARCH}/lib PETSC_INCLUDE = -I${PETSC_DIR} -I${PETSC_DIR}/${PETSC_ARCH}/include -I${PETSC_DIR}/include \

more comments about new build system

2007-06-11 Thread Lisandro Dalcin
If one of the goals of the new build system is to be more symmetric with the GNU model, in order to make life easier for packagers, so I think the '$PETSC_PREFIX/conf' location should be renamed, perhaps to '$PETSC_PREFIX/share/petsc'. I believe 'conf' is not a 'standard' location. -- Lisandro

more comments about new build system

2007-06-11 Thread Barry Smith
Lisandro, Good point. etc was also suggested. Adding the petsc is kind of ugly with the non-installed version, for example petsc-dev/$PETSC_ARCH/shared/petsc/petscrules instead of petsc-dev/$PETSC_ARCH/shared/petscrules These things are still up in the air and will be adjusted as

more comments about new build system

2007-06-11 Thread Barry Smith
I actually used conf because it is somewhat descriptive but won't miss up with other choices (like etc). Barry On Mon, 11 Jun 2007, Barry Smith wrote: Lisandro, Good point. etc was also suggested. Adding the petsc is kind of ugly with the non-installed version, for example

changes to PETSc-dev bmake system and library locations

2007-06-11 Thread Barry Smith
On Mon, 11 Jun 2007, Lisandro Dalcin wrote: I think 'conf/variables' needs a bit more of work. I am not sure about what to do, the problem is here: PETSC_LIB_DIR = ${PETSC_DIR}/${PETSC_ARCH}/lib PETSC_INCLUDE = -I${PETSC_DIR} -I${PETSC_DIR}/${PETSC_ARCH}/include

changes to PETSc-dev bmake system and library locations

2007-06-11 Thread Barry Smith
On Mon, 11 Jun 2007, Satish Balay wrote: However I think the requirement of 'PETSC_DIR' might still be a minor hurdle for this mode. [the alternative would be providing compiler wrappers but thats a different discussion] Satish This will be fixed with my next push. Also the