All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/5] package/nodejs: bump version to 5.3.0
Date: Fri, 18 Dec 2015 22:09:29 +0100	[thread overview]
Message-ID: <20151218210929.GC27578@free.fr> (raw)
In-Reply-To: <1450394426-3349-1-git-send-email-martin@barkynet.com>

Martin, All,

On 2015-12-17 23:20 +0000, Martin Bark spake thusly:
> Replace 4.2.3 with 5.3.0.  5.3.0 is the current Stable release. See
> https://nodejs.org/en/blog/release/v5.3.0 for details on the release.
> 
> Copied 4.2.3 patched to 5.3.0 with the following exceptions:
>  - Removed 0004-fix-arm-vfpv2.patch, committed upstream and included in
>    5.3.0.  See https://github.com/nodejs/node/commit/84dea1bd0c
>  - Added 0004-Fix-va_list-not-declared.patch, fix for a new bug.  This
>    has already been fixed upstream but is not in 5.3.0
> 
> Signed-off-by: Martin Bark <martin@barkynet.com>
[--SNIP--]
> diff --git a/package/nodejs/Config.in b/package/nodejs/Config.in
> index b0f4f2b..769710c 100644
> --- a/package/nodejs/Config.in
> +++ b/package/nodejs/Config.in
> @@ -48,14 +48,16 @@ config BR2_BR2_PACKAGE_NODEJS_0_12_X
>  	bool "v0.12.9"
>  	depends on BR2_PACKAGE_NODEJS_V8_ARCH_SUPPORTS
>  
> -config BR2_BR2_PACKAGE_NODEJS_4_X
> -	bool "v4.2.3"
> +config BR2_PACKAGE_NODEJS_5_X
> +	bool "v5.3.0"
>  	depends on BR2_PACKAGE_NODEJS_V8_ARCH_SUPPORTS
>  	depends on BR2_TOOLCHAIN_GCC_AT_LEAST_4_8
> +	depends on BR2_USE_WCHAR
> 
> -comment "v4.2.3 needs a toolchain w/ gcc >= 4.8"
> +comment "v5.3.0 needs a toolchain w/ gcc >= 4.8, wchar"
>  	depends on BR2_PACKAGE_NODEJS_V8_ARCH_SUPPORTS
>  	depends on !BR2_TOOLCHAIN_GCC_AT_LEAST_4_8
> +	depends on !BR2_USE_WCHAR

Wrong, this should be:

    depends on !BR2_TOOLCHAIN_GCC_AT_LEAST_4_8 || !BR2_USE_WCHAR

Otherwise OK for me...

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  parent reply	other threads:[~2015-12-18 21:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-17 23:20 [Buildroot] [PATCH v2 1/5] package/nodejs: bump version to 5.3.0 Martin Bark
2015-12-17 23:20 ` [Buildroot] [PATCH v2 2/5] package/nodejs: removed version 0.12.9 Martin Bark
2015-12-17 23:20 ` [Buildroot] [PATCH v2 3/5] package/nodejs: correct 0.10.x option name Martin Bark
2015-12-18 21:12   ` Yann E. MORIN
2015-12-18 22:47     ` Arnout Vandecappelle
2015-12-20 17:03       ` Martin Bark
2015-12-17 23:20 ` [Buildroot] [PATCH v2 4/5] package/nodejs: fix support for uClibc-ng Martin Bark
2015-12-18 21:15   ` Yann E. MORIN
2015-12-20 16:58     ` Martin Bark
2015-12-17 23:20 ` [Buildroot] [PATCH v2 5/5] package/libuv: " Martin Bark
2015-12-18 21:09 ` Yann E. MORIN [this message]
2015-12-18 21:35 ` [Buildroot] [PATCH v2 1/5] package/nodejs: bump version to 5.3.0 Yann E. MORIN
2015-12-20 16:59   ` 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=20151218210929.GC27578@free.fr \
    --to=yann.morin.1998@free.fr \
    --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.