Specifying an alias in crossdev discards command line options. In the case of --show-target-cfg, crossdev attempts to create a build environment instead of dumping the target configuration: user $ crossdev --show-target-cfg cell * The 'cell' target is really an alias for the 'ppu' target(s) -------------------------------------------------------------------------- * crossdev version: 20230616 * Host Portage ARCH: amd64 * Host Portage System: x86_64-pc-linux-gnu (i686-pc-linux-gnu x86_64-pc- linux-gnu) * Target Portage ARCH: ppc64 * Target System: ppu * Stage: 4 (C/C++ compiler) * USE=multilib: no * Target ABIs: default * binutils: binutils-[latest] * gcc: gcc-[latest] * headers: linux-headers-[latest] * libc: [none]-[latest] * CROSSDEV_OVERLAY: /var/db/repos/testing * PORT_LOGDIR: /var/log/portage * PORTAGE_CONFIGROOT: / * Portage flags: _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ ^C Rough mockup of expected behavior: user $ crossdev --show-target-cfg cell * The 'cell' target is really an alias for the 'ppu' target(s) arch=ppc64 target=spu-elf category=cross-spu-elf binutils_category=sys-devel binutils_pn=binutils gcc_category=sys-devel gcc_pn=gcc kernel_category= kernel_pn= libc_category=sys-libs libc_pn=newlib crosspkgs='binutils gcc kernel libc'
