Default build behaviour

[Former user]

On CentOS 7 I did:

cd
git checkout https://bitbucket.org/hpgmg/hpgmg
git checkout https://bitbucket.org/petsc/petsc
cd petsc
./configure --prefix=/opt/petsc --with-debugging=0 --with-mpi-dir=/opt/openmpi-2.0.1 --with-cuda=1 --with-blas-lib=/usr/lib64/libblas.a --with-lapack-lib=/usr/lib64/liblapack.a
make
make install
cd ../hpgmg
./configure --fe --petsc-dir=/opt/petsc

If I build hpgmg with

make

I only get the binary hpgmg-fv, whereas

make -C build

results into the building of both binaries hpgmg-fv and hpgmg-fe. To my mind it would be more reasonable if a simple make builds both binaries, especially as I already demanded the finite elements binary at the configuration stage. This is merely a suggestion for a simple intuitive default build behaviour.

[Jed Brown]

make: top-level "make all" use configured build if possible [close issue #3]

Formerly, an existing configured build was being overwritten by rerunning a default configure.

Reported-by: https://bitbucket.org/cjklein/

→ <<cset f4875d6da35e>>

[Jed Brown]

Thanks for the report @cjklein.