[petsc-users] Build Error

Barry Smith bsmith at petsc.dev
Fri May 26 12:41:38 CDT 2023


  When PETSc is configured it creates a file configure.log in the PETSC_DIR directory; when make is run on it it creates a make.log file.

   The configure.log file is very useful for figuring anything that goes wrong.


> On May 26, 2023, at 1:32 PM, SENECA, MICHAEL <mseneca at anl.gov> wrote:
> 
> Where might I find the configure.log? Or do you mean the petsc build log information?
>  
>  
> From: Barry Smith <bsmith at petsc.dev <mailto:bsmith at petsc.dev>>
> Date: Friday, May 26, 2023 at 9:40 AM
> To: SENECA, MICHAEL <mseneca at anl.gov <mailto:mseneca at anl.gov>>
> Cc: petsc-users at mcs.anl.gov <mailto:petsc-users at mcs.anl.gov> <petsc-users at mcs.anl.gov <mailto:petsc-users at mcs.anl.gov>>
> Subject: Re: [petsc-users] Build Error
> 
>  
>   PETSc configure is suppose to handle this cleanly. Please send configure.log to petsc-maint at mcs.anl.gov <mailto:petsc-maint at mcs.anl.gov>  as we need more context to understand why it is not working.
>  
>   PETSc configure looks for libgtoolize (which is what brew names it) and uses it for  libtoolize
>  
>   You can use --with-libtoolize-exec=pathtolibtoolize  (or --with-libtoolize=pathtolibtoolize for older versions of PETSc) to select the executable PETSc uses
>  
>  
>  
> 
> 
> On May 25, 2023, at 1:35 PM, SENECA, MICHAEL via petsc-users <petsc-users at mcs.anl.gov <mailto:petsc-users at mcs.anl.gov>> wrote:
>  
> Hi all,
>  
> I have been attempting to install cardinal on my new MacBook M2 Pro chip but I have run into some errors when attempting to build petsc, the script attempts to access
> /usr/bin/libtoolize
> which does not exist on my MacBook. I have libtoolize installed via homebrew and have made a link from the homebrew installation to
> usr/local/bin/libtoolize
> But the script does not look in the local directory. From what I have gathered online, the /usr/bin/ should not be edited as it is managed by macOS and its system software which can lead to system instability. Do any of you know of a way around to get the petsc script to just look for libtoolize from my path and not /usr/bin/libtoolize?
>  
> Best regards,
> Michael Seneca

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20230526/6e8021b9/attachment.html>


More information about the petsc-users mailing list