petsc-3.0.0-p11 configure failure

[Alberto.Verga@…]

Installing PETSc fails on my MacPro 10.6.3 at the configuration step. I have installed the gcc43 and python26 ports and use the default architecture x86_64 for Snow Leopard.

$ sudo port install -d petsc
Password: xxxxxx
--->  Computing dependencies for petsc
--->  Configuring petsc
Error: Target org.macports.configure returned: configure failure: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_petsc/work/petsc-3.0.0-p11" && /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_petsc/work/petsc-3.0.0-p11/config/configure.py --prefix=/opt/local --with-python --with-debugging=0 --with-c-support=1 --with-c++-support=1 --with-pic=fPIC --prefix=/opt/local/lib/petsc --with-cc=/opt/local/bin/openmpicc --with-cxx=/opt/local/bin/openmpicxx --with-mpiexec=/opt/local/bin/openmpiexec " returned error 1
Command output: TESTING: checkDynamicLinker from config.setCompilers(/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_petsc/work/petsc-3.0.0-p11/config/BuildSystem/config/setCompilers.py:1195)
TESTING: output from config.setCompilers(/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_petsc/work/petsc-3.0.0-p11/config/BuildSystem/config/setCompilers.py:1241)
TESTING: configureCompilerFlags from config.compilerFlags(/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_petsc/work/petsc-3.0.0-p11/config/BuildSystem/config/compilerFlags.py:66)
TESTING: configureDebugging from PETSc.utilities.debugging(/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_petsc/work/petsc-3.0.0-p11/config/PETSc/utilities/debugging.py:25)
          =================================================================================
                        WARNING! Compiling PETSc with no debugging, this should 
                              only be done for timing and production runs. All development should 
                              be done when configured using --with-debugging=1
          =================================================================================
        
TESTING: configureArchitecture from PETSc.utilities.arch(/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_petsc/work/petsc-3.0.0-p11/config/PETSc/utilities/arch.py:39)
TESTING: configureSharedLibraries from PETSc.utilities.sharedLibraries(/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_petsc/work/petsc-3.0.0-p11/config/PETSc/utilities/sharedLibraries.py:41)
TESTING: configureDynamicLibraries from PETSc.utilities.sharedLibraries(/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_petsc/work/petsc-3.0.0-p11/config/PETSc/utilities/sharedLibraries.py:64)
TESTING: configureBmakeDir from PETSc.utilities.bmakeDir(/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_petsc/work/petsc-3.0.0-p11/config/PETSc/utilities/bmakeDir.py:26)
TESTING: checkRestrict from config.compilers(/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_petsc/work/petsc-3.0.0-p11/config/BuildSystem/config/compilers.py:134)
TESTING: checkCFormatting from config.compilers(/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_petsc/work/petsc-3.0.0-p11/config/BuildSystem/config/compilers.py:276)
TESTING: checkCStaticInline from config.compilers(/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_petsc/work/petsc-3.0.0-p11/config/BuildSystem/config/compilers.py:105)
TESTING: checkDynamicLoadFlag from config.compilers(/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_petsc/work/petsc-3.0.0-p11/config/BuildSystem/config/compilers.py:286)
TESTING: checkCLibraries from config.compilers(/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_petsc/work/petsc-3.0.0-p11/config/BuildSystem/config/compilers.py:161)
TESTING: checkRestrict from config.compilers(/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_petsc/work/petsc-3.0.0-p11/config/BuildSystem/config/compilers.py:134)
TESTING: checkCxxNamespace from config.compilers(/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_petsc/work/petsc-3.0.0-p11/config/BuildSystem/config/compilers.py:324)
TESTING: checkCxxOptionalExtensions from config.compilers(/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_petsc/work/petsc-3.0.0-p11/config/BuildSystem/config/compilers.py:299)
TESTING: checkCxxStaticInline from config.compilers(/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_petsc/work/petsc-3.0.0-p11/config/BuildSystem/config/compilers.py:119)
TESTING: checkCxxLibraries from config.compilers(/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_petsc/work/petsc-3.0.0-p11/config/BuildSystem/config/compilers.py:339)
*********************************************************************************
                    UNABLE to EXECUTE BINARIES for config/configure.py 
---------------------------------------------------------------------------------------
Cannot run executables created with FC. It is possible that you will need to configure using --with-batch which allows configuration without interactive sessions.
*********************************************************************************


Error: Status 1 encountered during processing.

Thanks, Alberto Verga

[mamoll (Mark Moll)]

petsc/work/petsc-3.0.0-p11/configure.log

[mamoll (Mark Moll)]

I have added the output of "sudo port -dv install petsc" as build.log. I have also added the configure.log file create by the petsc configure stage in petsc/work/petsc-3.0.0-p11/configure.log. Can you compare these to the output on your machine and tell me if there's any difference?

[Alberto.Verga@…]

Replying to mmoll@…:

I have added the output of "sudo port -dv install petsc" as build.log. I have also added the configure.log file create by the petsc configure stage in petsc/work/petsc-3.0.0-p11/configure.log. Can you compare these to the output on your machine and tell me if there's any difference?

Thank you for your help. Comparing the two configure.log files I detected that I had a broken /usr/bin/gfortran in my PATH; configure.py detected this executable and tried to use it. After removing usr/bin/gfortran I succeeded to build PETSc.

Thanks again,

Alberto Verga.