From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] swig: enable support for Node.js >= 7.x
Date: Sun, 8 Oct 2017 15:52:52 +0200 [thread overview]
Message-ID: <20171008155252.5f08f349@windsurf> (raw)
In-Reply-To: <1506686356-4509-1-git-send-email-yegorslists@googlemail.com>
Hello,
On Fri, 29 Sep 2017 13:59:16 +0200, yegorslists at googlemail.com wrote:
> From: Yegor Yefremov <yegorslists@googlemail.com>
>
> Recent Node.js versions have removed some depreciated API calls,
> that swig still relies on. Patches taken from this PR [1] fix
> this issue.
>
> [1] https://github.com/swig/swig/pull/968
>
> Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
> ---
> .../0001-Add-Node-7.x-aka-V8-5.2-support.patch | 328 +++++++++++++++++++++
> ...e-warnings-on-Node-6.x-aka-V8-5.0-and-5.1.patch | 222 ++++++++++++++
Applied to master.
To be honest, I hesitated a bit, those patches are a bit big and
invasive, and have not been merged upstream yet. I've merged anyway,
but we might need to drop them at the next swig bump if they haven't
been merged upstream.
Also, how do you in practice build swig with nodejs support? There is
no dependency between host-swig and host-nodejs.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-10-08 13:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-29 11:59 [Buildroot] [PATCH] swig: enable support for Node.js >= 7.x yegorslists at googlemail.com
2017-10-08 13:52 ` Thomas Petazzoni [this message]
2017-10-08 17:16 ` Yegor Yefremov
2017-10-08 18:50 ` 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=20171008155252.5f08f349@windsurf \
--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