/ # crossdev -t hppa1.1 -------------------------------------------------------------------------------- * crossdev version: 20101011 * Host Portage ARCH: x86 * Target Portage ARCH: hppa * Target System: hppa1.1-unknown-linux-gnu * Stage: 4 (C/C++ compiler) * binutils: binutils-[latest] * gcc: gcc-[latest] * headers: linux-headers-[latest] * libc: glibc-[latest] * PORTDIR_OVERLAY: /usr/local/portage * PORT_LOGDIR: /var/log/portage * PORTAGE_CONFIGROOT: _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - * Forcing the latest versions of {binutils,gcc}-config/gnuconfig ... [ ok ] * Log: /var/log/portage/cross-hppa1.1-unknown-linux-gnu-binutils.log * Emerging cross-binutils ... [ ok ] * Log: /var/log/portage/cross-hppa1.1-unknown-linux-gnu-linux-headers-quick.log * Emerging cross-linux-headers-quick ... [ ok ] * Log: /var/log/portage/cross-hppa1.1-unknown-linux-gnu-glibc-headers.log * Emerging cross-glibc-headers ... [ ok ] * Log: /var/log/portage/cross-hppa1.1-unknown-linux-gnu-gcc-stage1.log * Emerging cross-gcc-stage1 ... [ ok ] * Log: /var/log/portage/cross-hppa1.1-unknown-linux-gnu-linux-headers.log * Emerging cross-linux-headers ... [ ok ] * Log: /var/log/portage/cross-hppa1.1-unknown-linux-gnu-glibc.log * Emerging cross-glibc ... * glibc failed :( * If you file a bug, please attach the following logfiles: * /var/log/portage/cross-hppa1.1-unknown-linux-gnu-info.log * /var/log/portage/cross-hppa1.1-unknown-linux-gnu-glibc.log !!!!! As a further hint it happens the same on the hppa K210 system I'm trying to cross compile for Reproducible: Always Steps to Reproduce: 1.emerge distcc emerge crossdev 2.run command 3. Actual Results: see above screen output Expected Results: cross compiled helper pc
Created attachment 268973 [details] output log suggested by output--partial this is the end of the log where the eroors started--I think..
Created attachment 268975 [details] information log
(In reply to comment #1) > Created attachment 268973 [details] > output log suggested by output--partial > > this is the end of the log where the errors started--I think.. Sorry, that's not the relevant part -- the real error info came earlier. If the full log file is huge, you can attach it compressed.
ive fixed a build error related to DEFAULT_STACK_PERMS. assuming that is the issue you're hitting.
