Hello April,
You’ll need PETSc 3.16.0 to use 
--download-mumps=https://bitbucket.org/petsc/pkg-mumps.git 
--download-mumps-commit=v5.4.1-p1
The MUMPS Makefile rule changed between 3.15.X (alllib) and 3.16.Y (all).

Thanks,
Pierre

> On 10 Nov 2021, at 8:00 PM, Novak, April via petsc-users 
> <petsc-users@mcs.anl.gov> wrote:
> 
> Hi Barry,
>  
> Thank you for your assistance - I’ve attached the latest configure.log. I 
> still encounter issues building, though some of the MUMPS errors do seem to 
> have been fixed with the --download-mumps-commit option. Do you have a 
> recommendation for addressing these other errors?
>  
> Thanks,
>  
> -April
>  
> From: Fande Kong <fdkong...@gmail.com>
> Date: Wednesday, November 10, 2021 at 9:44 AM
> To: Barry Smith <bsm...@petsc.dev>
> Cc: PETSc users list <petsc-users@mcs.anl.gov>, Novak, April <ano...@anl.gov>
> Subject: Re: [petsc-users] Error running make on MUMPS
> 
> Thanks, Barry,
> 
> We will try this, and report back
>  
>  
> Fande
>  
> On Tue, Nov 9, 2021 at 5:41 PM Barry Smith <bsm...@petsc.dev 
> <mailto:bsm...@petsc.dev>> wrote:
>  
>    This version of MUMPS has a bug in its build system; it does not have all 
> the dependencies on Fortran modules properly listed so Fortran files can get 
> compiled too early causing "random" failures during some builds, especially 
> on machines with lots of cores for compiling.
>  
>    I think you should be able to use 
> --download-mumps=https://bitbucket.org/petsc/pkg-mumps.git 
> <https://bitbucket.org/petsc/pkg-mumps.git> --download-mumps-commit=v5.4.1-p1 
> to get a patched version.
>  
> Barry
>  
> 
> 
> On Nov 9, 2021, at 6:10 PM, Fande Kong <fdkong...@gmail.com 
> <mailto:fdkong...@gmail.com>> wrote:
>  
> Hi All,
>  
> We encountered a configuration error when running the PETSc configuration on 
> a HPC system.  Went through the log file, but could not find much. The log 
> file was attached. 
>  
> Any thoughts?
>  
> Thanks for your help, as always.
>  
> Fande
>  
>  
>  
>  
>  
>  
> <configure.log>
>  
> <configure.log>

Reply via email to