From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3] package/nodejs: bump version to 7.7.1
Date: Sun, 12 Mar 2017 23:36:44 +0100 [thread overview]
Message-ID: <20170312233644.1006d0ef@free-electrons.com> (raw)
In-Reply-To: <1488671310-27378-2-git-send-email-martin@barkynet.com>
Hello,
On Sat, 4 Mar 2017 23:48:29 +0000, Martin Bark wrote:
> See https://nodejs.org/en/blog/release/v7.7.1/
>
> Signed-off-by: Martin Bark <martin@barkynet.com>
This patch breaks the build with nodejs 0.10, because nodejs 0.10 does
not have this mkpeephole binary. Therefore, your PATCH 3/3 should be
before PATCH 2/3.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-03-12 22:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-04 23:48 [Buildroot] [PATCH 1/3] DEVELOPERS: add Martin Bark for package/nodejs Martin Bark
2017-03-04 23:48 ` [Buildroot] [PATCH 2/3] package/nodejs: bump version to 7.7.1 Martin Bark
2017-03-12 22:36 ` Thomas Petazzoni [this message]
2017-03-14 9:11 ` Martin Bark
2017-03-04 23:48 ` [Buildroot] [PATCH 3/3] package/nodejs: remove 0.10.x support Martin Bark
2017-03-05 22:40 ` Arnout Vandecappelle
2017-03-06 10:08 ` Martin Bark
2017-03-06 12:23 ` Arnout Vandecappelle
2017-03-06 21:13 ` Yann E. MORIN
2017-03-07 15:32 ` Peter Korsgaard
2017-03-05 11:13 ` [Buildroot] [PATCH 1/3] DEVELOPERS: add Martin Bark for package/nodejs Thomas Petazzoni
2017-03-05 15:35 ` Martin Bark
2017-03-05 15:49 ` Yann E. MORIN
2017-03-05 17:51 ` Thomas Petazzoni
2017-03-05 20:28 ` Martin Bark
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=20170312233644.1006d0ef@free-electrons.com \
--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