| Summary: | cross-arm-linux-gnueabihf/gcc-4.8.3 - checking dynamic linker characteristics... configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES. | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Luke-Jr <luke-jr+gentoobugs> |
| Component: | [OLD] Core system | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | normal | CC: | ag+services, godzil |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
emerge --info
build.log.xz my emerge --info gcc-config logs cross-armv6j-hardfloat-linux-gnueabi-info logs cross-armv6j-hardfloat-linux-gnueabi-gcc-stage1 logs |
||
Created attachment 387024 [details]
build.log.xz
Comment on attachment 387024 [details]
build.log.xz
You don't need to explain why you use compression.
I haven't tested with other CHOST, but it fail in the same way on my side with cross-armv6j-hardfloat-linux-gnueabi and cross-armv6zk-hardfloat-linux-gnueabi and cross-armv7a-hardfloat-linux-gnueabi. All of them are CHOST for targeting the RaspberryPi. I'm using the Funtoo "flavor" but I doubt it would change anything about that, crossdev is the latest "unstable" 20151026 and it fail at GCC stage1. I've tried with version 5.3, 4.9.3 and 4.8.5 of GCC all fail the same way. I suspect there is a configuration issue, but I'm absolutely clueless. I've build by hand cross version GCC in the past but it was always a pain and crossdev solved some of them even if not completely painless, but this one leave me completely clueless. The build command was: USE="-fortran nossp" crossdev -S --gcc 4.9.3 -t armv6j-hardfloat-linux-gnueabi I don't know why ~amd64 is activated as it's not part of my make.conf nor any profile as far as I know, I have to check on that side, but I don't think it can be the culprit here. I will try to attach the logs from crossdev and my emerge --info Created attachment 441728 [details]
my emerge --info
Created attachment 441730 [details]
gcc-config logs
Created attachment 441732 [details]
cross-armv6j-hardfloat-linux-gnueabi-info logs
Created attachment 441734 [details]
cross-armv6j-hardfloat-linux-gnueabi-gcc-stage1 logs
looks like your gcc stage1 is trying to build stuff it shouldn't. crossdev disables a ton of USE flags for the stage1 build, but your gcc has them enabled anyways. should figure out why. most notably, mudflap & libstdc++ shouldn't even be built. yet configure has: --enable-libmudflap --enable-languages=c,c++,lto you're also using Funtoo which makes the output even less useful. |
Created attachment 387022 [details] emerge --info gcc-4.8.3 rebuilds were triggered by a new 'sanitize' USE flag. However, the ebuild no longer compiles for *some* ARM targets (it did in the past). Whether USE=sanitize is set or not seems to be irrelevant. Failed ARM builds: arm-none-eabi and arm-linux-gnueabihf Successful ARM builds: arm-linux-gnueabi, arm-none-linux-gnueabi, armv7a-linux-gnueabi, armv7a-softfloat-linux-gnueabi, armv7a-unknown-linux-gnueabi Additionally, MIPS and PowerPC cross-compilers succeeded in this rebuild.