On Friday, 5 April 2024 07:34:01 BST Paul Sopka wrote: > On 05.04.24 08:31, Paul Sopka wrote: > > On 05.04.24 00:55, Michael wrote: > >> Your toolchain is now correct. Can you show the output of: > >> > >> equery u media-libs/libjpeg-turbo > >> > >> and > >> > >> emerge --info media-libs/libjpeg-turbo > >> > >> However, it could be this is a bug, you can check here for reports: > >> > >> https://bugs.gentoo.org/buglist.cgi?quicksearch=media-libs%2Flibjpeg-turb > >> o > >> > >> > >> If this is the only package you're getting a problem with, you can run: > >> > >> emerge --resume --skipfirst > >> > >> to complete your migration to profile 23.0, then try again to emerge > >> libjpeg- > >> turbo on its own. > > Also one or two weeks ago I successfully emerged with emptytree after > migrating to profile 23.0.
OK, for some reason (packages which require 32bit binary compatibility, or you setting some specific USE flag for a package in portage) the media-libs/ libjpeg-turbo had been built also with abi_x86_32. Now it seems your USE flags and corresponding build time dependencies have changed. Can you get it to build with: ABI_X86="64 -32 -x32" emerge -1aDv media-libs/libjpeg-turbo Check what flags you have set for packages in your /etc/portage/package.use to make them consistent.
signature.asc
Description: This is a digitally signed message part.
