| Summary: | dev-util/valgrind: fails to build on <ARMv7 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Tres 'RiverRat' Melton <RiverRat> |
| Component: | [OLD] Development | Assignee: | Anthony Basile <blueness> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | normal | CC: | kripton, xmw |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | ARM | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 475662 | ||
| Attachments: |
The output
The build log emerge pretend emerge info |
||
Created attachment 352540 [details]
The build log
Created attachment 352542 [details]
emerge pretend
Created attachment 352544 [details]
emerge info
I've gone into the auto config tools and adjusted it to build anyway and it does completely build but it fails to run as it tries to use illegal op codes (from the ARMv7) so the problem is deep. The ebuild should recognize the family of ARM chip that this is and fail to even try to install. This ebuild should be hardmasked on the Raspberry Pi (ARMv6j). *** Bug 475662 has been marked as a duplicate of this bug. *** pretty sure this is a known issue upstream and there's nothing we're going to do about it in Gentoo land |
Created attachment 352538 [details] The output checking build system type... armv6j-hardfloat-linux-gnueabi checking host system type... armv6j-hardfloat-linux-gnueabi checking for a supported CPU... no (armv6j) configure: error: Unsupported host architecture. Sorry