- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Describe the bug
configure stops with error. It is invoked with
./configure CC="mpiicc -cc=icx" CXX="mpiicpc -cxx=icpx" F90="mpiifort -fc=ifx" FC="mpiifort -fc=ifx" F77="mpiifort -fc=ifx" --enable-shared --enable-parallel --enable-fortran --with-zlib=yes --with-szlib=no
Expected behavior
Installation with Intel oneAPI LLVM compilers should be possible
Platform (please complete the following information)
- HDF5 1.12.2
- Arch Linux (Kernel 6.0.2-arch1-1)
- Intel oneAPI 2022.3.0.8767 (BaseKit + HPCKit)
- Gnu Make 4.3
Additional context
It seems that configure finds the classic intel compilers
- compiler 'mpiicc -cc=icx' is Intel icc-2022.2.0
- compiler 'mpiifort -fc=ifx' is Intel ifort-2022.2.0
- compiler 'mpiicpc -cxx=icpx' is Intel icpc-2022.2.0
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Thanks for posting in the Intel forums.
Could you please let us know if you are facing any errors while configuring HDF5 using the Intel oneAPI compilers(icx,icpx,ifx)?
Thanks & Regards,
Santosh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
./configure CC="mpiicc -cc=icc" CXX="mpiicpc -cxx=icpc" F90="mpiifort -fc=ifort" FC="mpiifort -fc=ifort" F77="mpiifort -fc=ifort" --enable-shared --enable-parallel --enable-fortran --with-zlib=yes --with-szlib=no
works. I think the issue is that the build system cannot discriminate the compilers and uses options or expects behavior that work for the traditional compilers but not for the new ones.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Could you please confirm if you are facing a similar error as shown below? If not, please provide us a screenshot of the error you are facing.
Thanks & regards,
Santosh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I can confirm that. I think the interesting information is in the this statement from config.log:
/usr/bin/ld: cannot find -loopopt=1: No such file or director
to me it seems that there is a dash missing and it is interpreted as a single character statement -l='oopopt=1'
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
We Assume that your issue is resolved. So could you please confirm to close this issue?
Thanks & Regards,
Santosh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I assume that your issue is resolved. If you need any additional information, please post a new question as this thread will no longer be monitored by Intel.
Thanks & Regards,
Santosh
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page