I'm trying to setup distcc for a raspberry pi, and I'm having a hell of a time getting crossdev to work. Each package seems to fail in the unpacking phase, not being able to find a file or directory of some sort. I can kind of fix it by hand, but then the next package fails in the same manner. Also, not sure if it has anything to do with it, but the failure is always preceded by a "vecho command not found" error. (I was under the impression vecho had been stripped out of ebuilds quite some time ago) Reproducible: Always
Created attachment 364462 [details] Build log
Created attachment 364464 [details] emerge info
Created attachment 364466 [details] environment
After manually unpacking the patches for binutils manually, the package builds. However the next package (glibc) also fails in the unpacking phase. I'm attaching it's build log as well.
Created attachment 364532 [details] Build log - glibc
Created attachment 364534 [details] environ
Created attachment 364536 [details] environment - glibc
Created attachment 364538 [details] patch-output - glibc
sounds like something is fundamentally broken in your system. does it only happen with cross packages, or does it happen with other ones ? is your portage install broken ? try `qcheck portage`. do you have weird bashrc hooks ? or portage env settings ? you can run `emerge --debug pkg >& log` and post that output as an attachment
I'm thinking that is probably the case as well, because I was able to get it to build on a separate system. However, I can't seem to figure out what it is. Normal portage stuff outside of cross packages works fine. 'qcheck portage' checks out ok The only thing I've added to bashrc is "source /etc/profile" No custom portage env settings (that I'm aware of) I'll add the debug log from 'emerge --oneshot --nodeps --debug cross-armv6j-hardfloat-linux-gnueabi/glibc >& debug.log'
Created attachment 364542 [details] emerge debug log
you have ridiculous CFLAGS. use something sane like: CFLAGS="-O2 -march=native -pipe" same goes for CXXFLAGS. then rebuild your glibc/gcc/binutils/patch/portage/python/bash programs and see if the problem fixes itself.
