Pretty much what says in the summary, sorry I couldn't elaborate further. Reproducible: Always Steps to Reproduce: 1.Just the regular, sync, update and emerge. 2. 3. Actual Results: Just emerging. Expected Results: Failed compilation Should have successfully emerged and installed.
Tried to submit a build log but says file too big.
Anyway here;s where it fails: ninja: build stopped: subcommand failed. [31;01m*[0m ERROR: media-libs/mesa-20.3.0::gentoo failed (compile phase): [31;01m*[0m ninja -v -j4 -l0 -C /var/tmp/portage/media-libs/mesa-20.3.0/work/mesa-20.3.0-abi_x86_32.x86 failed [31;01m*[0m [31;01m*[0m Call stack: [31;01m*[0m ebuild.sh, line 125: Called src_compile [31;01m*[0m environment, line 4120: Called multilib-minimal_src_compile [31;01m*[0m environment, line 2781: Called multilib_foreach_abi 'multilib-minimal_abi_src_compile' [31;01m*[0m environment, line 3051: Called multibuild_foreach_variant '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_compile' [31;01m*[0m environment, line 2716: Called _multibuild_run '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_compile' [31;01m*[0m environment, line 2714: Called _multilib_multibuild_wrapper 'multilib-minimal_abi_src_compile' [31;01m*[0m environment, line 928: Called multilib-minimal_abi_src_compile [31;01m*[0m environment, line 2775: Called multilib_src_compile [31;01m*[0m environment, line 3263: Called meson_src_compile [31;01m*[0m environment, line 2603: Called eninja '-C' '/var/tmp/portage/media-libs/mesa-20.3.0/work/mesa-20.3.0-abi_x86_32.x86' [31;01m*[0m environment, line 1761: Called die [31;01m*[0m The specific snippet of code: [31;01m*[0m "$@" || die "${nonfatal_args[@]}" "${*} failed" [31;01m*[0m [31;01m*[0m If you need support, post the output of `emerge --info '=media-libs/mesa-20.3.0::gentoo'`, [31;01m*[0m the complete build log and the output of `emerge -pqv '=media-libs/mesa-20.3.0::gentoo'`. [31;01m*[0m The complete build log is located at '/var/tmp/portage/media-libs/mesa-20.3.0/temp/build.log'. [31;01m*[0m The ebuild environment file is located at '/var/tmp/portage/media-libs/mesa-20.3.0/temp/environment'. [31;01m*[0m Working directory: '/var/tmp/portage/media-libs/mesa-20.3.0/work/mesa-20.3.0-abi_x86_32.x86' [31;01m*[0m S: '/var/tmp/portage/media-libs/mesa-20.3.0/work/mesa-20.3.0'
(In reply to Pednick from comment #2) > Anyway here;s where it fails: > > ninja: build stopped: subcommand failed. > [31;01m*[0m ERROR: media-libs/mesa-20.3.0::gentoo failed (compile phase): > [31;01m*[0m ninja -v -j4 -l0 -C > /var/tmp/portage/media-libs/mesa-20.3.0/work/mesa-20.3.0-abi_x86_32.x86 > failed > [31;01m*[0m > [31;01m*[0m Call stack: > [31;01m*[0m ebuild.sh, line 125: Called src_compile > [31;01m*[0m environment, line 4120: Called multilib-minimal_src_compile > [31;01m*[0m environment, line 2781: Called multilib_foreach_abi > 'multilib-minimal_abi_src_compile' > [31;01m*[0m environment, line 3051: Called multibuild_foreach_variant > '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_compile' > [31;01m*[0m environment, line 2716: Called _multibuild_run > '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_compile' > [31;01m*[0m environment, line 2714: Called _multilib_multibuild_wrapper > 'multilib-minimal_abi_src_compile' > [31;01m*[0m environment, line 928: Called > multilib-minimal_abi_src_compile > [31;01m*[0m environment, line 2775: Called multilib_src_compile > [31;01m*[0m environment, line 3263: Called meson_src_compile > [31;01m*[0m environment, line 2603: Called eninja '-C' > '/var/tmp/portage/media-libs/mesa-20.3.0/work/mesa-20.3.0-abi_x86_32.x86' > [31;01m*[0m environment, line 1761: Called die > [31;01m*[0m The specific snippet of code: > [31;01m*[0m "$@" || die "${nonfatal_args[@]}" "${*} failed" > [31;01m*[0m > [31;01m*[0m If you need support, post the output of `emerge --info > '=media-libs/mesa-20.3.0::gentoo'`, > [31;01m*[0m the complete build log and the output of `emerge -pqv > '=media-libs/mesa-20.3.0::gentoo'`. > [31;01m*[0m The complete build log is located at > '/var/tmp/portage/media-libs/mesa-20.3.0/temp/build.log'. > [31;01m*[0m The ebuild environment file is located at > '/var/tmp/portage/media-libs/mesa-20.3.0/temp/environment'. > [31;01m*[0m Working directory: > '/var/tmp/portage/media-libs/mesa-20.3.0/work/mesa-20.3.0-abi_x86_32.x86' > [31;01m*[0m S: '/var/tmp/portage/media-libs/mesa-20.3.0/work/mesa-20.3.0' If this was the first time it has failed, try to update it again. ninja failed to update libdrm and mesa on my systems at first as well but succeeded the second time.
Nope not the first time but I just tried to emerge libdrm and mesa again. Libdrm succeeeded but mesa failed again.
Ok I figured out what was wrong, so I unmerged llvm and then emerge --update --newuse --deep --with-bdeps=y @world, forgot how long the llvm compile was or I would've replied sooner. Everything emerged and installed fine after that, the llvm must have gotton corrupted. Sorry for the confusion. Do I or the moderators change the status to resolved?
Thank you for reporting that all is fine. Happy compiling and all the best.
