From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] libnspr: Add dependency on !BR2_xtensa
Date: Wed, 27 Nov 2013 09:27:20 +0100 [thread overview]
Message-ID: <20131127092720.77f97fd0@skate> (raw)
In-Reply-To: <d1411c9410eaa1ebe9389cb5c20f4209b96a041f.1385530164.git.baruch@tkos.co.il>
Dear Baruch Siach,
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 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.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-11-27 8:27 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 [this message]
2013-11-27 9:02 ` Baruch Siach
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=20131127092720.77f97fd0@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