> the configure.log sent didn't list the build command used for eigen. Yeah it never got there. The log is the “complete” log from configure. After a while I always just ctrl-c the configure. I will try building from conf.eigen and see if it goes through.
Best regards, Jacob Faibussowitsch (Jacob Fai - booss - oh - vitch) Cell: (312) 694-3391 > On Mar 24, 2020, at 1:27 PM, Satish Balay <[email protected]> wrote: > > the configure.log sent didn't list the build command used for eigen. > >>>> > Have to rebuild EIGEN, > /Users/jacobfaibussowitsch/NoSync/petsc/64-arch-darwin-c-debug/externalpackages/git.eigen/eigen.petscconf > != > /Users/jacobfaibussowitsch/NoSync/petsc/64-arch-darwin-c-debug/lib/petsc/conf/pkg.conf.eigen > <<<< > > You can check the contents of > /Users/jacobfaibussowitsch/NoSync/petsc/64-arch-darwin-c-debug/lib/petsc/conf/pkg.conf.eigen > - use it to manually build eigen and see if the problem persists. > > In my build - I see: [invoked from > /Users/balay/petsc/64-arch-darwin-c-debug/externalpackages/git.eigen/petsc-build] > > Executing: /usr/local/bin/cmake .. > -DCMAKE_INSTALL_PREFIX=/Users/balay/petsc/64-arch-darwin-c-debug > -DCMAKE_VERBOSE_MAKEFILE=1 > -DCMAKE_C_COMPILER="/Users/balay/petsc/64-arch-darwin-c-debug/bin/mpicc" > -DCMAKE_AR=/usr/bin/ar -DCMAKE_RANLIB=/usr/bin/ranlib > -DCMAKE_C_FLAGS:STRING="-fstack-protector -fno-stack-check -Qunused-arguments > -g3" -DCMAKE_C_FLAGS_DEBUG:STRING="-fstack-protector -fno-stack-check > -Qunused-arguments -g3" -DCMAKE_C_FLAGS_RELEASE:STRING="-fstack-protector > -fno-stack-check -Qunused-arguments -g3" > -DCMAKE_CXX_COMPILER="/Users/balay/petsc/64-arch-darwin-c-debug/bin/mpicxx" > -DCMAKE_CXX_FLAGS:STRING="-fstack-protector -fno-stack-check -g" > -DCMAKE_CXX_FLAGS_DEBUG:STRING="-fstack-protector -fno-stack-check -g" > -DCMAKE_CXX_FLAGS_RELEASE:STRING="-fstack-protector -fno-stack-check -g" > -DCMAKE_Fortran_COMPILER="/Users/balay/petsc/64-arch-darwin-c-debug/bin/mpif90" > -DCMAKE_Fortran_FLAGS:STRING="-ffree-line-length-0 -g" > -DCMAKE_Fortran_FLAGS_DEBUG:STRING="-ffree-line-lengt > h-0 -g" -DCMAKE_Fortran_FLAGS_RELEASE:STRING="-ffree-line-length-0 -g" > -DBUILD_SHARED_LIBS=on -DENABLE_OPENMP=OFF > > Satish > > On Tue, 24 Mar 2020, Pierre Jolivet wrote: > >> FWIW, I’ve had the same issue as Jacob for quite a while and I’ve since been >> using brew install eigen to bypass this. >> I’ve just checked again, and look at one of the process spawned during >> ./configure. That doesn’t look alright to me. >> >> Thanks, >> Pierre >> >> >> >>> On 24 Mar 2020, at 6:40 PM, Satish Balay via petsc-dev >>> <[email protected]> wrote: >>> >>> I just attempted a build on osx - and didn't see any such hang. I'm not >>> sure why your build is hanging.. >>> >>> balay@kpro petsc % ./configure --download-eigen --download-pragmatic >>> --download-metis --download-mpich >>> >>> Satish >>> >>> On Tue, 24 Mar 2020, Jacob Faibussowitsch wrote: >>> >>>> Hello all, >>>> >>>> Trying to install pragmatic using petsc, which requires Eigen package. I >>>> am installing these packages using arch/lib/petsc/conf/reconfigure >>>> —download-eigen —download-pragmatic. This is as far as it gets: >>>> >>>> /reconfigure-64-arch-darwin-c-debug.py --download-eigen >>>> =============================================================================== >>>> Configuring PETSc to compile on your system >>>> =============================================================================== >>>> =============================================================================== >>>> Trying to download git://https://gitlab.com/libeigen/eigen for EIGEN >>>> >>>> =============================================================================== >>>> =============================================================================== >>>> Configuring EIGEN with cmake, this may take several minutes >>>> >>>> =============================================================================== >>>> >>>> I have let this run for ~30 minute periods 3 times and it never >>>> progresses. I think that it does finish configure, but never progresses to >>>> the make stage. >>>> >>>> I have checked htop (brew version of top) and the only relevant processes >>>> running are bash with ~5% CPU. This is less robust but on my setup the >>>> window bar (where the close, minimize, etc buttons are) of the terminal >>>> window also reports the currently running process and this also only shows >>>> bash. For reference when configure is running normally, the top bar >>>> switches between clang, ld, expr, cmake, g++, etc. System resources used >>>> usually shoots up to ~40-90% as it gets into the different configures and >>>> makes for each package. >>>> >>>> I have tried this on 2 different petsc configurations; >>>> --with-64-bit-indices=0/1, since this originally didn’t work with 64 bit >>>> indices so I figured that may be the issue. I have also cleared my ccache >>>> completely using ccache -c -C and rerun both configures. >>>> >>>> I have attached both configure.logs, note configure.log —> >>>> —with-64-bit-indices=1, configure.log.bkp —> —with-64-bit-indices=0 >>>> >>>> >>>> Best regards, >>>> >>>> Jacob Faibussowitsch >>>> (Jacob Fai - booss - oh - vitch) >>>> Cell: (312) 694-3391 >>>> >> >>
