Summary: | [cross-powerpc64/gcc] sys-devel/gcc-4.4.2 fails with libgcc/../gcc/config/freebsd-spec.h:130:23: error: sys/param.h: No such file or directory | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jean-Francis Roy <jeanfrancis> |
Component: | [OLD] Core system | Assignee: | Gentoo Crossdev team <crossdev> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | johannes |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 627914 | ||
Attachments: |
info.log
gcc-stage2.log glibc-headers.log from crossdev cross-powerpc-unknown-linux-gnu-glibc-headers.log cross-powerpc-unknown-linux-gnu-info.log |
Description
Jean-Francis Roy
2010-02-03 03:23:14 UTC
Created attachment 218269 [details]
info.log
Created attachment 218271 [details]
gcc-stage2.log
glibc didnt fail, gcc (stage2?) did. sys/param.h is supposed to be from the glibc build, and it works on my machine. $ qlist -I -v powerpc64 cross-powerpc64-unknown-linux-gnu/binutils-2.20.1 cross-powerpc64-unknown-linux-gnu/gcc-4.4.3 cross-powerpc64-unknown-linux-gnu/glibc-2.11-r1 cross-powerpc64-unknown-linux-gnu/linux-headers-2.6.33 $ ls -l /usr/powerpc64-unknown-linux-gnu/usr/include/sys/param.h -rw-r--r-- 1 root root 2470 Mar 8 21:52 /usr/powerpc64-unknown-linux-gnu/usr/include/sys/param.h post the actual output from crossdev I just reproduced the bug. Here is the actual crossdev output: # crossdev -t powerpc64 ---------------------------------------------------------------------------------------------------------------------- * Host Portage ARCH: amd64 * Target Portage ARCH: ppc64 * Target System: powerpc64-unknown-linux-gnu * Stage: 4 (C/C++ compiler) * binutils: binutils-[latest] * gcc: gcc-[latest] * headers: linux-headers-[latest] * libc: glibc-[latest] * PORTDIR_OVERLAY: /var/lib/layman/sunrise * PORT_LOGDIR: /var/log/portage * PKGDIR: /usr/portage/packages/cross/powerpc64-unknown-linux-gnu * PORTAGE_TMPDIR: /var/tmp/cross/powerpc64-unknown-linux-gnu _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ * Forcing the latest versions of {binutils,gcc}-config/gnuconfig... [ok] * Log: /var/log/portage/cross-powerpc64-unknown-linux-gnu-binutils.log * Emerging cross-binutils... [ok] * Log: /var/log/portage/cross-powerpc64-unknown-linux-gnu-linux-headers-quick.log * Emerging cross-linux-headers-quick... [ok] * Log: /var/log/portage/cross-powerpc64-unknown-linux-gnu-glibc-headers.log * Emerging cross-glibc-headers... * glibc failed :( * If you file a bug, please attach the following logfiles: * /var/log/portage/cross-powerpc64-unknown-linux-gnu-info.log * /var/log/portage/cross-powerpc64-unknown-linux-gnu-glibc-headers.log Comment on attachment 218271 [details]
gcc-stage2.log
this log is definitely not glibc-headers
you need to post that log file then Created attachment 222773 [details]
glibc-headers.log from crossdev
This is the fresh cross-powerpc64-unknown-linux-gnu-glibc-headers.log from /var/log/portage
# ls -l cross-powerpc64-unknown-linux-gnu-glibc-headers.log
-rw-r--r-- 1 root root 864542 Mar 8 23:00 cross-powerpc64-unknown-linux-gnu-glibc-headers.log
Even if the file contains a build error from GCC, it IS cross-powerpc64-unknown-linux-gnu-glibc-headers.log created by crossdev.
The file requested as been attached, I'm reopening the bug. This file is definitely the glibc-headers log created by crossdev. If it's not what you want, there's a problem with crossdev not logging the good thing at the good place. Comment on attachment 222773 [details]
glibc-headers.log from crossdev
same log as before. guess it's a dependency issue. run crossdev with -P --nodeps to workaround the issue.
Of course it was the same log as before, you asked me to post the actual file so I did :-). You were right about the dependency issue, running with --nodeps worked. For some reason GCC was pulled before glibc-headers. So this is resolved, I put the resolution to INVALID as it seems I'm the only one who got this dependency problem. Thanks! :-) *** Bug 316669 has been marked as a duplicate of this bug. *** something isnt quite right and i need to find a day to poke it Hello, Jean-François, you're not the only one ! Having same problem with PowerPC crossdev from an x86. crossdev -d powerpc ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ * crossdev version: 20100620 * Host Portage ARCH: x86 * Target Portage ARCH: ppc * Target System: powerpc-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/layman/sunrise * PORT_LOGDIR: /var/log/portage * PKGDIR: /usr/portage/packages/cross/powerpc-unknown-linux-gnu * PORTAGE_TMPDIR: /var/tmp/cross/powerpc-unknown-linux-gnu _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - * Forcing the latest versions of {binutils,gcc}-config/gnuconfig ... [ ok ] * Log: /var/log/portage/cross-powerpc-unknown-linux-gnu-binutils.log * Emerging cross-binutils ... [ ok ] * Log: /var/log/portage/cross-powerpc-unknown-linux-gnu-linux-headers-quick.log * Emerging cross-linux-headers-quick ... [ ok ] * Log: /var/log/portage/cross-powerpc-unknown-linux-gnu-glibc-headers.log * Emerging cross-glibc-headers ... * glibc failed :( * If you file a bug, please attach the following logfiles: * /var/log/portage/cross-powerpc-unknown-linux-gnu-info.log * /var/log/portage/cross-powerpc-unknown-linux-gnu-glibc-headers.log Attaching files... Created attachment 245803 [details]
cross-powerpc-unknown-linux-gnu-glibc-headers.log
Created attachment 245806 [details]
cross-powerpc-unknown-linux-gnu-info.log
Comment on attachment 245803 [details]
cross-powerpc-unknown-linux-gnu-glibc-headers.log
your error is unrelated
Let's close it as obsolete. It's an old bug against old gcc version. Probably fixed/worked-around by bug #686248. |