Hi Jorge,

Okay this looks more like its failing now with something that may be due to 
your workarounds for linking:

10349 configure:20091: checking if C and C++ are link compatible
10350 configure:20114: icx -c -O3 -DNDEBUG  -finline-functions  conftest_c.c
10351 configure:20117: $? = 0
10352 configure:20145: icpx -o conftest -DNDEBUG    conftest.cpp conftest_c.o  
>&5
10353 /usr/x86_64-linux-gnu/bin/ld: cannot find -lstdc++: No such file or 
directory
10354 icpx: error: linker command failed with exit code 1 (use -v to see 
invocation)
10355 configure:20145: $? = 1
10356 configure: failed program was:

I'd suggest trying to build some simple non-MPI  c++  and c tests you build 
with icpx and icx respectively then try to link using icpx.
This sounds like a problem better directed toward one of the One API community 
lists.

Howard


On 6/15/26, 3:51 PM, "[email protected] 
<mailto:[email protected]> on behalf of [email protected] 
<mailto:[email protected]>" <[email protected] 
<mailto:[email protected]> on behalf of [email protected] 
<mailto:[email protected]>> wrote:


Hi Howard,


"'Pritchard Jr., Howard' via Open MPI users" 
<[email protected] <mailto:[email protected]>> escribió:


> Hi Jorge,
>
> Your config.log has these lines:
>
> configure:10133: checking whether the C compiler works
> configure:10155: icx -DNDEBUG '-O3' conftest.c >&5
> icx: error: no such file or directory: ''-O3''
> configure:10159: $? = 1
> configure:10199: result: no
> configure: failed program was:
>
> The problem seems to be that somehow the "-O3" you are using on the 
> command line gets mangled into '-O3' for the compiler. The compiler 
> doesn't understand that.
> Maybe try again without the CFLAGS, etc. being specified on the 
> configure line?
>
> Also make sure to use CXX=icpx
> Otherwise the configure will fail somewhere else.


Ok. Then, I temporarily try with a new configuration:


unset CC
unset CXX
unset FC
options="CC=icx CXX=icpx FC=ifx --prefix=${PREFIX} 
--with-prrte=internal --with-pmix=internal --with-ucx --without-verbs 
--without-libfabric --without-xpmem"


and I have attached the resulting config.log.gz file.


THANKS.


Regards
Jorge.




