Michael Weyershäuser wrote: > Daniel Iliev wrote: > >> I tried to use a x86 pc to aid the compiling of packages for amd64 via >> distcc. I followed the official "DistCC Cross-compiling Guide" [1] but I >> had no luck. Is it possible at all, am I doing something wrong or there >> is a bug? >> >> [1] http://www.gentoo.org/doc/en/cross-compiling-distcc.xml >> >> > I'm running such a setup for about 6 months now and I have never run > into any package not compiling due to the crossdev environment (and I > compile quite a lot of packages as an amd64 AT). So this should in > general work without any trouble or patches. > >> The i686 pc gives: >> >> localhost ~ # crossdev -t x86_64-pc-linux-gnu >> * You need to set PORTDIR_OVERLAY in your make.conf. >> * A standard setting is /usr/local/portage >> localhost ~ # echo PORTDIR_OVERLAY=/usr/local/portage >> /etc/make.conf >> localhost ~ # crossdev -t x86_64-pc-linux-gnu >> !!! Invalid PORTDIR_OVERLAY (not a dir): '/usr/local/portage' >> !!! Invalid PORTDIR_OVERLAY (not a dir): '/usr/local/portage' >> >> localhost ~ # mkdir /usr/local/portage >> localhost ~ # crossdev -t x86_64-pc-linux-gnu >> -------------------------------------------------------------------------------- >> * Host Portage ARCH: x86 >> * Target Portage ARCH: amd64 >> * Target System: x86_64-pc-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 >> * PKGDIR: /usr/portage/packages/cross/x86_64-pc-linux-gnu >> * PORTAGE_TMPDIR: /tmp/cross/x86_64-pc-linux-gnu >> _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ >> - _ - >> * Forcing the latest versions of binutils-config/gcc-config >> ... [ ok ] >> * Log: /var/log/portage/cross-x86_64-pc-linux-gnu-binutils.log >> * Emerging cross-binutils ... >> >> * binutils failed :( >> * If you file a bug, please attach the following logfiles: >> * /var/log/portage/cross-x86_64-pc-linux-gnu-info.log >> * /var/log/portage/cross-x86_64-pc-linux-gnu-binutils.log >> > > If this was a bug I would close it as RESOLVED NEEDINFO right now. > Please attach these two log files if you want anybody to be able to help > you ;) > > >
I saw an update for gcc and after emerging it I decided to try again. Four steps forward but the final goal is not achieved yet. crossdev -t x86_64-pc-linux-gnu -------------------------------------------------------------------------------- * Host Portage ARCH: x86 * Target Portage ARCH: amd64 * Target System: x86_64-pc-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 * PKGDIR: /usr/portage/packages/cross/x86_64-pc-linux-gnu * PORTAGE_TMPDIR: /tmp/cross/x86_64-pc-linux-gnu _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - * Forcing the latest versions of binutils-config/gcc-config ... [ ok ] * Log: /var/log/portage/cross-x86_64-pc-linux-gnu-binutils.log * Emerging cross-binutils ... [ ok ] * Log: /var/log/portage/cross-x86_64-pc-linux-gnu-gcc-stage1.log * Emerging cross-gcc-stage1 ... [ ok ] * Log: /var/log/portage/cross-x86_64-pc-linux-gnu-linux-headers.log * Emerging cross-linux-headers ... [ ok ] * Log: /var/log/portage/cross-x86_64-pc-linux-gnu-glibc.log * Emerging cross-glibc ... * glibc failed :( * If you file a bug, please attach the following logfiles: * /var/log/portage/cross-x86_64-pc-linux-gnu-info.log * /var/log/portage/cross-x86_64-pc-linux-gnu-glibc.log The last file is attached in this email message as a bzip2 archive. At its end this log file reads: >checking for forced unwind support... no >configure: error: forced unwind support is required Unfortunately I have no idea what this means. Any suggestions, please? -- Best regards, Daniel -- [email protected] mailing list
