Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] package/nodejs: bump 0.10.x branch to version 0.10.41
Date: Sat, 12 Dec 2015 18:32:35 +0100	[thread overview]
Message-ID: <20151212183235.09bb8139@free-electrons.com> (raw)
In-Reply-To: <1449609500-10071-1-git-send-email-joerg.krause@embedded.rocks>

Dear J?rg Krause,

On Tue,  8 Dec 2015 22:18:18 +0100, J?rg Krause wrote:
> Also remove a patch applied upstream.
> 
> Signed-off-by: J?rg Krause <joerg.krause@embedded.rocks>
> ---
>  ...4-fix-build-error-without-OpenSSL-support.patch | 54 ----------------------
>  .../0001-remove-python-bz2-dependency.patch        |  0
>  .../0002-gyp-force-link-command-to-use-CXX.patch   |  0
>  .../0003-use-python-variable.patch                 |  0
>  .../0004-fix-musl-USE-MISC-build-issue.patch}      |  0
>  package/nodejs/Config.in                           |  4 +-
>  package/nodejs/nodejs.hash                         |  4 +-
>  7 files changed, 4 insertions(+), 58 deletions(-)
>  delete mode 100644 package/nodejs/0.10.40/0004-fix-build-error-without-OpenSSL-support.patch
>  rename package/nodejs/{0.10.40 => 0.10.41}/0001-remove-python-bz2-dependency.patch (100%)
>  rename package/nodejs/{0.10.40 => 0.10.41}/0002-gyp-force-link-command-to-use-CXX.patch (100%)
>  rename package/nodejs/{0.10.40 => 0.10.41}/0003-use-python-variable.patch (100%)
>  rename package/nodejs/{0.10.40/0005-fix-musl-USE-MISC-build-issue.patch => 0.10.41/0004-fix-musl-USE-MISC-build-issue.patch} (100%)

I've applied all three patches. However, there is a problem: if you
select a Cortex-A9 ARM processor, only the 0.10 version is visible, the
0.12 and 4.x versions are not visible. This is because for Cortex-A9,
BR2_ARM_CPU_HAS_VFPV2 is not true. This is something that should be
fixed at some point.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  parent reply	other threads:[~2015-12-12 17:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-08 21:18 [Buildroot] [PATCH 1/3] package/nodejs: bump 0.10.x branch to version 0.10.41 Jörg Krause
2015-12-08 21:18 ` [Buildroot] [PATCH 2/3] package/nodejs: bump 0.12.x branch to version 0.12.9 Jörg Krause
2015-12-08 21:18 ` [Buildroot] [PATCH 3/3] package/nodejs: bump 4.x branch to version 4.2.3 Jörg Krause
2015-12-12 17:32 ` Thomas Petazzoni [this message]
2015-12-13 20:42   ` [Buildroot] [PATCH 1/3] package/nodejs: bump 0.10.x branch to version 0.10.41 Arnout Vandecappelle
2015-12-13 21:18     ` 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=20151212183235.09bb8139@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