Bug 913040 – sys-cluster/openmpi-4.1.4-r1: unable to compile using clang profile with LTO (checking external symbol convention... configure: error: unknown naming convention: )

• Status: UNCONFIRMED
• Product: Gentoo Linux

[Description Arniii 2023-08-26 08:09:45 UTC]

Created attachment 868755 [details]
configuration log with the error

Firstly, was problem that gfortran don't understand -rtlib=compiler-rt . That's solved by sam_ . Thanks to you.

And then I got to another problem: it uses at configuring demangler. IDK why.
So, it tries to use llvm-nm at gfortran's lto files and it gets error.

[Comment 1 Arniii 2023-08-26 08:10:22 UTC]

Created attachment 868756 [details]
emerge --info openmpi

[Comment 2 Arniii 2023-08-26 08:11:14 UTC]

Created attachment 868757 [details]
emerge's build log

[Comment 3 Arniii 2023-08-26 08:12:06 UTC]

Created attachment 868758 [details]
my /etc/portage/make.conf . Add here that it's on clang profile.

[Comment 4 Sam James 2023-08-29 06:19:14 UTC]

configure:44496: checking to see if Fortran compilers need additional linker flags
configure:44617: result: none
configure:44672: checking  external symbol convention
configure:44729: x86_64-pc-linux-gnu-gfortran -O3 -pipe -march=skylake -mabm --param=l1-cache-line-size=64 --param=l1-cache-size=32 --param=l2-cache-size=6144 -g3 -ggdb -flto=4 -c conftest.f -Wl,-O1 -Wl,--as-needed -Wl,--as-needed  -lz
configure:44736: $? = 0
Could not determine Fortran naming convention. Output from llvm-nm:
0000000000000001 C __gnu_lto_slim
0000000000000000 W conftest.f.100c6f4c
configure:44775: result: 
configure:44793: error: unknown naming convention: 


Does it work without LTO?

[Comment 5 Arniii 2023-09-15 14:05:07 UTC]

(In reply to Sam James from comment #4)
> configure:44496: checking to see if Fortran compilers need additional linker
> flags
> configure:44617: result: none
> configure:44672: checking  external symbol convention
> configure:44729: x86_64-pc-linux-gnu-gfortran -O3 -pipe -march=skylake -mabm
> --param=l1-cache-line-size=64 --param=l1-cache-size=32
> --param=l2-cache-size=6144 -g3 -ggdb -flto=4 -c conftest.f -Wl,-O1
> -Wl,--as-needed -Wl,--as-needed  -lz
> configure:44736: $? = 0
> Could not determine Fortran naming convention. Output from llvm-nm:
> 0000000000000001 C __gnu_lto_slim
> 0000000000000000 W conftest.f.100c6f4c
> configure:44775: result: 
> configure:44793: error: unknown naming convention: 
> 
> 
> Does it work without LTO?

I've tried without LTO, yep, it steps through the point further. So yes, llvm-nm  cannot understand gfortran lto symbols.