The following change gets rid of the warning on my linux box.. diff --git a/makefile b/makefile index b16da461fb..38b92d50fd 100644 --- a/makefile +++ b/makefile @@ -241,7 +241,7 @@ distclean: chk_petscdir # reconfigure: - @${PYTHON} ${PETSC_ARCH}/lib/petsc/conf/reconfigure-${PETSC_ARCH}.py + @unset MAKEFLAGS && ${PYTHON} ${PETSC_ARCH}/lib/petsc/conf/reconfigure-${PETSC_ARCH}.py # install: @${PYTHON} ./config/install.py -destDir=${DESTDIR} Satish On Sun, 2 Dec 2018, Lisandro Dalcin wrote:
Maybe configure should not warn if environment variables are empty? Or at least special-case MAKEFLAGS such that `make reconfigure` does not print the confusing message? What do you think, Satish?
On Sat, 1 Dec 2018 at 22:23, Hapla Vaclav via petsc-dev < [email protected]> wrote:
... except that it somehow passes this MAKEFLAGS= to configure, resulting in the confusing message ...
1. 12. 2018 v 17:33, Stefano Zampini <[email protected]>:
Make reconfigure is equivalent to rerun the configure script
Il giorno Sab 1 Dic 2018, 18:09 Hapla Vaclav <[email protected]> ha scritto:
... but this is apparently not caused by your merge.
Is it just normal behavior of make reconfigure? I didn't know about this, I always call the reconfigure script directly.
Vaclav
1. 12. 2018 v 16:04, Hapla Vaclav <[email protected]>:
Thanks, you're right.
However,
$ make reconfigure
===============================================================================
Configuring PETSc to compile on your system
===============================================================================
===============================================================================
***** WARNING: MAKEFLAGS (set to ) found in
environment variables - ignoring
use ./configure MAKEFLAGS=$MAKEFLAGS if you
really want to use that value ****** ===============================================================================
although I have no such variable set in my shell.
Vaclav
1. 12. 2018 v 15:36, Stefano Zampini <[email protected]>:
I have added a new package that gets built after petsc. You have to
run
make reconfigure
Il giorno Sab 1 Dic 2018, 16:52 Hapla Vaclav <
[email protected]> ha scritto:
Hi Stefano
After pulling latest master, I get the following at the end of make output: make[1]: *** No rule to make target 'mfem-build', needed by 'all-gnumake-local'. Stop. make[1]: Leaving directory '/scratch/petsc-dev-1' Now to check if the libraries are working do: make PETSC_DIR=/scratch/petsc-dev-1 PETSC_ARCH=arch-linux-gcc check
Do you think you could remove that line for non-mfem builds? I think it looks like an error for a user.
Vaclav