> On 6/15/26, 1:52 PM, "[email protected] 
> <mailto:[email protected]> 
> <mailto:[email protected] <mailto:[email protected]>> on behalf 
> of 
> [email protected] <mailto:[email protected]> 
> <mailto:[email protected] <mailto:[email protected]>>" 
> <[email protected] <mailto:[email protected]> 
> <mailto:[email protected] <mailto:[email protected]>> on 
> behalf of [email protected] <mailto:[email protected]> 
> <mailto:[email protected] <mailto:[email protected]>>> 
> wrote:
>
>
> Hi Howard,
>
>
> Thanks for replying. I am sorry, I did not have any luck with the suggestion.
> There are no significant changes. I have attached the new config.log.gz file.
> I suspect problems, perhaps, related to the symbolic link
> ln -s /usr/lib64/libgcc_s.so.1 
> /usr/x86_64-linux-gnu/lib/https://urldefense.com/v3/__http://libgcc_s.so__;!!Bt8fGhp8LhKGRg!BNmpId7wlYNL0cBzB6JFJoldka0u-PJ_-F6WoFuHDoHIUzLn-u6nJVNV1dRStKwE2uLT0Wp4XCiB8RoHLblR65I$
>  
> <https://urldefense.com/v3/__http://libgcc_s.so__;!!Bt8fGhp8LhKGRg!BNmpId7wlYNL0cBzB6JFJoldka0u-PJ_-F6WoFuHDoHIUzLn-u6nJVNV1dRStKwE2uLT0Wp4XCiB8RoHLblR65I$>
>  
> <https://urldefense.com/v3/__http://libgcc_s.so__;!!Bt8fGhp8LhKGRg!BNmpId7wlYNL0cBzB6JFJoldka0u-PJ_-F6WoFuHDoHIUzLn-u6nJVNV1dRStKwE2uLT0Wp4XCiB8RoHLblR65I$
>  
> <https://urldefense.com/v3/__http://libgcc_s.so__;!!Bt8fGhp8LhKGRg!BNmpId7wlYNL0cBzB6JFJoldka0u-PJ_-F6WoFuHDoHIUzLn-u6nJVNV1dRStKwE2uLT0Wp4XCiB8RoHLblR65I$>>
>  
> .
> So, please, do you have any other suggestions?
>
>
> Regards,
> Jorge.
>
>
> "'Pritchard Jr., Howard' via Open MPI users"
> <[email protected] <mailto:[email protected]> 
> <mailto:[email protected] <mailto:[email protected]>>> escribió:
>
>
>> Hi,
>>
>> Could you try modifying your configure command to be something like this?
>>
>> ./configure CC=icx CXX=icpx FC=ifx CFLAGS="-O3" CXXFLAGS="-O3" FCFLAGS="-O3"
>>
>> This works for me. I am using a somewhat older one api compiler
>> suite however:
>>
>> icx --version
>> Intel(R) oneAPI DPC++/C++ Compiler 2023.2.0 (2023.2.0.20230622)
>>
>> Howard
>>
>> From: <[email protected] <mailto:[email protected]> 
>> <mailto:[email protected] <mailto:[email protected]>>> 
>> on behalf of
>> "[email protected] <mailto:[email protected]> 
>> <mailto:[email protected] <mailto:[email protected]>>" 
>> <[email protected] <mailto:[email protected]> 
>> <mailto:[email protected] <mailto:[email protected]>>>
>> Reply-To: "[email protected] <mailto:[email protected]> 
>> <mailto:[email protected] <mailto:[email protected]>>" 
>> <[email protected] <mailto:[email protected]> 
>> <mailto:[email protected] <mailto:[email protected]>>>
>> Date: Monday, June 15, 2026 at 7:40 AM
>> To: Open MPI Users <[email protected] 
>> <mailto:[email protected]> 
>> <mailto:[email protected] <mailto:[email protected]>>>
>> Subject: [EXTERNAL] [OMPI users] configure failed of openmpi-5.0.10
>> with the 2026.0.0 icx and ifx compilers in Fedora 44
>>
>>
>> Der all,
>>
>> I cannot configure openmpi-5.010 with the 2026.0.0 icx+ifx compilers in
>> Fedora Linux 44 (Workstation Edition) system (altough an alternative
>> version with gcc+gfortran is ok).
>>
>> It is worth noting that during the installation of the icx/ifx
>> compilers, I had to add the line:
>> ln -s /usr/lib64/libgcc_s.so.1 
>> /usr/x86_64-linux-gnu/lib/https://urldefense.com/v3/__http://libgcc_s.so__;!!Bt8fGhp8LhKGRg!BNmpId7wlYNL0cBzB6JFJoldka0u-PJ_-F6WoFuHDoHIUzLn-u6nJVNV1dRStKwE2uLT0Wp4XCiB8RoHLblR65I$
>>  
>> <https://urldefense.com/v3/__http://libgcc_s.so__;!!Bt8fGhp8LhKGRg!BNmpId7wlYNL0cBzB6JFJoldka0u-PJ_-F6WoFuHDoHIUzLn-u6nJVNV1dRStKwE2uLT0Wp4XCiB8RoHLblR65I$>
>>  
>> <https://urldefense.com/v3/__http://libgcc_s.so__;!!Bt8fGhp8LhKGRg!BNmpId7wlYNL0cBzB6JFJoldka0u-PJ_-F6WoFuHDoHIUzLn-u6nJVNV1dRStKwE2uLT0Wp4XCiB8RoHLblR65I$
>>  
>> <https://urldefense.com/v3/__http://libgcc_s.so__;!!Bt8fGhp8LhKGRg!BNmpId7wlYNL0cBzB6JFJoldka0u-PJ_-F6WoFuHDoHIUzLn-u6nJVNV1dRStKwE2uLT0Wp4XCiB8RoHLblR65I$>>
>>  
>> .
>>
>> Please, any suggestions on how to resolve the issues listed in the
>> attached file?
>> Thank you in advance.
>>
>> Regards.
>> Jorge D'Elia.
>>
>> To unsubscribe from this group and stop receiving emails from it,
>> send an email to
>> [email protected] 
>> <mailto:[email protected]> 
>> <mailto:[email protected] 
>> <mailto:[email protected]>><mailto:[email protected]
>>  <mailto:[email protected]> 
>> <mailto:[email protected] 
>> <mailto:[email protected]>>>.
>>
>> To unsubscribe from this group and stop receiving emails from it,
>> send an email to [email protected] 
>> <mailto:[email protected]> 
>> <mailto:[email protected] 
>> <mailto:[email protected]>>.
>
>
>
>
> To unsubscribe from this group and stop receiving emails from it, 
> send an email to [email protected] 
> <mailto:[email protected]> 
> <mailto:[email protected] 
> <mailto:[email protected]>>.
>
>
>
> To unsubscribe from this group and stop receiving emails from it, 
> send an email to [email protected] 
> <mailto:[email protected]>.




To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected] 
<mailto:[email protected]>.



To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].

Reply via email to