From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/gcc: fix xtensa uclinux code generation
Date: Thu, 8 Nov 2018 20:51:27 +0100 [thread overview]
Message-ID: <20181108205127.76b81a8a@windsurf> (raw)
In-Reply-To: <CAMo8Bf+=OZWK2m8=i9e99UGBBDY5h9k+SaNB54h_ag9MiaLUOg@mail.gmail.com>
Hello,
On Thu, 8 Nov 2018 10:28:01 -0800, Max Filippov wrote:
> On Thu, Nov 8, 2018 at 2:35 AM Thomas Petazzoni
> <thomas.petazzoni@bootlin.com> wrote:
> > Do we actually support xtensa-uclinux (i.e noMMU Xtensa with BFLT) in
> > the context of Buildroot ?
>
> We do. There's even configs/qemu_xtensa_lx60_nommu_defconfig
> with an example config that builds working image.
Ah, forgot about this! Nice. Perhaps we should be testing this in the
autobuilders ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-11-08 19:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 21:20 [Buildroot] [PATCH] package/gcc: fix xtensa uclinux code generation Max Filippov
2018-11-08 10:35 ` Thomas Petazzoni
2018-11-08 18:28 ` Max Filippov
2018-11-08 19:51 ` Thomas Petazzoni [this message]
2018-11-08 20:17 ` Max Filippov
2018-11-09 14:51 ` Peter Korsgaard
2018-11-25 21:31 ` Peter Korsgaard
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=20181108205127.76b81a8a@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