From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] libnspr: Add dependency on !BR2_xtensa
Date: Wed, 27 Nov 2013 11:02:15 +0200 [thread overview]
Message-ID: <20131127090215.GX32436@tarshish> (raw)
In-Reply-To: <20131127092720.77f97fd0@skate>
Hi Thomas,
On Wed, Nov 27, 2013 at 09:27:20AM +0100, Thomas Petazzoni wrote:
> On Wed, 27 Nov 2013 07:29:24 +0200, Baruch Siach wrote:
> > From: Chris Zankel <chris@zankel.net>
> >
> > Xtensa is not yet supported in libnspr. Also add dependencies to
> > libnss, which requires libnspr, and ecryptfs-utils, which requires
> > libnss.
> >
> > Fixes
> > http://autobuild.buildroot.net/results/14b/14ba6426edbffa100de924aa69157b3f59368ff2/
> >
> > [baruch: fix summary, add autobuild referench, add comment dependency]
> >
> > Signed-off-by: Chris Zankel <chris@zankel.net>
> > Signed-off-by: Baruch Siach <baruch@tkos.co.il>
>
> Thanks! However, I wonder if it's not actually easier to include a
> patch to libnspr to add Xtensa support. See
> http://patchwork.ozlabs.org/patch/291080/ for a patch that adds NIOS2
> support, for example.
That would obviously be better, but I can't properly test a patch adding
libnspr xtensa support at the moment. Note that xtensa has BE and LE variants,
so it's a little more involved that the nios patch.
> That being said, I'm fine with having libnspr disabled on Xtensa, as I
> don't believe that many people will care about
> libnspr/libnss/ecryptfs-utils.
It seems like blackfin needs the same treatment
(http://autobuild.buildroot.net/results/dd353703ed94cec48cd126d80cd2f1b039811be4/).
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2013-11-27 9:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-27 5:29 [Buildroot] [PATCH v2] libnspr: Add dependency on !BR2_xtensa Baruch Siach
2013-11-27 8:27 ` Thomas Petazzoni
2013-11-27 9:02 ` Baruch Siach [this message]
2013-11-27 9:08 ` 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=20131127090215.GX32436@tarshish \
--to=baruch@tkos.co.il \
--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