https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: media-libs/embree-3.13.2 fails to compile. Discovered on: amd64 (internal ref: ci) NOTE: If you think this is a GCC-11 related issue, please block bug 732706.
Created attachment 755758 [details] build.log build log and emerge --info
ci has reproduced this issue with version 3.13.3 - Updating summary.
This is the offending cmake lines: --- execute_process(COMMAND objdump -C -t ${file} OUTPUT_VARIABLE output) string(REPLACE "\n" ";" output ${output}) --- I don't have any issues building this on my machine. So I have no clue why this would fail on your automated test system. Do you have any ideas?
ci has reproduced this issue with version 3.13.4 - Updating summary.
(In reply to Sebastian Parborg from comment #3) > This is the offending cmake lines: > --- > execute_process(COMMAND objdump -C -t ${file} OUTPUT_VARIABLE output) > string(REPLACE "\n" ";" output ${output}) > --- > > I don't have any issues building this on my machine. So I have no clue why > this would fail on your automated test system. > > Do you have any ideas? binutils-config[-native-symlinks], I'm guessing.
That does seem likely. Should I add that as a required use flag? Or is there an easy way in cmake to query for the path to the active binutils `objdump`?
I'm also hitting this issue with llvm-objdump. This may be unrelated though. Manually running "objdump -C -t /var/tmp/portage/media-libs/embree-3.13.5/work/embree-3.13.5_build/libembree_avx512.a" produces no output.
Oddly, I can't reproduce this when building outside of portage.
Okay, it seems like by default embree builds with -g in CXXFLAGS. For some reason, this isn't the case when building with portage. The cmake step it fails on requires the static archive it runs on to have debug info for objdump to produce any output.
(In reply to Violet Purcell from comment #9) > Okay, it seems like by default embree builds with -g in CXXFLAGS. For some > reason, this isn't the case when building with portage. The cmake step it > fails on requires the static archive it runs on to have debug info for > objdump to produce any output. Nevermind, that's not it.
I'll open a new bug for the issue with LLVM binutils, since it seems to be unrelated to the original build failure.
ci has reproduced this issue with version 4.3.0 - Updating summary.