From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] uclibc: add a special Xtensa version
Date: Sun, 22 Dec 2013 19:39:44 +0100 [thread overview]
Message-ID: <20131222193944.3e1abd5c@skate> (raw)
In-Reply-To: <20131222183218.GA4180@tarshish>
Dear Baruch Siach,
On Sun, 22 Dec 2013 20:32:18 +0200, Baruch Siach wrote:
> Thanks of looking into this. Commit 9591091f1 is quite old, however, and is
> missing a few important xtensa fixes like a20d9fe539 and caee562063. Since
> this breakage is new, It's probably related to the commits pushed to public
> git repo in the last few days. Specifically I suspect 2a021ae81c3 (buildsys:
> update unifdef), but I didn't look too deeply into it.
Aah, I looked at http://git.uclibc.org/uClibc/log/ where the last
commit is 9591091f1. There is (again) a cache problem, because this is
indeed not the latest commit, as can be seen at
http://git.uclibc.org/uClibc/log/?h=master.
> Can you verify that 3a3ad3dfc1 as default uClibc version for xtensa doesn't
> break the builds?
I'll try that.
> BTW, I'd also appreciate your response on
> http://article.gmane.org/gmane.comp.lib.uclibc.buildroot/72570.
Aaah, yes, I need to have a look into this one. Thanks for the reminder.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-12-22 18:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-22 17:40 [Buildroot] [PATCH] uclibc: add a special Xtensa version Thomas Petazzoni
2013-12-22 18:32 ` Baruch Siach
2013-12-22 18:39 ` Thomas Petazzoni [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-12-29 11:26 Baruch Siach
2013-12-29 12:33 ` 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=20131222193944.3e1abd5c@skate \
--to=thomas.petazzoni@free-electrons.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