Re: [gentoo-portage-dev] Build path abi missing in qemu-user
On 18/12/19 17:36, Joakim Tjernlund wrote: > On Wed, 2019-12-18 at 11:22 -0500, Mike Gilbert wrote: >> CAUTION: This email originated from outside of the organization. Do not >> click links or open attachments unless you recognize the sender and know the >> content is safe. >> >> >> On Thu, Dec 12, 2019 at 10:18 AM Joakim Tjernlund >> wrote: >>> When build in a qemu-user chroot I get odd build paths: >>> /var/tmp/portage/dev-libs/libxml2-2.9.9-r1/work/libxml2-2.9.9-.ppc >>> >>> This path is missing the abi_ppc_32 like so: >>> >>> /var/tmp/portage/dev-libs/libxml2-2.9.9-r1/work/libxml2-2.9.9-abi_ppc_32.ppc >>> >>> I struggle to find out why this happens, any ideas? >> I would guess you are using a profile that doesn't define the ABI_PPC >> USE_EXPAND variable properly. >> > # portageq envvar USE_EXPAND > ABI_MIPS ABI_PPC ABI_S390 ABI_X86 ALSA_CARDS APACHE2_MODULES APACHE2_MPMS > CALLIGRA_FEATURES CAMERAS COLLECTD_PLUGINS CPU_FLAGS_X86 CROSSCOMPILE_OPTS > CURL_SSL DRACUT_MODULES > DVB_CARDS ELIBC ENLIGHTENMENT_MODULES FCDSL_CARDS FFTOOLS FOO2ZJS_DEVICES > FRITZCAPI_CARDS GPSD_PROTOCOLS GRUB_PLATFORMS INPUT_DEVICES KERNEL > LCD_DEVICES LIBREOFFICE_EXTENSIONS > LINGUAS LIRC_DEVICES MONKEYD_PLUGINS NETBEANS_MODULES NGINX_MODULES_HTTP > NGINX_MODULES_MAIL OFED_DRIVERS OFFICE_IMPLEMENTATION OPENMPI_FABRICS > OPENMPI_OFED_FEATURES OPENMPI_RM > PHP_TARGETS PYTHON_SINGLE_TARGET PYTHON_TARGETS QEMU_SOFTMMU_TARGETS > QEMU_USER_TARGETS ROS_MESSAGES RUBY_TARGETS SANE_BACKENDS USERLAND > UWSGI_PLUGINS VIDEO_CARDS > VOICEMAIL_STORAGE XFCE_PLUGINS XTABLES_ADDONS > cu3-jocke fs # portageq envvar ABI_PPC > 32 > cu3-jocke fs # eselect profile list > Available profile symlink targets: > [1] default/linux/powerpc/ppc32/13.0 > [2] default/linux/powerpc/ppc32/13.0/desktop > [3] default/linux/powerpc/ppc32/13.0/desktop/gnome > [4] default/linux/powerpc/ppc32/13.0/desktop/gnome/systemd > [5] default/linux/powerpc/ppc32/13.0/desktop/kde > [6] default/linux/powerpc/ppc32/13.0/desktop/kde/systemd > [7] default/linux/powerpc/ppc32/13.0/developer > [8] default/linux/powerpc/ppc64/13.0/32bit-userland > [9] default/linux/powerpc/ppc64/13.0/32bit-userland/desktop > [10] default/linux/powerpc/ppc64/13.0/32bit-userland/desktop/gnome > [11] default/linux/powerpc/ppc64/13.0/32bit-userland/desktop/gnome/systemd > [12] default/linux/powerpc/ppc64/13.0/32bit-userland/desktop/kde > [13] default/linux/powerpc/ppc64/13.0/32bit-userland/desktop/kde/systemd > [14] default/linux/powerpc/ppc64/13.0/32bit-userland/developer > [15] hardened/linux/powerpc/ppc32 > [16] hardened/linux/powerpc/ppc64/32bit-userland > [17] hardened/linux/musl/ppc > [18] default/linux/uclibc/ppc > [19] hardened/linux/uclibc/ppc > [20] tmv3-target-overlay:cusfpv3 * > > cusfpv3 inherits default/linux/powerpc/ppc32/13.0 > > Jocke > Haven't 13.0 profiles been deprecated? (and/or deleted by now ...) signature.asc Description: OpenPGP digital signature
Re: [gentoo-portage-dev] Build path abi missing in qemu-user
On Wed, 2019-12-18 at 11:22 -0500, Mike Gilbert wrote: > CAUTION: This email originated from outside of the organization. Do not click > links or open attachments unless you recognize the sender and know the > content is safe. > > > On Thu, Dec 12, 2019 at 10:18 AM Joakim Tjernlund > wrote: > > When build in a qemu-user chroot I get odd build paths: > > /var/tmp/portage/dev-libs/libxml2-2.9.9-r1/work/libxml2-2.9.9-.ppc > > > > This path is missing the abi_ppc_32 like so: > > > > /var/tmp/portage/dev-libs/libxml2-2.9.9-r1/work/libxml2-2.9.9-abi_ppc_32.ppc > > > > I struggle to find out why this happens, any ideas? > > I would guess you are using a profile that doesn't define the ABI_PPC > USE_EXPAND variable properly. > # portageq envvar USE_EXPAND ABI_MIPS ABI_PPC ABI_S390 ABI_X86 ALSA_CARDS APACHE2_MODULES APACHE2_MPMS CALLIGRA_FEATURES CAMERAS COLLECTD_PLUGINS CPU_FLAGS_X86 CROSSCOMPILE_OPTS CURL_SSL DRACUT_MODULES DVB_CARDS ELIBC ENLIGHTENMENT_MODULES FCDSL_CARDS FFTOOLS FOO2ZJS_DEVICES FRITZCAPI_CARDS GPSD_PROTOCOLS GRUB_PLATFORMS INPUT_DEVICES KERNEL LCD_DEVICES LIBREOFFICE_EXTENSIONS LINGUAS LIRC_DEVICES MONKEYD_PLUGINS NETBEANS_MODULES NGINX_MODULES_HTTP NGINX_MODULES_MAIL OFED_DRIVERS OFFICE_IMPLEMENTATION OPENMPI_FABRICS OPENMPI_OFED_FEATURES OPENMPI_RM PHP_TARGETS PYTHON_SINGLE_TARGET PYTHON_TARGETS QEMU_SOFTMMU_TARGETS QEMU_USER_TARGETS ROS_MESSAGES RUBY_TARGETS SANE_BACKENDS USERLAND UWSGI_PLUGINS VIDEO_CARDS VOICEMAIL_STORAGE XFCE_PLUGINS XTABLES_ADDONS cu3-jocke fs # portageq envvar ABI_PPC 32 cu3-jocke fs # eselect profile list Available profile symlink targets: [1] default/linux/powerpc/ppc32/13.0 [2] default/linux/powerpc/ppc32/13.0/desktop [3] default/linux/powerpc/ppc32/13.0/desktop/gnome [4] default/linux/powerpc/ppc32/13.0/desktop/gnome/systemd [5] default/linux/powerpc/ppc32/13.0/desktop/kde [6] default/linux/powerpc/ppc32/13.0/desktop/kde/systemd [7] default/linux/powerpc/ppc32/13.0/developer [8] default/linux/powerpc/ppc64/13.0/32bit-userland [9] default/linux/powerpc/ppc64/13.0/32bit-userland/desktop [10] default/linux/powerpc/ppc64/13.0/32bit-userland/desktop/gnome [11] default/linux/powerpc/ppc64/13.0/32bit-userland/desktop/gnome/systemd [12] default/linux/powerpc/ppc64/13.0/32bit-userland/desktop/kde [13] default/linux/powerpc/ppc64/13.0/32bit-userland/desktop/kde/systemd [14] default/linux/powerpc/ppc64/13.0/32bit-userland/developer [15] hardened/linux/powerpc/ppc32 [16] hardened/linux/powerpc/ppc64/32bit-userland [17] hardened/linux/musl/ppc [18] default/linux/uclibc/ppc [19] hardened/linux/uclibc/ppc [20] tmv3-target-overlay:cusfpv3 * cusfpv3 inherits default/linux/powerpc/ppc32/13.0 Jocke
Re: [gentoo-portage-dev] Build path abi missing in qemu-user
On Thu, Dec 12, 2019 at 10:18 AM Joakim Tjernlund wrote: > > When build in a qemu-user chroot I get odd build paths: > /var/tmp/portage/dev-libs/libxml2-2.9.9-r1/work/libxml2-2.9.9-.ppc > > This path is missing the abi_ppc_32 like so: > /var/tmp/portage/dev-libs/libxml2-2.9.9-r1/work/libxml2-2.9.9-abi_ppc_32.ppc > > I struggle to find out why this happens, any ideas? I would guess you are using a profile that doesn't define the ABI_PPC USE_EXPAND variable properly.