Probably  not an issue at all but why does 
--with-blaslapack-dir=/home/bchapman/aocl/5.1.0/gcc end with gcc? 

> On Nov 26, 2025, at 2:46 PM, Benjamin Chapman via petsc-users 
> <[email protected]> wrote:
> 
> Hello,
>  
> I am currently trying to build PETSc using the AOCC compiler and using AOCL 
> libraries for BLAS/LAPACK. However, I am running into an issue when it tries 
> to download and construct the MPI library, it cannot find the 
> “.libs/libevent.so 
> <https://urldefense.us/v3/__http://libevent.so/__;!!G_uCfscf7eWS!eCTV7HOPIUn75CuafYQXAhs0576zXZiNO4f6GWn6VG2JrDwpWQTFEKHycgGPN8fq2EnAx1V9u3LBZq85HrRzfZ4$
>  >” library in libevent (which it downloads). I attached the configure.log 
> file.
>  
> The reason I’m so confused is because PETSc built successfully when I did 
> AOCC + MKL and gcc + AOCL, but not AOCC + AOCL together.
>  
> Is it even possible to build PETSc using AOCC + AOCL or is it not designed 
> for that? If so, is there a specific procedure I should follow?

   There is no specific reason with PETSc that this should not work. The 
failure takes place in building OpenMPI which should have nothing to do with 
aocl.  What you set for --with-blaslapack-dir should have no effect on the 
building of OpenMPI. OpenMPI builds libevent as part of its build process and 
then uses it. I cannot see a failure in building libevent just that it cannot 
find it later while working on other parts of OpenMPI.

   Can you delete your PETSC_ARCH directory  completely and rerun the 
./configure 

   Don't use --with-fortran-kernels=1  it is pretty worthless. Don't use 
--with-threadsafety unless you know specifically that you need it. 

   If the rerun of ./configure fails you can try a trick. Run without the 
--with-blaslapack-dir (and let it use the default it finds) then immediately 
run ./configure again this time with the --with-blaslapack-dir  option (it will 
reuse the OpenMPI that it has already just built and won't rebuild it).


>  
> Thanks in advance.
>  
> Best,
> Ben
> <configure_AOCC_AOCL_add.log>

Reply via email to