| Summary: | crossdev -t bfin-elf : newlib headers failed | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | amusingmuses |
| Component: | New packages | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | amusingmuses, binki, cbruner |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
crossdev requested file
crossdev requested file, general build info |
||
Created attachment 204387 [details]
crossdev requested file
Created attachment 204389 [details]
crossdev requested file, general build info
bfin-softfloat-elf is an invalid target. use bfin-elf. i'm not sure if newlib-1.16.0 had proper Blackfin support in it, i'll have to double check. although that may not be the problem here. (In reply to comment #3) > bfin-softfloat-elf is an invalid target. use bfin-elf. > > i'm not sure if newlib-1.16.0 had proper Blackfin support in it, i'll have to > double check. although that may not be the problem here. > From what I can glean from: http://www.gentoo.org/proj/en/base/embedded/handbook/index.xml?part=1&chap=3 It should be a valid target... How do you know it's an invalid target? How can I learn what valid targets are? That doc would serve many readers well to explain such things. -t bfin-elf failed too by the way in pretty much the same manner. A workaround I found on the gentoo forums: crossdev --without-headers -s1 -t bfin-softfloat-elf crossdev -t bfin-softfloat-elf Worked i know it's a valid target because i'm one of the developers of the Blackfin architecture. softfloat makes no sense because no Blackfin has FPU support in it. some of the toolchain packages internally parse the target looking for "bfin-elf". (In reply to comment #6) > i know it's a valid target because i'm one of the developers of the Blackfin > architecture. softfloat makes no sense because no Blackfin has FPU support in > it. some of the toolchain packages internally parse the target looking for > "bfin-elf". > Right but since the docs give you no frame of reference at all then for all one can tell, softfloat is the /only/ option that makes sense, given that no Blackfin has an FPU. Anyways I'll update my configuration now that I know there are internal parts that ostensibly expect a hard coded string like "bfin-elf". softfloat is for toolchains where the default is to assume FPU support. that is most architectures, but not the Blackfin arch. really it only makes sense on arm/mips/ppc ports. *** This bug has been marked as a duplicate of bug 259144 *** |
-------------------------------------------------------------------------------- * Host Portage ARCH: x86 * Target Portage ARCH: * * Target System: bfin-softfloat-elf * Stage: 3 (C compiler & libc) * binutils: binutils-[latest] * gcc: gcc-[latest] * libc: newlib-[latest] * PORTDIR_OVERLAY: /usr/local/portage * PORT_LOGDIR: /var/log/portage * PKGDIR: /usr/portage/packages/cross/bfin-softfloat-elf * PORTAGE_TMPDIR: /var/tmp/cross/bfin-softfloat-elf _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - * Forcing the latest versions of {binutils,gcc}-config/gnuconfig ... [ ok ] * Log: /var/log/portage/cross-bfin-softfloat-elf-binutils.log * Emerging cross-binutils ... [ ok ] * Log: /var/log/portage/cross-bfin-softfloat-elf-newlib-headers.log * Emerging cross-newlib-headers ... * newlib failed :( * If you file a bug, please attach the following logfiles: * /var/log/portage/cross-bfin-softfloat-elf-info.log * /var/log/portage/cross-bfin-softfloat-elf-newlib-headers.log --------- SNIP from /var/log/portage/cross-bfin-softfloat-elf-newlib-headers.log: make[5]: Entering directory `/var/tmp/cross/bfin-softfloat-elf/portage/cross-bfi n-softfloat-elf/newlib-1.16.0/work/build/bfin-softfloat-elf/newlib/libc' rm -f libc.a rm -rf tmp mkdir tmp cd tmp; \ for i in argz/lib.a stdlib/lib.a ctype/lib.a search/lib.a stdio/lib.a string/lib.a signal/lib.a time/lib.a locale/lib.a reent/lib.a errno/lib.a misc/ lib.a syscalls/lib.a machine/lib.a ; do \ bfin-softfloat-elf-ar x ../$i; \ done; \ bfin-softfloat-elf-ar rc ../libc.a *.o bfin-softfloat-elf-ar: ../argz/lib.a: No such file or directory bfin-softfloat-elf-ar: ../stdlib/lib.a: No such file or directory bfin-softfloat-elf-ar: ../ctype/lib.a: No such file or directory bfin-softfloat-elf-ar: ../search/lib.a: No such file or directory bfin-softfloat-elf-ar: ../stdio/lib.a: No such file or directory bfin-softfloat-elf-ar: ../string/lib.a: No such file or directory bfin-softfloat-elf-ar: ../signal/lib.a: No such file or directory Each referenced directory contains only a Makefile and no lib.a, so the Makefile running this code probably should call the Makefiles in the subdirectories first--would be my guess. If this is indeed likely the problem, let me know and I'll see if I can figure out how to fix the Makefile and submit a patch myself if I'm successful.