https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: games-strategy/s25rttr-0.9.0_pre20200723-r100 fails to compile. Discovered on: amd64 (internal ref: ci) NOTE: This machine uses GCC-11: https://gcc.gnu.org/gcc-11/porting_to.html If you think this is a GCC-11 related issue, please block bug 732706.
Created attachment 707208 [details] build.log build log and emerge --info
Created attachment 707211 [details] 1-CMakeOutput.log 1-CMakeOutput.log
Hmm. Why is this happening? I see: > * Working in BUILD_DIR: "/var/tmp/portage/games-strategy/s25rttr-0.9.0_pre20200723-r100/work/s25rttr-0.9.0_pre20200723_build" >cmake -C /var/tmp/portage/games-strategy/s25rttr-0.9.0_pre20200723-r100/work/s25rttr-0.9.0_pre20200723_build/gentoo_common_config.cmake -G Ninja -DCMAKE_INSTALL_PREFIX=/usr -DBUILD_TESTING=no -DCCACHE_PROGRAM=OFF -DCMAKE_SKIP_RPATH=ON ->DRTTR_BUILD_UPDATER=OFF -DRTTR_ENABLE_OPTIMIZATIONS=OFF -DRTTR_ENABLE_SANITIZERS=no -DRTTR_INCLUDE_DEVTOOLS=OFF -DRTTR_LIBDIR=lib64/s25rttr -DRTTR_REVISION=f0b97b120140c96bbeacae9c22633f899931db69 -DRTTR_USE_SYSTEM_LIBSAMPLERATE=ON ->DRTTR_VERSION=20200723 -DLUA_VERSION=5.1.5 -DCMAKE_BUILD_TYPE= -DCMAKE_TOOLCHAIN_FILE=/var/tmp/portage/games-strategy/s25rttr-0.9.0_pre20200723-r100/work/s25rttr-0.9.0_pre20200723_build/gentoo_toolchain.cmake /var/tmp/portage/games->strategy/s25rttr-0.9.0_pre20200723-r100/work/s25client-f0b97b120140c96bbeacae9c22633f899931db69 >loading initial cache file /var/tmp/portage/games-strategy/s25rttr-0.9.0_pre20200723-r100/work/s25rttr-0.9.0_pre20200723_build/gentoo_common_config.cmake Note that -DRTTR_REVISION=... is set, while for yours, it's "-DRTTR_REVISION= -D...". It's set to ${COMMIT} in the ebuild, so I don't see how it becomes blank?
I'll CC dev-portage but I'm probably missing something very obvious.
@ago could you provide environment file? Had a look but can't reproduce nor see how this could happen. Suspected eclasses might change $COMMIT somehow but I couldn't find anything so far.
(In reply to Ionen Wolkens from comment #5) > @ago could you provide environment file? > > Had a look but can't reproduce nor see how this could happen. > > Suspected eclasses might change $COMMIT somehow but I couldn't find anything > so far. My guess is possibly some Bash hook.
Actually there's a new release out and I was part way through bumping it but had a little trouble and got sidetracked.
*** Bug 808987 has been marked as a duplicate of this bug. ***