When I run crossdev for mips32, I end up with the following problem while compiling µClibc: * Done with patching * Runtime Prefix: / * Devel Prefix: /usr * Kernel Prefix: /usr/mips32-uclibc-linux/usr/include * CBUILD: x86_64-pc-linux-gnu * CHOST: x86_64-pc-linux-gnu * CTARGET: mips32-linux-uclibc * CPU: MIPS_ISA_3 * ENDIAN: BIG * Checking existence of //etc/portage/savedconfig/cross-mips32-uclibc-linux/uclibc-0.9.33.2-r11 ... * found //etc/portage/savedconfig/cross-mips32-uclibc-linux/uclibc-0.9.33.2-r11 and the build fails... It does even if I export the correct value with UCLIBC_CPU This because there is a bad pattern inside most µClibc ebuilds: export CBUILD=${CBUILD:-${CHOST}} export CTARGET=${CTARGET:-${CHOST}} so CTARGET isn't mips32, and... check_cpu_opts() { case ${CTARGET} in # Need to handle $ABI here w/mips. mips[1234]*) export UCLIBC_CPU="MIPS_ISA_${CTARGET:4:1}";; sh[2345]*) export UCLIBC_CPU="SH${CTARGET:2:1}";; i[3456]86*) export UCLIBC_CPU="${CTARGET:1:1}86";; # XXX: Should figure out how to handle sparc. esac } use the first number in mips32 which is 3 and mips III is a 64-bits platform.
This bug will not get looked more quickly by changing the severity level.
(In reply to Anthony Basile from comment #1) > This bug will not get looked more quickly by changing the severity level. Ok sorry, but this issue is blocking as can't compile for my system and some proprietary binaries (which control closed source in-kernel drivers) are already linked at µClibc. So I need µClibc and I can't use musl.
the plan is to kill these options off entirely. the only thing they do is add compiler flags like -mips1.
(In reply to SpanKY from comment #3) > the plan is to kill these options off entirely. the only thing they do is > add compiler flags like -mips1. Ok but why you don't mark the bug as confirmed then?
(In reply to lcellier from comment #4) > (In reply to SpanKY from comment #3) > > the plan is to kill these options off entirely. the only thing they do is > > add compiler flags like -mips1. > > Ok but why you don't mark the bug as confirmed then? Because no one cares about CONFIRMED vs UNCONFIRMED. And stop adding useless keywords.
uclibc support in Gentoo has been removed.
