From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Can we update NodeJS package to 0.12.*
Date: Mon, 13 Apr 2015 21:19:49 +0200 [thread overview]
Message-ID: <20150413211949.34856da8@free-electrons.com> (raw)
In-Reply-To: <B9FA34E87D998B44A9DFD1535DEAC39C4870891C@BBYEXM01.pmc-sierra.internal>
Dear George Chen,
On Mon, 13 Apr 2015 16:05:59 +0000, George Chen wrote:
> Current 2015.03 buildroot contains NodeJS 0.10.36
>
> Is there a way to customly configure the package to 0.11.* or 0.12.*?
Well, just adjust nodejs.mk. And then, send a patch to the Buildroot
mailing list, so that we can integrate this update in the official
Buildroot.
> The reason for the newer NodeJS version is that IPv6 is not fully supported in 0.10.*
>
> I tried to change Config.mk
I guess you meant nodejs.mk here.
>
> - NODEJS_VERSION = 0.10.36
> + NODEJS_VERSION = 0.12.0
>
> However, I am getting the make error:
>
> ../deps/v8/src/base/atomicops_internals_arm_gcc.h:258:4: error: #error "Your CPU's ARM architecture is not supported yet"
For which ARM target are you trying to build?
> Is my only option to add NodeJS 0.12.0 as a custom package?
Why would you want to add another package? Just improve the existing
nodejs package.
Best regards,
Thomas Petazzoni
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-04-13 19:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-13 16:05 [Buildroot] Can we update NodeJS package to 0.12.* George Chen
2015-04-13 19:19 ` Thomas Petazzoni [this message]
2015-04-15 8:02 ` Jörg Krause
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=20150413211949.34856da8@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 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.