From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/libnspr: bump to version 4.25, add xtensa support
Date: Tue, 4 Feb 2020 09:33:51 +0100 [thread overview]
Message-ID: <20200204093351.6393df15@windsurf> (raw)
In-Reply-To: <ba2c8b6f-1ccb-b077-a789-cdbe2b987915@mind.be>
On Tue, 4 Feb 2020 09:25:46 +0100
Arnout Vandecappelle <arnout@mind.be> wrote:
> > I don't feel very strongly about it, but I'm wondering if it doesn't
> > make sense to keep BR2_PACKAGE_LIBNSPR_ARCH_SUPPORT. There is some
> > architecture-specific code in libnpsr, so every time we add a new CPU
> > architecture, we would have to poentially re-add this hidden option.
>
> For what it's worth, I agree with doing that. We don't want to end up in the
> libffi situation...
Agreed. Though I don't think libnspr will ever be in the situation of
libffi, with zillions of reverse dependencies.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-02-04 8:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-01 8:47 [Buildroot] [PATCH 1/2] package/libnspr: bump to version 4.25, add xtensa support Bernd Kuhls
2020-02-01 8:47 ` [Buildroot] [PATCH 2/2] package/libnss: bump version to 3.49.2 Bernd Kuhls
2020-02-01 12:30 ` Giulio Benetti
2020-02-01 9:24 ` [Buildroot] [PATCH 1/2] package/libnspr: bump to version 4.25, add xtensa support Thomas Petazzoni
2020-02-04 8:25 ` Arnout Vandecappelle
2020-02-04 8:33 ` Thomas Petazzoni [this message]
2020-02-04 9:52 ` Giulio Benetti
2020-02-01 12:35 ` Giulio Benetti
2020-02-01 13:21 ` Bernd Kuhls
2020-02-01 13:24 ` Giulio Benetti
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=20200204093351.6393df15@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 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.