From: Chris Zankel <chris@zankel.net>
To: buildroot@busybox.net
Subject: [Buildroot] Xtensa support ?
Date: Tue, 18 Feb 2014 16:24:20 -0800 [thread overview]
Message-ID: <5303F9B4.60102@zankel.net> (raw)
In-Reply-To: <20140218222215.12b84764@skate>
+CC: Max
Hi Thomas,
Unfortunately, I have been really busy with another project and won't
have much time to look into it for another week or so. Max has been
working on Xtensa a lot, so maybe he can step in?
If the autobuilder supports multiple recipients, it would be great if
you could still keep me in that list, though.
Thanks,
-Chris
On 2/18/14, 1:22 PM, Thomas Petazzoni wrote:
> Baruch,
>
> On Sat, 15 Feb 2014 23:31:24 +0200, Baruch Siach wrote:
>
>> On Fri, Feb 14, 2014 at 10:12:41AM +0100, Thomas Petazzoni wrote:
>>>> xtensa | kmod-16 | NOK | http://autobuild.buildroot.net/results/ba205bcbb6898bee78f610883f3837930eda262c/
>>> Binutils internal error. Baruch ?
>> Xtensa Toolchain issues are out of scope for me at the moment I'm afraid.
>> Sorry.
> Argh, too bad. You have been very active in recent times in improving
> the Xtensa support, and this was really nice.
>
> The daily Xtensa autobuilder failures are sent to chris at zankel.net, but
> Chris doesn't seem to be very active in fixing the issues. Chris, are
> you still interested in Buildroot Xtensa support?
>
> Are there other Xtensa users on the list? If so, please speak up, we
> need you to continue improving the Xtensa Buildroot support.
>
> Thanks,
>
> Thomas
next prev parent reply other threads:[~2014-02-19 0:24 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-14 7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-02-13 Thomas Petazzoni
2014-02-14 9:12 ` [Buildroot] Analysis of build failures Thomas Petazzoni
2014-02-14 10:23 ` Anton Kolesov
2014-02-14 14:13 ` Thomas Petazzoni
2014-02-14 14:42 ` Peter Korsgaard
2014-02-14 15:19 ` Thomas Petazzoni
2014-02-14 17:05 ` Anton Kolesov
2014-02-14 17:42 ` Thomas Petazzoni
2014-02-14 11:29 ` Peter Korsgaard
2014-02-14 13:15 ` Ezequiel García
2014-02-15 7:27 ` Frank Bergmann
2014-02-15 17:29 ` Frank Bergmann
2014-02-15 18:52 ` [Buildroot] [PATCH 1/1] e2fsprogs: fix missing fallocate64() on nios2 Frank Bergmann
2014-02-18 21:19 ` Thomas Petazzoni
2014-02-18 23:13 ` Frank Bergmann
2014-02-20 20:52 ` Frank Bergmann
2014-02-27 13:35 ` Peter Korsgaard
2014-02-15 21:31 ` [Buildroot] Analysis of build failures Baruch Siach
2014-02-18 21:22 ` [Buildroot] Xtensa support ? Thomas Petazzoni
2014-02-19 0:24 ` Chris Zankel [this message]
2014-02-19 8:04 ` Thomas Petazzoni
[not found] ` <CAMo8Bf+gfdgfV+XFows8HmppvXdL=VWXGG_givbUNerep0zeHg@mail.gmail.com>
2014-02-19 13:19 ` Thomas Petazzoni
2014-02-19 5:26 ` Jonathan Ben Avraham
2014-02-19 8:05 ` Thomas Petazzoni
2014-02-19 8:16 ` Jonathan Ben Avraham
2014-02-19 8:22 ` Thomas Petazzoni
2014-02-16 0:00 ` [Buildroot] Analysis of build failures Romain Naour
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=5303F9B4.60102@zankel.net \
--to=chris@zankel.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.