From: Guenter Roeck <private@roeck-us.net>
To: 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>,
Arnd Bergmann <arnd@arndb.de>,
kito.cheng@gmail.com, wuiw@andestech.com
Subject: Re: nds32 build failures
Date: Mon, 16 Apr 2018 06:22:01 -0700 [thread overview]
Message-ID: <a009bde1-c2d5-02ad-91ae-e2af2dc9f789@roeck-us.net> (raw)
In-Reply-To: <CAEbi=3cr5i3HKLKOacFih9pz00c7UBKrd=o4ER8HAUT1j_oqGg@mail.gmail.com>
On 04/16/2018 02:06 AM, Greentime Hu wrote:
> 2018-04-16 11:58 GMT+08:00 Guenter Roeck <private@roeck-us.net>:
>> I thought I should give the brand new architecture a try. Unfortunately,
>> that was not very successful.
>>
>> Build reference: v4.17-rc1
>> gcc version: nds32le-elf-gcc (GCC) 7.3.0
>>
>> Building nds32:defconfig ... failed
>>
>> arch/nds32/include/asm/nds32.h: In function 'GIE_ENABLE':
>> arch/nds32/include/asm/nds32.h:25:2: error: implicit declaration of function
>> '__nds32__gie_en'; did you mean '__nds32__'?
>>
>> arch/nds32/include/asm/nds32.h: In function 'CACHE_SET':
>> arch/nds32/include/asm/nds32.h:38:18: error: implicit declaration of
>> function '__nds32__mfsr'; did you mean '__nds32__'?
>>
>> arch/nds32/include/asm/nds32.h:38:32: error: 'NDS32_SR_ICM_CFG' undeclared
>>
>> arch/nds32/include/asm/nds32.h:41:32: error: 'NDS32_SR_DCM_CFG'
>>
>> Am I missing something ?
>>
> Hi, Guenter:
>
> 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
>
Hmm. How comes that the defines are not there ? Also, is nds32_intrinsic.h supposed to be auto-generated ?
The toolchain as provided isn't usable for me since it is not position independent.
Arnd, it might make sense to drop the nds32 toolchain from kernel.org; its presence is at best misleading.
Guenter
next prev parent reply other threads:[~2018-04-16 13:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 3:58 nds32 build failures Guenter Roeck
2018-04-16 9:06 ` Greentime Hu
2018-04-16 13:22 ` Guenter Roeck [this message]
2018-04-16 13:59 ` Guenter Roeck
2018-04-17 12:47 ` Arnd Bergmann
2018-04-17 13:12 ` Guenter Roeck
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=a009bde1-c2d5-02ad-91ae-e2af2dc9f789@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;
as well as URLs for NNTP newsgroup(s).