From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v5 0/4] Add prebuilt nds32 toolchain, ae3xx board and autobuild configs support
Date: Wed, 17 Apr 2019 21:22:09 +0200 [thread overview]
Message-ID: <20190417212209.09ef3182@windsurf> (raw)
In-Reply-To: <20190416072545.17633-1-nylon7@andestech.com>
Hello Nylon,
On Tue, 16 Apr 2019 15:25:41 +0800
Nylon Chen <nylon7@andestech.com> wrote:
> Nylon Chen (4):
> arch: add support for Andes 32-bit(nds32)
> configs/andes_nds32_ae3xx: new defconfig
> toolchain-external-andes-nds32: new package
> support/config-fragments/autobuild: test the Andes nds32 toolchain
Following the merge of the nds32 architecture, two types of build
failures started to appear:
- The target binutils package failed to build, because binutils does
not yet have support for nds32. I tried with the latest binutils
release, 2.32, and it was the same. So for now, I have disabled
binutils on nds32. However, in binutils source, I see that
bfd/elf-nds32.c is present, so there at least the beginning of some
support. Could you comment on the status of nds32 support in
binutils upstream ?
Build failure: http://autobuild.buildroot.net/results/1b1/1b18acb11db4d6c4198deb7385aff3d4d524c37e/build-end.log
Commit to disable binutils on nds32: https://git.buildroot.org/buildroot/commit/?id=b45a703078e6f3be096f24ac63848490d32d0d29
- The libffi library does not have support for nds32 as well, so I
made sure that we don't try to build configurations that include
libffi on nds32. Are you planning on adding nds32 support to libffi
upstream ?
Build failure: http://autobuild.buildroot.net/results/128/12803a705586e82fdfb49013da2eb3b9879ccd45/build-end.log
Commit to disable libffi on nds32: https://git.buildroot.org/buildroot/commit/?id=2e1f98d9509d869352080331e168abe5f1452e1a
Best regards,
Thomas Petazzoni
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-04-17 19:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 7:25 [Buildroot] [PATCH v5 0/4] Add prebuilt nds32 toolchain, ae3xx board and autobuild configs support Nylon Chen
2019-04-16 7:25 ` [Buildroot] [PATCH v5 1/4] arch: add support for Andes 32-bit(nds32) Nylon Chen
2019-04-17 7:49 ` Thomas Petazzoni
2019-04-16 7:25 ` [Buildroot] [PATCH v5 2/4] configs/andes_nds32_ae3xx: new defconfig Nylon Chen
2019-04-17 7:53 ` Thomas Petazzoni
2019-04-16 7:25 ` [Buildroot] [PATCH v5 3/4] toolchain-external-andes-nds32: new package Nylon Chen
2019-04-17 7:52 ` Thomas Petazzoni
2019-04-16 7:25 ` [Buildroot] [PATCH v5 4/4] support/config-fragments/autobuild: test the Andes nds32 toolchain Nylon Chen
2019-04-17 7:53 ` Thomas Petazzoni
2019-04-17 19:22 ` Thomas Petazzoni [this message]
2019-04-18 8:39 ` [Buildroot] [PATCH v5 0/4] Add prebuilt nds32 toolchain, ae3xx board and autobuild configs support Nylon Chen
2019-04-18 9:00 ` Thomas Petazzoni
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=20190417212209.09ef3182@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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