From: Guenter Roeck <private@roeck-us.net>
To: Arnd Bergmann <arnd@arndb.de>, Greentime Hu <green.hu@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Vincent Chen <vincentc@andestech.com>,
Greentime Hu <greentime@andestech.com>,
kito.cheng@gmail.com, wuiw@andestech.com
Subject: Re: nds32 build failures
Date: Tue, 17 Apr 2018 06:12:54 -0700 [thread overview]
Message-ID: <f7facab2-ca5d-ceb8-78f1-92a055627f6c@roeck-us.net> (raw)
In-Reply-To: <CAK8P3a2cogDMEdvhNt8CsJwaONWOgBR7zR3sABun4u8pAgTtqQ@mail.gmail.com>
On 04/17/2018 05:47 AM, Arnd Bergmann wrote:
> On Mon, Apr 16, 2018 at 11:06 AM, Greentime Hu <green.hu@gmail.com> wrote:
>> 2018-04-16 11:58 GMT+08:00 Guenter Roeck <private@roeck-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
next prev parent reply other threads:[~2018-04-17 13:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 3:58 Guenter Roeck
2018-04-16 9:06 ` Greentime Hu
2018-04-16 13:22 ` Guenter Roeck
2018-04-16 13:59 ` Guenter Roeck
2018-04-17 12:47 ` Arnd Bergmann
2018-04-17 13:12 ` Guenter Roeck [this message]
2018-04-18 7:19 ` Greentime Hu
2018-05-11 2:40 ` Arnd Bergmann
2018-05-11 4:31 ` Guenter Roeck
2018-05-11 5:17 ` Kito Cheng
2018-05-22 2:15 ` Vincent Chen
2018-05-22 10:39 ` Arnd Bergmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f7facab2-ca5d-ceb8-78f1-92a055627f6c@roeck-us.net \
--to=private@roeck-us.net \
--cc=arnd@arndb.de \
--cc=green.hu@gmail.com \
--cc=greentime@andestech.com \
--cc=kito.cheng@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vincentc@andestech.com \
--cc=wuiw@andestech.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®