Well I used a fresh petsc clone and that worked. On Fri, May 29, 2015 at 1:05 PM, Mark Adams <[email protected]> wrote:
> Humm, I cleaned everything, and even cut and pasted your configure line, > same thing. I am now trying with a fresh petsc clone. > > I add these modules: > > module load adios/1.6.0 > module load cray-hdf5-parallel > module load cmake/2.8.11.2 > module unload darshan > > and I do not see this bfort-base.txt file: > > 10:03 edison03 master ~/petsc_install/petsc$ ll arch-xc30-opt64-intel/share > total 32 > -rw-r--r-- 1 madams madams 4755 May 29 09:52 basedefs.txt > -rw-r--r-- 1 madams madams 326 May 29 09:52 blueball.gif > drwxr-x--- 2 madams madams 512 May 29 09:52 doctext > -rw-r--r-- 1 madams madams 326 May 29 09:52 greenball.gif > -rw-r--r-- 1 madams madams 1625 May 29 09:52 html.def > -rw-r--r-- 1 madams madams 1668 May 29 09:52 latex.def > drwxr-x--- 3 madams madams 512 May 29 09:52 man > -rw-r--r-- 1 madams madams 79 May 29 09:52 next.gif > -rw-r--r-- 1 madams madams 287 May 29 09:52 next.xbm > -rw-r--r-- 1 madams madams 1482 May 29 09:52 nroff.def > -rw-r--r-- 1 madams madams 79 May 29 09:52 previous.gif > -rw-r--r-- 1 madams madams 299 May 29 09:52 previous.xbm > -rw-r--r-- 1 madams madams 7353 May 29 09:52 pstoppm.ps > -rw-r--r-- 1 madams madams 326 May 29 09:52 purpleball.gif > -rw-r--r-- 1 madams madams 326 May 29 09:52 redball.gif > -rw-r--r-- 1 madams madams 283 May 29 09:52 refman.def > -rw-r--r-- 1 madams madams 3151 May 29 09:52 refman.sty > -rw-r--r-- 1 madams madams 74 May 29 09:52 up.gif > -rw-r--r-- 1 madams madams 281 May 29 09:52 up.xbm > -rw-r--r-- 1 madams madams 324 May 29 09:52 yellowball.gif > > > > > On Fri, May 29, 2015 at 11:23 AM, Satish Balay <[email protected]> wrote: > >> I tried building on edison - and can't reproduce this problem. >> >> ./configure --COPTFLAGS="-fast -no-ipo" --CXXOPTFLAGS="-fast -no-ipo" >> --FOPTFLAGS="-fast -no-ipo" --with-ssl=0 --with-cc=cc >> --with-clib-autodetect=0 --with-cxx=CC --with-cxxlib-autodetect=0 >> --with-debugging=0 --with-fc=ftn --with-fortranlib-autodetect=0 >> --with-shared-libraries=0 --with-x=0 --with-mpiexec=aprun LIBS=-lstdc++ >> --with-64-bit-indices PETSC_DIR=$PWD PETSC_ARCH=arch-xc30-opt64-intel >> --prefix=$HOME/soft/test >> >> The error message you get is puzzling.. >> >> > Unable to find bfort-base.txt config file in >> /global/homes/m/madams/petsc_install/petsc/arch-xc30-opt64-intel/share******* >> >> Can you attempt a build from a 'clean' repo? >> >> rm -rf arch* >> git clean -f -d -x >> ./configure.... >> >> Satish >> >> >> On Fri, 29 May 2015, Mark Adams wrote: >> >> > Barry, It looks like you blew it. >> > >> > On Wed, May 27, 2015 at 4:03 PM, Barry Smith <[email protected]> >> wrote: >> > >> > > >> > > Apparently all people with access to the PETSc repository (i.e. >> > > everyone in the world with internet access) have caught a rare >> disease that >> > > has caused their fingers to fall off, making them incapable of fixing >> this. >> > > >> > > I have added all the PETSc enums to this file in master and next. >> Make >> > > sure you run make allfortranstubs to regenerate the stubs. >> > > >> > > Barry >> > > >> > > >> > > >> > > > On May 27, 2015, at 2:15 PM, Mark Adams <[email protected]> wrote: >> > > > >> > > > FYI, this does not seem to be fixed. >> > > > >> > > > On Sat, Apr 18, 2015 at 5:49 AM, Barry Smith <[email protected]> >> wrote: >> > > > >> > > > Looks like a bunch of these things are missing from >> > > lib/petsc/conf/bfort-petsc.txt it should be listed under native >> > > > >> > > > Barry >> > > > >> > > > >> > > > >> > > > > On Apr 17, 2015, at 4:43 PM, Matthew Knepley <[email protected]> >> > > wrote: >> > > > > >> > > > > Does bfort have to be told that PCCompositeType is an enum? >> > > > > >> > > > > Matt "bfort's biggest fan" >> > > > > >> > > > > On Fri, Apr 17, 2015 at 4:37 PM, Mark Adams <[email protected]> >> wrote: >> > > > > It looks like fieldsplitf.c has an extra PetscToPointer. type is >> > > already a pointer: >> > > > > >> > > > > PETSC_EXTERN void PETSC_STDCALL pcfieldsplitgettype_(PC >> > > pc,PCCompositeType *type, int *__ierr ){ >> > > > > *__ierr = PCFieldSplitGetType( >> > > > > (PC)PetscToPointer((pc) ), >> > > > > (PCCompositeType* )PetscToPointer((type) )); >> > > > > } >> > > > > >> > > > > On Fri, Apr 17, 2015 at 4:12 PM, Barry Smith <[email protected]> >> > > wrote: >> > > > > >> > > > > Likely need to run in the debugger to see what generates the >> error. >> > > Perhaps a missing ierr? >> > > > > >> > > > > Barry >> > > > > >> > > > > >> > > > > > On Apr 17, 2015, at 9:10 AM, Mark Adams <[email protected]> >> wrote: >> > > > > > >> > > > > > I declare >> > > > > > >> > > > > > PCCompositeType::pcctype >> > > > > > >> > > > > > But PCFieldSplitGetType does not seem to like it? >> > > > > > >> > > > > > Mark >> > > > > > >> > > > > > [1]PETSC ERROR: --------------------- Error Message >> > > -------------------------------------------------------------- >> > > > > > [1]PETSC ERROR: Invalid pointer >> > > > > > [1]PETSC ERROR: Invalid Pointer to Int: Parameter # 2 >> > > > > > [1]PETSC ERROR: See >> > > http://www.mcs.anl.gov/petsc/documentation/faq.html for trouble >> shooting. >> > > > > > [1]PETSC ERROR: Petsc Development GIT revision: >> > > v3.5.3-2702-g1f714da GIT Date: 2015-04-16 11:32:06 -0500 >> > > > > > [1]PETSC ERROR: ../../XGC1_3/xgc-em on a arch-macosx-gnu-g named >> > > MacBook-Pro.local by markadams Fri Apr 17 10:06:09 2015 >> > > > > > [1]PETSC ERROR: Configure options --download-hypre=1 >> > > --download-p4est --download-superlu=1 --download-mumps >> --download-scalapack >> > > --download-superlu_dist=1 --download-parmetis=1 --download-metis=1 >> > > --download-triangle=1 --with-hdf5-dir=/Users/markadams/Codes/hdf5 >> > > --with-x=0 --with-debugging=1 PETSC_ARCH=arch-macosx-gnu-g >> > > > > > [1]PETSC ERROR: #1 PCFieldSplitGetType() line 2046 in >> > > /Users/markadams/Codes/petsc/src/ksp/pc/impls/fieldsplit/fieldsplit.c >> > > > > > >> > > > > >> > > > > >> > > > > >> > > > > >> > > > > >> > > > > -- >> > > > > What most experimenters take for granted before they begin their >> > > experiments is infinitely more interesting than any results to which >> their >> > > experiments lead. >> > > > > -- Norbert Wiener >> > > > >> > > > >> > > >> > > >> > >> >> >
