https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: dev-python/python-efl-1.24.0 fails to compile. Discovered on: amd64 (internal ref: tinderbox) NOTE: This machine uses a clang/LLVM toolchain. If you think that this issue is strictly related to clang/LLVM please block bug 408963. If you think that this issue is strictly related to the LLD linker, please block bug 731004. This machine uses also GLIBC-2.32. If you think that this issue is strictly related to GLIBC please block bug 736174.
Created attachment 661659 [details] build.log build log and emerge --info
Possible context of error(s): clang-10: error: unknown argument: '-fno-var-tracking-assignments'
I don't know, your CC line and unset lines are different from mine in your emerge --info. What's the correct way to set up these? Since I'm following https://wiki.gentoo.org/wiki/Clang and it works. There's a very specific patch already in tree about this, too: https://gitweb.gentoo.org/repo/gentoo.git/tree/dev-python/python-efl/files/python-efl-1.24-clang.patch so should the documentation be updated, or are your tinderbox settings wonky?
CC is x86_64-pc-linux-gnu-clang here Please try x86_64-pc-linux-gnu-clang -fno-var-tracking-assignments
(In reply to Agostino Sarubbo from comment #4) > CC is x86_64-pc-linux-gnu-clang here > Yes I can see that, but where did you get the idea to set it so? I can't find any documentation supporting you should do that.
(In reply to Joonas Niilola from comment #5) > (In reply to Agostino Sarubbo from comment #4) > > CC is x86_64-pc-linux-gnu-clang here > > > > Yes I can see that, but where did you get the idea to set it so? I can't > find any documentation supporting you should do that. I can see the same output while running "x86_64-pc-linux-gnu-clang -fno-var-tracking-assignments" or just "clang -fno-var-tracking-assignments" so I don't understand at all what are you meaning. Also, "diff -ru /usr/lib/llvm/10/bin/x86_64-pc-linux-gnu-clang /usr/lib/llvm/10/bin/clang" gives no output that means that is the same binary
I have modified settings as described in here, https://wiki.gentoo.org/wiki/Clang and it works for me. >: emerge -pv python-efl clang llvm These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] sys-devel/llvm-10.0.1:10::gentoo USE="libffi ncurses xml -debug -doc -exegesis -gold -libedit -test -xar -z3" ABI_X86="32 (64) (-x32)" LLVM_TARGETS="AMDGPU BPF (X86) -AArch64 -ARC -ARM -AVR -Hexagon -Lanai -MSP430 -Mips -NVPTX -PowerPC -RISCV -Sparc -SystemZ -WebAssembly -XCore" 0 KiB [ebuild R ] sys-devel/clang-10.0.1:10::gentoo USE="static-analyzer xml -debug -default-compiler-rt -default-libcxx -default-lld -doc -test" ABI_X86="32 (64) (-x32)" LLVM_TARGETS="AMDGPU BPF (X86) -AArch64 -ARC -ARM -AVR -Hexagon -Lanai -MSP430 -Mips -NVPTX -PowerPC -RISCV -Sparc -SystemZ -WebAssembly -XCore" PYTHON_SINGLE_TARGET="python3_7 -python3_6 -python3_8 -python3_9" 0 KiB [ebuild R ] dev-python/python-efl-1.24.0::gentoo USE="-doc* -test*" PYTHON_TARGETS="python3_6 >: cat /var/db/pkg/dev-python/python-efl-1.24.0/CC clang So you have some weird undocumented unsupported system configuration that doesn't work?
The point is about prefixed toolchain command line. I guess in case of cross compiling the clang patch is broken because expects only clang instead of prefixed clang. Regarding the unsupported undocumented thing I guess it is like to say gcc is supported while x86_64-pc-linux-gnu-gcc is not.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d7c2885608dafa2e5190d51513c867988b6a8c97 commit d7c2885608dafa2e5190d51513c867988b6a8c97 Author: Joonas Niilola <juippis@gentoo.org> AuthorDate: 2020-09-22 05:59:44 +0000 Commit: Joonas Niilola <juippis@gentoo.org> CommitDate: 2020-09-22 06:01:17 +0000 dev-python/python-efl: fix crosscompile with clang Closes: https://bugs.gentoo.org/743787 Signed-off-by: Joonas Niilola <juippis@gentoo.org> .../python-efl/files/python-efl-1.24-clang.patch | 29 ++++++---------------- 1 file changed, 8 insertions(+), 21 deletions(-)
Thanks for explaining, it makes sense now. I just wanted to know where the x86_64-pc-linux-gnu-clang came from. There's no reason to support hundred variations of "my-custom-cc-wrapper".
