On Wed, Feb 13, 2019 at 09:59:38AM +0100, Koen Kooi wrote:
Op 13 feb. 2019, om 01:54 heeft Denys Dmytriyenko denis@denix.org het volgende geschreven:
On Thu, Feb 07, 2019 at 11:07:21AM +0100, Koen Kooi wrote:
Op 6 feb. 2019, om 22:58 heeft Denys Dmytriyenko denis@denix.org het volgende geschreven:
On Wed, Feb 06, 2019 at 09:30:04AM +0100, Koen Kooi wrote:
Op 5 feb. 2019, om 17:32 heeft Denys Dmytriyenko denis@denix.org het volgende geschreven:
On Tue, Feb 05, 2019 at 11:24:58AM +0100, Koen Kooi wrote: > >> Op 5 feb. 2019, om 07:48 heeft Denys Dmytriyenko denis@denix.org het volgende geschreven: >> >> From: Denys Dmytriyenko denys@ti.com >> >> Fixes for the recently introduced external ARM toolchain support. > > Thanks for all these! I had done 1/15 already locally and was reworking the > FILES_* based on OE-core changes. I’ll fold your patches into my patchset > and push that to gerrit later today.
Sounds good, thanks! I'm still working on other areas, such as using EAT in SDK. Will probably have more fixes coming...
But I have 2 requests:
- There's "arm-8.2" recipe now, thanks. Can we also get "arm-2.30" version
of binutils? Trying to match the versions and oe-core/thud has 2.31, while oe-core/master has 2.32.
I’m a bit hesitant to add that, since the ‘arm-2.30’ version is unmodified upstream 2.30. But leaving ‘arm’ out of the name will lead to many, many emails from confused users :/
I guess I can try living with 2.31 from oe-core/thud, should be close enough. Hopefully won't cause any issues...
- Once everything is fixed, can this be backported to thud branch? It was
released with gcc 8.2, so should fit nicely. The only difference is that master removed gcc-cross{,sdk}-initial, which needs to be fixed for thud: https://git.linaro.org/openembedded/meta-linaro.git/commit/?id=1107d1a2d3bb9...
It’s on my TODO, but very low down since it hasn’t been requested yet internally.
Would be nice, thanks.
Also, have you tried building qtwebkit from meta-qt5 for aarch64 with this Arm toolchain? I had no problems building it with gcc 8.2 from oe-core, but now getting:
/opt/gcc-arm-8.2-2019.01-x86_64-aarch64-linux-gnu/bin/../lib/gcc/aarch64-linux-gnu/8.2.1/../../../../aarch64-linux-gnu/bin/ld.gold: fatal error: /opt/gcc-arm-8.2-2019.01-x86_64-aarch64-linux-gnu/bin/../libexec/gcc/aarch64-linux-gnu/8.2.1/liblto_plugin.so: unsupported ELF machine number 62
Any ideas? Thanks.
While I haven’t tried webkit, I get this when trying to build go (for docker):
| Building std for target, linux/arm64. | # /build/rpb-master/build-rpb/tmp-rpb-glibc/work/aarch64-linaro-linux/go-runtime/1.11.4-r0/go-tmp/go-build841039236/b189/libstd.so | /build/rpb-master/build-rpb/tmp-rpb-glibc/work/aarch64-linaro-linux/go-runtime/1.11.4-r0/go/pkg/tool/native_native/link: running aarch64-linux-gnu-gcc failed: exit status 1 | /home/koen/arm-toolchain/gcc-arm-8.2-2019.01-x86_64-aarch64-linux-gnu/bin/../lib/gcc/aarch64-linux-gnu/8.2.1/../../../../aarch64-linux-gnu/bin/ld.gold: fatal error: /home/koen/arm-toolchain/gcc-arm-8.2-2019.01-x86_64-aarch64-linux-gnu/bin/../libexec/gcc/aarch64-linux-gnu/8.2.1/liblto_plugin.so: unsupported ELF machine number 62 | collect2: error: ld returned 1 exit status
Google suggests ’62’ is x86_64, so something is getting misdetect. And like you gcc 8.2 from OE-core has not issues with this. I’m going to sort out the packaging issues first before looking at this.
Any updates on packaging issues?
Fixed and merged into master, please give it a try and see if I missed something.
Thanks! Seems to work fine. How about back-porting it to thud now? :) Let me know if you'd like me to submit patches - like I said earlier, it needs some fixing around gcc-cross{,sdk}-initial recipes...
Linaro bugzilla has an entry for this prebuilt arm toolchain nowadays, so could you file a bug for this?
Thanks!
Have you had any luck with this issue? I haven't yet looked too close into it myself though.