... 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 <vaclav.hapla(a)erdw.ethz.ch>:
>
> 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 <stefano.zampini(a)gmail.com>:
>>
>> 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 <vaclav.hapla(a)erdw.ethz.ch> 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
>
