[petsc-users] Installation issue of 3.18.* and 3.19.0 on Apple systems

[Satish Balay]

Is it possible some unicode chars are in configure options?

Perhaps debug with:

diff --git a/config/configure.py b/config/configure.py
index e00a7a9617c..a95483b61a5 100755
--- a/config/configure.py
+++ b/config/configure.py
@@ -455,6 +455,7 @@ def petsc_configure(configure_options):
   tbo = None
   framework = None
   try:
+    print(sys.argv[1:])
     framework = config.framework.Framework(['--configModules=PETSc.Configure','--optionsModule=config.compilerOptions']+sys.argv[1:], loadArgDB = 0)
     framework.setup()
     framework.logPrintBox('Configuring PETSc to compile on your system')


[Note the error message is printed further below]

Satish

On Wed, 5 Apr 2023, Stefano Zampini wrote:

> It seems there's some typo/error in the configure command that is being
> executed. Can you post it here?
> 
> Il giorno mer 5 apr 2023 alle ore 23:18 Kaus, Boris <kaus at uni-mainz.de> ha
> scritto:
> 
> > Hi everyone,
> >
> > I’m trying to install precompiled binaries for PETSc 3.18.5 & 3.19.0 using
> > the BinaryBuilder cross-compilation:
> > https://github.com/JuliaPackaging/Yggdrasil/pull/6533, which mostly works
> > fine: https://buildkite.com/julialang/yggdrasil/builds/2093).
> >
> > Yet, on apple systems I receive a somewhat weird bug during the configure
> > step:
> >
> > [22:08:49]
> > *******************************************************************************
> > [22:08:49]     TypeError or ValueError possibly related to ERROR in
> > COMMAND LINE ARGUMENT while running ./configure
> > [22:08:49]
> > -------------------------------------------------------------------------------
> > [22:08:49] invalid literal for int() with base 10: ''
> > [22:08:49]
> > *******************************************************************************
> > [22:08:49]
> > [22:08:49]
> > [22:08:49] /workspace/srcdir/petsc-3.18.0/lib/petsc/conf/rules:860:
> > /workspace/srcdir/petsc-3.18.0//lib/petsc/conf/petscrules: No such file or
> > directory
> > [22:08:49] make[1]: *** No rule to make target
> > '/workspace/srcdir/petsc-3.18.0//lib/petsc/conf/petscrules'.  Stop.
> > [22:08:49] /workspace/srcdir/petsc-3.18.0/lib/petsc/conf/rules:860:
> > /workspace/srcdir/petsc-3.18.0//lib/petsc/conf/petscrules: No such file or
> > directory
> > [22:08:49] make[1]: *** No rule to make target
> > '/workspace/srcdir/petsc-3.18.0//lib/petsc/conf/petscrules'.  Stop.
> > [22:08:49] make: *** [GNUmakefile:17:
> > /workspace/srcdir/petsc-3.18.0//lib/petsc/conf/petscvariables] Error 2
> > [22:08:49] make: *** Waiting for unfinished jobs....
> > [22:08:49] make: *** [GNUmakefile:17: lib/petsc/conf/petscvariables] Error
> > 2
> >
> > The log file is rather brief:
> >
> > sandbox:${WORKSPACE}/srcdir/petsc-3.18.0 # more configure.log
> > Executing: uname -s
> > stdout: Darwin
> >
> > It works fine for PETSc 3.16.5/3.17.5, and this first occurs in 3.18.0.
> > Is there something that changed between 3.17 & 3.18 that could cause this?
> >
> > The build system seems to use python3.9 (3.4+ as required)
> >
> > Thanks!
> > Boris
> >
> >
> >
> >
> >
> 
>