[petsc-dev] Problem with latest "petsc-dev" change

Satish Balay balay at mcs.anl.gov
Wed Nov 3 18:07:03 CDT 2010


You have some contradictory statements here:

" Note that while I pulled BuildSystem,"

" although I'm skipping the steps"
"  hg pull -u"


How did you pull BuildSystem - if not with 'hg pull -u'? [same with petsc-dev]

[I'm assuming you've done 'hg clone' a few days ago - not today]

Just to be sure - do:

cd petsc-dev
hg pull; hg update
cd config/BuildSystem
hg pull; hg update
cd ../../
./configure ........

And if configure continues to fail - send us the configure.log at petsc-maint at mcs.anl.gov

Satish

On Wed, 3 Nov 2010, Carl Ponder wrote:

> *On 11/03/2010 05:43 PM, Satish Balay wrote:*
> 
> >     Perhaps you pulled petsc-dev - but not BuildSystem - so they are
> > out-of-sync?
> 
> 
> Satish -- here are the commands I used:
> 
>    hg clone http://petsc.cs.iit.edu/petsc/petsc-dev
>    cd petsc-dev/config
>    hg clone http://petsc.cs.iit.edu/petsc/BuildSystem
>    cd ..
>    export PETSC_ARCH=arch-linux-gnu-c-debug
>    export PETSC_DIR=$PWD
>    ./configure --with-cc=mpicc --with-fc=mpif90
>    --download-f-blas-lapack=1 --download-hdf5=1
>    --prefix=$PETSC_DIR/$PETSC_ARCH
>    make PETSC_DIR=$PWD PETSC_ARCH=arch-linux-gnu-c-debug all
> 
> Note that while I pulledBuildSystem, I haven't taken any special steps to
> install it, I just run the installation steps forpetsc-dev in the parent
> directory.
> This is what I get from reading
> 
>    http://www.mcs.anl.gov/petsc/petsc-as/developers/index.html#Obtaining
> 
> although I'm skipping the steps
> 
>    hg pull -u
>    ./$PETSC_ARCH/conf/reconfigure-$PETSC_ARCH.py
> 
> Are these necessary, given that I've pulled the updated trees and run the
> configure & make?
> Thanks,
> 
>                     Carl Ponder
> 
> 
> -----------------------------------------------------------------------------------
> This email message is for the sole use of the intended recipient(s) and may
> contain
> confidential information.  Any unauthorized review, use, disclosure or
> distribution
> is prohibited.  If you are not the intended recipient, please contact the
> sender by
> reply email and destroy all copies of the original message.
> -----------------------------------------------------------------------------------
> 




More information about the petsc-dev mailing list