Due to some strange errors with distcc I decided to remove & re-install my cross-compiling toolchains. i686-pc-linux-gnu (for laptop) compiled fine, and the distcc errors went away, but re-install of i486-pc-linux-gnu toolchain (for fileserver) failed on glibc-headers. Error logs are attached.
Created attachment 213343 [details] cross-i486-pc-linux-gnu-info.log
Created attachment 213345 [details] cross-i486-pc-linux-gnu-glibc-headers.log
Does it work with binutils-2.18-r3? You can set the versions of the relevant packages to use through *VER environment variables[1] as well as through the options to crossdev. Right now it appears to pick up the latest ~arch versions instead. [1] Which you can also set up in /etc/portage/crossdev/<tuple>/[BGKL]VER for convenience.
No. it fails with exactly the same error, even if I explicitly specify all the versions instead of using crossdev --stable
Well, this is strange... I tried to downgrade crossdev, but it fails in the same way with all crossdev versions currently in portage
Ok, now I finally figured out what you asked originally, sorry for being so slow :) : yes, temporarily downgrading the *system* binutils to 2.18-r3 allows i468-pc-linux-gnu toolchain to compile. Crossdev really seems to pick up wrong version of binutils
Downgrading crossdev won't help if it launches the emerge runs correctly. What's more, the problem has nothing to do with crossdev - it's the emerge that fails. So the real nature of this bug report is more along the lines of "i486-pc-linux-gnu-glibc-headers fails with sys-devel/binutils". Which version of binutils did it try? And did you switch to the *VER environment variables solution I suggested?
use glibc-2.9_p20081201-r3+
