https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: media-gfx/luminance-hdr-2.6.0 calls commands that do not exist. Discovered on: amd64 (internal ref: ci)
Created attachment 666227 [details] build.log build log and emerge --info
readelf is provided by GNU Binutils, which you have clearly installed. The only explanation that I can find is that binutils-config was never run, and thus some symlinks are missing.
(In reply to Andreas K. Hüttel from comment #2) > readelf is provided by GNU Binutils, which you have clearly installed. > > The only explanation that I can find is that binutils-config was never run, > and thus some symlinks are missing. this is because of binutils[-native-symlinks] luminance-hdr is calling it directly instead of use the prefixed version.
(In reply to Agostino Sarubbo from comment #3) > (In reply to Andreas K. Hüttel from comment #2) > > readelf is provided by GNU Binutils, which you have clearly installed. > > > > The only explanation that I can find is that binutils-config was never run, > > and thus some symlinks are missing. > > this is because of binutils[-native-symlinks] > luminance-hdr is calling it directly instead of use the prefixed version. According to your emerge --info, USE="acl amd64 berkdb bzip2 cli crypt dri elogind fortran gdbm iconv ipv6 jumbo-build libglvnd libtirpc multilib native-symlinks ncurses nls nptl openmp pam pcre readline seccomp split-usr ssl tcpd unicode xattr zlib" So this explanation is wrong.
Hi, I don't want to play this game to change the status of the bug. The emerge --info as you know contains the general USE. The tinderbox make a test by using a local flag(package.use), so you will always see native-symlinks in emerge --info because it is supposed to work in this way. If you want to reproduce and then fix the bug you have the reproducer.
