From: Nylon Chen <nylon7@andestech.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 3/3] upport/config-fragments/autobuild: test the Andes nds32 toolchain
Date: Fri, 22 Mar 2019 16:45:11 +0800 [thread overview]
Message-ID: <20190322084511.GB28644@app09> (raw)
In-Reply-To: <20190321111210.GA2660@scaer>
Yann, Thomas, All,
On Thu, Mar 21, 2019 at 12:12:10PM +0100, Yann E. MORIN wrote:
> Nylon, Thomas, All,
>
> On 2019-03-21 08:51 +0100, Thomas Petazzoni spake thusly:
> > On Thu, 21 Mar 2019 10:51:03 +0800
> > Nylon Chen <nylon7@andestech.com> wrote:
> >
> > > > > diff --git a/support/config-fragments/autobuild/br-andes-nds32.config b/support/config-fragments/autobuild/br-andes-nds32.config
> > > > > new file mode 100644
> > > > > index 0000000000..cd093a20f9
> > > > > --- /dev/null
> > > > > +++ b/support/config-fragments/autobuild/br-andes-nds32.config
> > > > > @@ -0,0 +1,9 @@
> > > > > +BR2_nds32=y
> > > > > +BR2_TOOLCHAIN_EXTERNAL=y
> > > > > +BR2_TOOLCHAIN_EXTERNAL_CUSTOM=y
> > > > > +BR2_TOOLCHAIN_EXTERNAL_DOWNLOAD=y
> > > > > +BR2_TOOLCHAIN_EXTERNAL_URL="https://github.com/vincentzwc/prebuilt-nds32-toolchain/releases/download/20180521/nds32le-linux-glibc-v3-upstream.tar.gz"
> > > I think I misunderstood the meaning of Thomas Petazzo.
> > >
> > > I thought that as long as the pre-build remote toolcahin is given.(So I used our own pre-build remote toolchain)
> > >
> > > It may take a few more days, we will contribute glibc back to upstream, and then we can compile it internally using buildroot.
> >
> > It is perfectly fine to use a pre-built toolchain, I think what Yann
> > explained is that since the source code of gcc/binutils/glibc/linux is
> > available, it makes sense to *also* support building the toolchain with
> > Buildroot.
>
> Exactly, yes.
>
> But that can come later, in a followup series.
>
> Regards,
> Yann E. MORIN.
>
In order to get rid of rework.
I prefer to send glibc to upstream and then come to this patch.
> > Also, it is not mandatory for the glibc support to be in upstream
> > glibc. We support architectures for which the gcc, binutils or libc
> > support is not yet fully upstreamed. For example, for RISC-V 32-bit,
> > we're using a non-upstream glibc.
> >
> > Best regards,
> >
> > Thomas
> > --
> > Thomas Petazzoni, CTO, Bootlin
> > Embedded Linux and Kernel engineering
> > https://bootlin.com
>
> --
> .-----------------.--------------------.------------------.--------------------.
> | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
> | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
> | +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
> | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
> '------------------------------^-------^------------------^--------------------'
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
prev parent reply other threads:[~2019-03-22 8:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-07 2:11 [Buildroot] [PATCH v2 0/3] Add prebuilt nds32 toolchain, ae3xx board and autobuild configs support Nylon Chen
2019-03-07 2:11 ` [Buildroot] [PATCH v3 1/3] arch: add support for Andes 32-bit(nds32) Nylon Chen
2019-03-14 22:22 ` Yann E. MORIN
2019-03-21 2:36 ` Nylon Chen
2019-03-21 11:18 ` Yann E. MORIN
2019-03-22 8:39 ` Nylon Chen
2019-03-22 11:40 ` Yann E. MORIN
2019-03-07 2:11 ` [Buildroot] [PATCH v3 2/3] configs/andes_nds32_ae3xx: new defconfig Nylon Chen
2019-03-14 22:31 ` Yann E. MORIN
2019-03-07 2:11 ` [Buildroot] [PATCH v3 3/3] upport/config-fragments/autobuild: test the Andes nds32 toolchain Nylon Chen
2019-03-14 22:42 ` Yann E. MORIN
2019-03-21 2:51 ` Nylon Chen
2019-03-21 7:51 ` Thomas Petazzoni
2019-03-21 11:12 ` Yann E. MORIN
2019-03-22 8:45 ` Nylon Chen [this message]
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=20190322084511.GB28644@app09 \
--to=nylon7@andestech.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