Using recent Catalyst with uclibc

Since Koon stopped maintaining GNAP I've been building updated tarballs for personal use a couple of times each year.

One thing that has continously bugged me is that everything works out alright with Catalyst 2.0.1 and manual chroots but using later versions (at least 2.0.3_pre3 and 2.0.6) it fails to properly detect compiler settings. Ie. building busybox bails out with:


/var/tmp/portage/sys-apps/busybox-1.14.2/work/busybox-1.14.2/scripts/gcc-version.sh: line 11: i386-pc-linux-gnu-gcc: command not found


Obviously it should look after i386-gentoo-linux-uclibc-gcc but somehow the build scripts messes up the settings.

Enabling ccache just causes things to break sooner, ncurses then bails out with:

checking for i386-pc-linux-gnu-gcc... i386-pc-linux-gnu-gcc
checking for C compiler default output... configure: error: C compiler cannot create executables


Without Catalyst it seems like the problem is a broken binutils installation, but both with Catalyst 2.0.1 and with a manual chroot everything is working fine. This only happens when I update Catalyst, so it seems like either recent Catalyst is broken or more likely somehow my stage3 tarball is broken:/