[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f7facab2-ca5d-ceb8-78f1-92a055627f6c@roeck-us.net>
Date: Tue, 17 Apr 2018 06:12:54 -0700
From: Guenter Roeck <private@...ck-us.net>
To: Arnd Bergmann <arnd@...db.de>, Greentime Hu <green.hu@...il.com>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Vincent Chen <vincentc@...estech.com>,
Greentime Hu <greentime@...estech.com>, kito.cheng@...il.com,
wuiw@...estech.com
Subject: Re: nds32 build failures
On 04/17/2018 05:47 AM, Arnd Bergmann wrote:
> On Mon, Apr 16, 2018 at 11:06 AM, Greentime Hu <green.hu@...il.com> wrote:
>> 2018-04-16 11:58 GMT+08:00 Guenter Roeck <private@...ck-us.net>:
>>
>> This built failure is because the toolchain version you used is not
>> supported the latest intrinsic function/macro.
>> We are sending the latest patchset now and we expect the whole new
>> features will be supported in gcc8.0.0 and binutil2.31+.
>>
>> If you'd like to get these new features of toolchain, you may use the
>> github version.
>> This is the built-script repo. https://github.com/andestech/build_script.git
> I've taken the gcc-6.3 sources from there, and updated them to gcc-6.4.0
> in order to build a nds32le-linux toolchain based on the same version as
> the other ones.
>
> Unfortunately neither the usual binutils-2.29.1 nor your binutils worked
> for me, but I eventually managed to get a build using the binutils-2.30
> release.
>
> With this, I could build a mainline kernel with a couple of warnings,
> but an 'allmodconfig' build still failed.
>
> Guenter, can you try my binary from
> www.kernel.org/pub/tools/crosstool/files/bin/x86_64/6.4.0/x86_64-gcc-6.4.0-nolibc-nds32le-linux.tar.xz
> ?
defconfig and allnoconfig are ok. allyesconfig results in a linker core dump,
unrecognized instruction warnings from the assembler, and various vdso
related build errors.
Guenter
Powered by blists - more mailing lists