From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] libnss: fix build without int128
Date: Mon, 4 Jun 2018 21:50:02 +0200 [thread overview]
Message-ID: <20180604215002.7ce9094c@windsurf> (raw)
In-Reply-To: <20180604170926.372-1-fontaine.fabrice@gmail.com>
Hello,
On Mon, 4 Jun 2018 19:09:26 +0200, Fabrice Fontaine wrote:
> Patch retrieved from upstream, more info here:
> https://bugzilla.mozilla.org/show_bug.cgi?format=default&id=1459739
>
> Fixes:
> - http://autobuild.buildroot.net/results/093113829d7ce19d578a920e76caa10822774139
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> ...r-c-when-not-building-with-int128-support.patch | 143 +++++++++++++++++++++
> 1 file changed, 143 insertions(+)
> create mode 100644 package/libnss/0003-Bug-1432455-Build-FStar-c-when-not-building-with-int128-support.patch
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-06-04 19:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-04 17:09 [Buildroot] [PATCH 1/1] libnss: fix build without int128 Fabrice Fontaine
2018-06-04 19:50 ` Thomas Petazzoni [this message]
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=20180604215002.7ce9094c@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox