> -----Original Message-----
> From: Tom Rini [mailto:[email protected]]
> Sent: Tuesday, April 24, 2018 4:17 AM
> To: [email protected]; Rick Jian-Zhi Chen(陳建志)
> Subject: NDS32 toolchain?
>
> Hey,
>
> So I'm looking over my setups again at what we do and do not have build 
> testing
> and run-time testing, and I see that for nds32 I just cannot find a good 
> toolchain.
> If I try for example
> https://mirrors.edge.kernel.org/pub/tools/crosstool/files/bin/x86_64/7.3.0/x86_
> 64-gcc-7.3.0-nolibc-nds32-elf.tar.xz
> it first fails on the -G0 flag that we have set in and then it complains 
> about a lack
> of position independent code support.  Is the kernel.org toolchain perhaps
> configured incorrectly?
>

Hi Tom

You may try the following paths:

1.
github version
https://github.com/andestech/build_script.git
https://github.com/greentime/prebuilt-nds32-toolchain/releases

2.
Arnd Bergmann built
https://lkml.org/lkml/2018/4/17/395
www.kernel.org/pub/tools/crosstool/files/bin/x86_64/6.4.0/x86_64-gcc-6.4.0-nolibc-nds32le-linux.tar.xz

> Related, is there a QEMU target for nds32 that we could leverage so that once
> the toolchain issue is resolved we can update .travis.yml to run tests on it?
> Thanks!
>

I am applying the QEMU offering permit.
If it is ok. I will prepare it for you.

Thanks

Rick :)

> --
> Tom
CONFIDENTIALITY NOTICE:

This e-mail (and its attachments) may contain confidential and legally 
privileged information or information protected from disclosure. If you are not 
the intended recipient, you are hereby notified that any disclosure, copying, 
distribution, or use of the information contained herein is strictly 
prohibited. In this case, please immediately notify the sender by return 
e-mail, delete the message (and any accompanying documents) and destroy all 
printed hard copies. Thank you for your cooperation.

Copyright ANDES TECHNOLOGY CORPORATION - All Rights Reserved.
_______________________________________________
U-Boot mailing list
[email protected]
https://lists.denx.de/listinfo/u-boot

Reply via email to