Thank you Satish! > > I think I find the issue, the MKLROOT should be one of the subdirectory for > the previous address. > > Another question, do you know if PETSc can be configured with AMD AOCL > https://urldefense.us/v3/__https://www.amd.com/en/developer/aocl.html__;!!G_uCfscf7eWS!brsW3VFdIkOx2YYJn_E9B4AxRRg1Ccxzi3m0X4IhDVuWBH2Q7qwq6gDOaiNM8DClyEWiy_Me3_vHAIUpiOKKQik$ > > <https://urldefense.us/v3/__https://www.amd.com/en/developer/aocl.html__;!!G_uCfscf7eWS!bLykqpElcA3Fh7lwJb3zD6mSMQ3zMUcI_ktTXnK41krRlRU6bWUv5h4HEDG8Pa7SjaqgjaAmNGStHpZVQhV6n9ZF5uclZA6v5gI$> > as the BLAS and LAPACK.
You should be able to use the configure option --with-blaslapack-dir=directory_of_aocl Please let us know of any difficulties. Barry > > Thanks, > Yongzhong > > From: Satish Balay <balay....@fastmail.org <mailto:balay....@fastmail.org>> > Date: Tuesday, July 23, 2024 at 10:43 PM > To: Yongzhong Li <yongzhong...@mail.utoronto.ca > <mailto:yongzhong...@mail.utoronto.ca>> > Cc: petsc-users@mcs.anl.gov <mailto:petsc-users@mcs.anl.gov> > <petsc-users@mcs.anl.gov <mailto:petsc-users@mcs.anl.gov>>, > petsc-ma...@mcs.anl.gov <mailto:petsc-ma...@mcs.anl.gov> > <petsc-ma...@mcs.anl.gov <mailto:petsc-ma...@mcs.anl.gov>> > Subject: Re: [petsc-users] MKL installation can't be used to configure PETSc > > [????????? balay....@fastmail.org <mailto:balay....@fastmail.org> ????????? > https://urldefense.us/v3/__https://aka.ms/LearnAboutSenderIdentification?**K__;Pz8_Pz8_Pz8_Pz8_!!G_uCfscf7eWS!brsW3VFdIkOx2YYJn_E9B4AxRRg1Ccxzi3m0X4IhDVuWBH2Q7qwq6gDOaiNM8DClyEWiy_Me3_vHAIUpD0n3Xpw$ > ] > <https://urldefense.us/v3/__https://aka.ms/LearnAboutSenderIdentification?**L5d__;Pz8_Pz8_Pz8_Pz8_JQ!!G_uCfscf7eWS!bLykqpElcA3Fh7lwJb3zD6mSMQ3zMUcI_ktTXnK41krRlRU6bWUv5h4HEDG8Pa7SjaqgjaAmNGStHpZVQhV6n9ZF5uclmq4yA0Q$> > > Are you sure you are providing the correct path? > > >>>> > --with-blaslapack-dir=/tool/pandora64/.package/oneMKL-2021.3/mkl > > MKL Path not found.. skipping: > /tool/pandora64/.package/oneMKL-2021.3/mkl/lib/64 > MKL Path not found.. skipping: > /tool/pandora64/.package/oneMKL-2021.3/mkl/lib/ia64 > MKL Path not found.. skipping: > /tool/pandora64/.package/oneMKL-2021.3/mkl/lib/em64t > MKL Path not found.. skipping: > /tool/pandora64/.package/oneMKL-2021.3/mkl/lib/intel64 > MKL Path not found.. skipping: > /tool/pandora64/.package/oneMKL-2021.3/mkl/lib > MKL Path not found.. skipping: > /tool/pandora64/.package/oneMKL-2021.3/mkl/64 > MKL Path not found.. skipping: > /tool/pandora64/.package/oneMKL-2021.3/mkl/ia64 > MKL Path not found.. skipping: > /tool/pandora64/.package/oneMKL-2021.3/mkl/em64t > MKL Path not found.. skipping: > /tool/pandora64/.package/oneMKL-2021.3/mkl/intel64 > MKL Path not found.. skipping: > /tool/pandora64/.package/oneMKL-2021.3/mkl/lib/32 > MKL Path not found.. skipping: > /tool/pandora64/.package/oneMKL-2021.3/mkl/lib/ia32 > MKL Path not found.. skipping: > /tool/pandora64/.package/oneMKL-2021.3/mkl/32 > MKL Path not found.. skipping: > /tool/pandora64/.package/oneMKL-2021.3/mkl/ia32 > > <<< > > Normally you should see something like the following [wrt the dir you specify > to --with-blaslapack-dir] > > >>> > balay@cg:~$ env |grep MKL > MKLROOT=/nfs/gce/software/custom/linux-ubuntu22.04-x86_64/spack/opt/spack/linux-ubuntu22.04-x86_64/gcc-11.2.0/intel-oneapi-mkl-2022.0.2-lzrncoj/mkl/2022.0.2 > balay@cg:~$ find > /nfs/gce/software/custom/linux-ubuntu22.04-x86_64/spack/opt/spack/linux-ubuntu22.04-x86_64/gcc-11.2.0/intel-oneapi-mkl-2022.0.2-lzrncoj/mkl/2022.0.2 > -name libmkl_core.so > <https://urldefense.us/v3/__http://libmkl_core.so/__;!!G_uCfscf7eWS!brsW3VFdIkOx2YYJn_E9B4AxRRg1Ccxzi3m0X4IhDVuWBH2Q7qwq6gDOaiNM8DClyEWiy_Me3_vHAIUp9wt2bk0$ > > > /nfs/gce/software/custom/linux-ubuntu22.04-x86_64/spack/opt/spack/linux-ubuntu22.04-x86_64/gcc-11.2.0/intel-oneapi-mkl-2022.0.2-lzrncoj/mkl/2022.0.2/lib/ia32/libmkl_core.so > > <https://urldefense.us/v3/__http://libmkl_core.so/__;!!G_uCfscf7eWS!brsW3VFdIkOx2YYJn_E9B4AxRRg1Ccxzi3m0X4IhDVuWBH2Q7qwq6gDOaiNM8DClyEWiy_Me3_vHAIUp9wt2bk0$ > > > /nfs/gce/software/custom/linux-ubuntu22.04-x86_64/spack/opt/spack/linux-ubuntu22.04-x86_64/gcc-11.2.0/intel-oneapi-mkl-2022.0.2-lzrncoj/mkl/2022.0.2/lib/intel64/libmkl_core.so > > <https://urldefense.us/v3/__http://libmkl_core.so/__;!!G_uCfscf7eWS!brsW3VFdIkOx2YYJn_E9B4AxRRg1Ccxzi3m0X4IhDVuWBH2Q7qwq6gDOaiNM8DClyEWiy_Me3_vHAIUp9wt2bk0$ > > > > Satish > > On Wed, 24 Jul 2024, Yongzhong Li wrote: > > > Dear PETSc developers, > > > > Recently, when I configured the PETSc with blas/lapack provided by Intel > > MKL, I got the following error message, > > > > > > [ 1%] Performing configure step for 'external_petsc' > > ============================================================================================= > > Configuring PETSc to compile on your system > > ============================================================================================= > > ============================================================================================= > > ***** WARNING ***** > > Found environment variable: MAKEFLAGS=s. Ignoring it! Use "./configure > > MAKEFLAGS=$MAKEFLAGS" if you really want to use this value > > ============================================================================================= > > TESTING: checkLib from > > config.packages.BlasLapack(config/BuildSystem/config/packages/BlasLapack.py:114) > > ********************************************************************************************* > > UNABLE to CONFIGURE with GIVEN OPTIONS (see configure.log for > > details): > > --------------------------------------------------------------------------------------------- > > You set a value for --with-blaslapack-dir=<dir>, but > > /tool/pandora64/.package/oneMKL-2021.3/mkl cannot be used > > ********************************************************************************************* > > > > make[2]: *** [CMakeFiles/external_petsc.dir/build.make:92: > > external/builds/petsc-3.21.0/src/external_petsc-stamp/external_petsc-configure] > > Error 1 > > make[1]: *** [CMakeFiles/Makefile2:114: CMakeFiles/external_petsc.dir/all] > > Error 2 > > make: *** [Makefile:91: all] Error 2 > > > > However, I think I was using the correct MKL root address to configure > > PETSc. I have attached the configure.log file, could you help me look at > > where might be wrong? > > > > Thanks! > > Yongzhong > > ----------------------------------------------------------- > > Yongzhong Li > > PhD student | Electromagnetics Group > > Department of Electrical & Computer Engineering > > University of Toronto > > https://urldefense.us/v3/__https://can01.safelinks.protection.outlook.com/?url=https*3A*2F*2Furldefense.us*2Fv3*2F__http*3A*2F*2Fwww.modelics.org__*3B!!G_uCfscf7eWS!aa4LdUX0JV3i0ce3Jp20GLg521rd7L25vZSpFhCmlvTUN8EZFjfbk-IsfiTOD3IpCfXCB_zHA8nh1WMIkiHosbwZgv8PzmzPEec*24&data=05*7C02*7Cyongzhong.li*40mail.utoronto.ca*7Cac6df78a38534d3cced208dcab8a6ce0*7C78aac2262f034b4d9037b46d56c55210*7C0*7C0*7C638573858217585114*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C0*7C*7C*7C&sdata=c237HxX0WzOtO2poHtci4lSZaaG37UH81irVGlu*2FsUg*3D&reserved=0__;JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl!!G_uCfscf7eWS!brsW3VFdIkOx2YYJn_E9B4AxRRg1Ccxzi3m0X4IhDVuWBH2Q7qwq6gDOaiNM8DClyEWiy_Me3_vHAIUp4pSlR3Y$ > > > > <https://urldefense.us/v3/__http://www.modelics.org__;!!G_uCfscf7eWS!aa4LdUX0JV3i0ce3Jp20GLg521rd7L25vZSpFhCmlvTUN8EZFjfbk-IsfiTOD3IpCfXCB_zHA8nh1WMIkiHosbwZgv8PzmzPEec$> > > > > >