Per instructions at http://dev.gentoo.org/~armin76/arm/beaglebone/install.xml Build a crosscompiler Code Listing 3.2: Building a crosscompiler # crossdev -S armv7a-unknown-linux-gnueabi fails trying to build glibc. Reproducible: Always Steps to Reproduce: 1. crossdev -S armv7a-unknown-linux-gnueabi Actual Results: hermes portage # crossdev -S armv7a-unknown-linux-gnueabi -------------------------------------------------------------------------------- * crossdev version: 20120531 * Host Portage ARCH: amd64 * Target Portage ARCH: arm * Target System: armv7a-unknown-linux-gnueabi * Stage: 4 (C/C++ compiler) * ABIs: default * binutils: binutils-[stable] * gcc: gcc-[stable] * headers: linux-headers-[stable] * libc: glibc-[stable] * CROSSDEV_OVERLAY: /var/lib/layman/stuge * PORT_LOGDIR: /var/log/portage * PORTAGE_CONFIGROOT: * Portage flags: _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - * Log: /var/log/portage/cross-armv7a-unknown-linux-gnueabi-binutils.log * Emerging cross-binutils ... [ ok ] * Log: /var/log/portage/cross-armv7a-unknown-linux-gnueabi-linux-headers-quick.log * Emerging cross-linux-headers-quick ... [ ok ] * Log: /var/log/portage/cross-armv7a-unknown-linux-gnueabi-glibc-headers.log * Emerging cross-glibc-headers ... [ ok ] * Log: /var/log/portage/cross-armv7a-unknown-linux-gnueabi-gcc-stage1.log * Emerging cross-gcc-stage1 ... [ ok ] * Log: /var/log/portage/cross-armv7a-unknown-linux-gnueabi-linux-headers.log * Emerging cross-linux-headers ... [ ok ] * Log: /var/log/portage/cross-armv7a-unknown-linux-gnueabi-glibc.log * Emerging cross-glibc ... * glibc failed :( * If you file a bug, please attach the following logfiles: * /var/log/portage/cross-armv7a-unknown-linux-gnueabi-info.log * /var/log/portage/cross-armv7a-unknown-linux-gnueabi-glibc.log.xz * /var/tmp/portage/cross-armv7a-unknown-linux-gnueabi/glibc*/temp/glibc-config.logs.tar.xz hermes portage # Expected Results: successful build of cross-dev environment It's not clear where this bug should be filed. It would be helpful if the output indicated whether bugs should be lodged against cross-dev or the component that fails, in this case, glibc
* If you file a bug, please attach the following logfiles: * /var/log/portage/cross-armv7a-unknown-linux-gnueabi-info.log * /var/log/portage/cross-armv7a-unknown-linux-gnueabi-glibc.log.xz * /var/tmp/portage/cross-armv7a-unknown-linux-gnueabi/glibc*/temp/glibc-config.logs.tar.xz Please attach these (separately).
Created attachment 322110 [details] cross-armv7a-unknown-linux-gnueabi-info.log
Created attachment 322112 [details] cross-armv7a-unknown-linux-gnueabi-glibc.log.xz
Created attachment 322114 [details] /var/tmp/portage/cross-armv7a-unknown-linux-gnueabi/glibc*/temp/glibc-config.logs.tar.xz
Is there a way to initially attach files when creating a bug? Here, I opened the bug and immediately proceeded to attach files, yet a very watchful bugmeister intervened and found the attachments not present. I have found myself in this situation before and do recall seeing in the interface a way to attach files at the outset. Is there something in the new bug interface that allows attachments?
(In reply to comment #5) > I have found myself in this situation before and do recall seeing in the should be: I have found myself in this situation before and do *not* recall seeing in the
(In reply to comment #5) you can attach just one file with the initial bug report. additional files have to be attached one-by-one. obvious question: have you synced your tree recently ?
(In reply to comment #7) > (In reply to comment #5) > obvious question: have you synced your tree recently ? I updated several weeks ago. I just emerge --sync against my server which, in turn, I emerge --sync (OSU), and I'm attaching the emerge --pretend listing. Some of the packages, e.g. postgis 2.0 do not successfully emerge for various reasons. I'll proceed with the update, but wanted to give you a bird's eye view of the state of my machine using the emerge_pretend.txt
Created attachment 322118 [details] emerge --update --newuse --deep world -p output
i'm not really interested in the general system packages being up to date. i want to make sure that you aren't simply hitting the same bug already reported and fixed. *** This bug has been marked as a duplicate of bug 431304 ***
I updated my tree (everything execept postgis-2.0 and sci-geosciences) and retried. Success: I made it past the glibc hurdle and the crossdev script completed without incident. Thank you.
(In reply to comment #11) in the future, please make sure your tree is up-to-date before filing bugs
I will. Sorry about that, this is a machine I don't use daily and last time I started it up, I had brought it current... but that was several weeks ago.
