Summary: | >=www-client/chromium-73.0.3683.75 fail to detect cross-compiler and runs into error: unrecognized command line option ‘-mfpu=neon` | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | tt_1 <herrtimson> |
Component: | Current packages | Assignee: | Chromium Project <chromium> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://chromium.googlesource.com/chromium/src/build/+/master/toolchain/linux/unbundle/ | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
build log of chromium
output of emerge --info for armv7a-unknown-linux-gnueabihf |
Description
tt_1
2019-03-18 21:41:58 UTC
Created attachment 569734 [details]
build log of chromium
Created attachment 569736 [details]
output of emerge --info for armv7a-unknown-linux-gnueabihf
the document I linked says: use a custom toolchain if you're a distro by adding custom_toolchain="//build/toolchain/linux/unbundle:default" and also to add this in case of cross-compile: host_toolchain="//build/toolchain/linux/unbundle:host" v8_snapshot_toolchain="//build/toolchain/linux/unbundle:host" which to my reading of the ebuild and the build.log is the case here. I don't know where to even start to look at, can you give a bit of direction what could be the cause for this? file of interest might be BUILD.gn and build/toolchain/gcc_toolchain.gni the non-working part of the ebuild is here:
tc-export BUILD_{AR,CC,CXX,NM}
if setting the BUILD_* variables manually, it works in the sense of using the cross-compiler instead of the hosts.
< tc-export BUILD_{AR,CC,CXX,NM}
---
>
> export BUILD_AR=armv7a-unknown-linux-gnueabihf-ar
> export BUILD_CC=armv7a-unknown-linux-gnueabihf-gcc
> export BUILD_CXX=armv7a-unknown-linux-gnueabihf-g++
> export BUILD_NM=armv7a-unknown-linux-gnueabihf-nm
It still fails for another reason, but that's expected and not part of this bug.
|