2013-06-05 23:53:30 +00:00
|
|
|
################################################################################
|
2013-03-07 15:31:16 +00:00
|
|
|
#
|
|
|
|
|
# nodejs
|
|
|
|
|
#
|
2013-06-05 23:53:30 +00:00
|
|
|
################################################################################
|
2013-03-07 15:31:16 +00:00
|
|
|
|
package/nodejs: security bump to version v10.16.3
Fixes the following security vulnerabilities:
- CVE-2019-9511 "Data Dribble": The attacker requests a large amount of data
from a specified resource over multiple streams. They manipulate window
size and stream priority to force the server to queue the data in 1-byte
chunks. Depending on how efficiently this data is queued, this can
consume excess CPU, memory, or both, potentially leading to a denial of
service.
- CVE-2019-9512 "Ping Flood": The attacker sends continual pings to an
HTTP/2 peer, causing the peer to build an internal queue of responses.
Depending on how efficiently this data is queued, this can consume excess
CPU, memory, or both, potentially leading to a denial of service.
- CVE-2019-9513 "Resource Loop": The attacker creates multiple request
streams and continually shuffles the priority of the streams in a way that
causes substantial churn to the priority tree. This can consume excess
CPU, potentially leading to a denial of service.
- CVE-2019-9514 "Reset Flood": The attacker opens a number of streams and
sends an invalid request over each stream that should solicit a stream of
RST_STREAM frames from the peer. Depending on how the peer queues the
RST_STREAM frames, this can consume excess memory, CPU, or both,
potentially leading to a denial of service.
- CVE-2019-9515 "Settings Flood": The attacker sends a stream of SETTINGS
frames to the peer. Since the RFC requires that the peer reply with one
acknowledgement per SETTINGS frame, an empty SETTINGS frame is almost
equivalent in behavior to a ping. Depending on how efficiently this data
is queued, this can consume excess CPU, memory, or both, potentially
leading to a denial of service.
- CVE-2019-9516 "0-Length Headers Leak": The attacker sends a stream of
headers with a 0-length header name and 0-length header value, optionally
Huffman encoded into 1-byte or greater headers. Some implementations
allocate memory for these headers and keep the allocation alive until the
session dies. This can consume excess memory, potentially leading to a
denial of service.
- CVE-2019-9517 "Internal Data Buffering": The attacker opens the HTTP/2
window so the peer can send without constraint; however, they leave the
TCP window closed so the peer cannot actually write (many of) the bytes on
the wire. The attacker then sends a stream of requests for a large
response object. Depending on how the servers queue the responses, this
can consume excess memory, CPU, or both, potentially leading to a denial
of service.
- CVE-2019-9518 "Empty Frames Flood": The attacker sends a stream of frames
with an empty payload and without the end-of-stream flag. These frames
can be DATA, HEADERS, CONTINUATION and/or PUSH_PROMISE. The peer spends
time processing each frame disproportionate to attack bandwidth. This can
consume excess CPU, potentially leading to a denial of service.
(Discovered by Piotr Sikora of Google)
Notice that this version bump requires nghttp2 1.39.2. It also includes an
(unconditional) embedded copy of brotli.
Update the license hash because of copyright year changes and the addition
of the MIT-style license text for large_pages and brotli.
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-09-12 21:43:54 +02:00
|
|
|
NODEJS_VERSION = 10.16.3
|
2015-10-19 23:59:08 +02:00
|
|
|
NODEJS_SOURCE = node-v$(NODEJS_VERSION).tar.xz
|
2013-03-07 15:31:16 +00:00
|
|
|
NODEJS_SITE = http://nodejs.org/dist/v$(NODEJS_VERSION)
|
2017-07-18 12:45:42 +01:00
|
|
|
NODEJS_DEPENDENCIES = host-python host-nodejs c-ares \
|
2019-03-14 13:38:13 +00:00
|
|
|
libhttpparser libuv zlib nghttp2 \
|
2014-10-25 08:20:44 +02:00
|
|
|
$(call qstrip,$(BR2_PACKAGE_NODEJS_MODULES_ADDITIONAL_DEPS))
|
2019-03-14 13:38:11 +00:00
|
|
|
HOST_NODEJS_DEPENDENCIES = host-libopenssl host-python host-zlib host-patchelf
|
2013-03-07 15:31:16 +00:00
|
|
|
NODEJS_LICENSE = MIT (core code); MIT, Apache and BSD family licenses (Bundled components)
|
|
|
|
|
NODEJS_LICENSE_FILES = LICENSE
|
|
|
|
|
|
2016-06-03 20:15:43 +01:00
|
|
|
NODEJS_CONF_OPTS = \
|
|
|
|
|
--without-snapshot \
|
|
|
|
|
--shared-zlib \
|
2017-07-18 12:45:41 +01:00
|
|
|
--shared-cares \
|
2017-07-18 12:45:42 +01:00
|
|
|
--shared-http-parser \
|
2017-07-18 12:45:43 +01:00
|
|
|
--shared-libuv \
|
2019-03-14 13:38:13 +00:00
|
|
|
--shared-nghttp2 \
|
2016-06-03 20:15:43 +01:00
|
|
|
--without-dtrace \
|
|
|
|
|
--without-etw \
|
|
|
|
|
--dest-os=linux
|
|
|
|
|
|
2013-03-07 15:31:16 +00:00
|
|
|
ifeq ($(BR2_PACKAGE_OPENSSL),y)
|
2015-03-31 09:21:57 +02:00
|
|
|
NODEJS_DEPENDENCIES += openssl
|
2016-06-03 20:15:45 +01:00
|
|
|
NODEJS_CONF_OPTS += --shared-openssl
|
|
|
|
|
else
|
|
|
|
|
NODEJS_CONF_OPTS += --without-ssl
|
2013-03-07 15:31:16 +00:00
|
|
|
endif
|
|
|
|
|
|
2016-06-03 11:41:16 +01:00
|
|
|
ifeq ($(BR2_PACKAGE_ICU),y)
|
|
|
|
|
NODEJS_DEPENDENCIES += icu
|
2016-06-03 20:15:44 +01:00
|
|
|
NODEJS_CONF_OPTS += --with-intl=system-icu
|
|
|
|
|
else
|
|
|
|
|
NODEJS_CONF_OPTS += --with-intl=none
|
2016-06-03 11:41:16 +01:00
|
|
|
endif
|
|
|
|
|
|
2016-06-03 20:15:46 +01:00
|
|
|
ifneq ($(BR2_PACKAGE_NODEJS_NPM),y)
|
|
|
|
|
NODEJS_CONF_OPTS += --without-npm
|
|
|
|
|
endif
|
|
|
|
|
|
2014-04-15 00:09:48 +02:00
|
|
|
# nodejs build system is based on python, but only support python-2.6 or
|
|
|
|
|
# python-2.7. So, we have to enforce PYTHON interpreter to be python2.
|
2013-03-07 15:31:16 +00:00
|
|
|
define HOST_NODEJS_CONFIGURE_CMDS
|
2016-03-03 22:29:27 +00:00
|
|
|
# The build system directly calls python. Work around this by forcing python2
|
|
|
|
|
# into PATH. See https://github.com/nodejs/node/issues/2735
|
|
|
|
|
mkdir -p $(@D)/bin
|
2017-07-05 13:14:19 +02:00
|
|
|
ln -sf $(HOST_DIR)/bin/python2 $(@D)/bin/python
|
2016-03-03 22:29:27 +00:00
|
|
|
|
2013-03-07 15:31:16 +00:00
|
|
|
(cd $(@D); \
|
2014-04-15 00:09:47 +02:00
|
|
|
$(HOST_CONFIGURE_OPTS) \
|
2016-03-03 22:29:27 +00:00
|
|
|
PATH=$(@D)/bin:$(BR_PATH) \
|
2017-07-05 13:14:19 +02:00
|
|
|
PYTHON=$(HOST_DIR)/bin/python2 \
|
|
|
|
|
$(HOST_DIR)/bin/python2 ./configure \
|
2017-07-05 13:14:18 +02:00
|
|
|
--prefix=$(HOST_DIR) \
|
2013-03-07 15:31:16 +00:00
|
|
|
--without-snapshot \
|
|
|
|
|
--without-dtrace \
|
|
|
|
|
--without-etw \
|
2018-08-19 18:51:58 +02:00
|
|
|
--shared-openssl \
|
|
|
|
|
--shared-openssl-includes=$(HOST_DIR)/include/openssl \
|
|
|
|
|
--shared-openssl-libpath=$(HOST_DIR)/lib \
|
2014-08-15 19:20:03 +02:00
|
|
|
--shared-zlib \
|
2017-03-14 12:06:17 +00:00
|
|
|
--with-intl=none \
|
2013-03-07 15:31:16 +00:00
|
|
|
)
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define HOST_NODEJS_BUILD_CMDS
|
2017-07-05 13:14:19 +02:00
|
|
|
$(HOST_MAKE_ENV) PYTHON=$(HOST_DIR)/bin/python2 \
|
2014-09-06 19:00:54 +02:00
|
|
|
$(MAKE) -C $(@D) \
|
2016-03-03 22:29:27 +00:00
|
|
|
$(HOST_CONFIGURE_OPTS) \
|
2017-06-20 09:39:01 +01:00
|
|
|
NO_LOAD=cctest.target.mk \
|
2016-03-03 22:29:27 +00:00
|
|
|
PATH=$(@D)/bin:$(BR_PATH)
|
2019-03-14 13:38:11 +00:00
|
|
|
|
|
|
|
|
$(HOST_DIR)/bin/patchelf --set-rpath $(HOST_DIR)/lib $(@D)/out/Release/torque
|
2013-03-07 15:31:16 +00:00
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define HOST_NODEJS_INSTALL_CMDS
|
2017-07-05 13:14:19 +02:00
|
|
|
$(HOST_MAKE_ENV) PYTHON=$(HOST_DIR)/bin/python2 \
|
2014-09-06 19:00:54 +02:00
|
|
|
$(MAKE) -C $(@D) install \
|
2016-03-03 22:29:27 +00:00
|
|
|
$(HOST_CONFIGURE_OPTS) \
|
2017-06-20 09:39:01 +01:00
|
|
|
NO_LOAD=cctest.target.mk \
|
2016-03-03 22:29:27 +00:00
|
|
|
PATH=$(@D)/bin:$(BR_PATH)
|
2019-03-14 13:38:11 +00:00
|
|
|
|
|
|
|
|
$(INSTALL) -m755 -D $(@D)/out/Release/torque $(HOST_DIR)/bin/torque
|
2013-03-07 15:31:16 +00:00
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
ifeq ($(BR2_i386),y)
|
.mk files: bulk aligment and whitespace cleanup of assignments
The Buildroot coding style defines one space around make assignments and
does not align the assignment symbols.
This patch does a bulk fix of offending packages. The package
infrastructures (or more in general assignments to calculated variable
names, like $(2)_FOO) are not touched.
Alignment of line continuation characters (\) is kept as-is.
The sed command used to do this replacement is:
find * -name "*.mk" | xargs sed -i \
-e 's#^\([A-Z0-9a-z_]\+\)\s*\([?:+]\?=\)\s*$#\1 \2#'
-e 's#^\([A-Z0-9a-z_]\+\)\s*\([?:+]\?=\)\s*\([^\\]\+\)$#\1 \2 \3#'
-e 's#^\([A-Z0-9a-z_]\+\)\s*\([?:+]\?=\)\s*\([^\\ \t]\+\s*\\\)\s*$#\1 \2 \3#'
-e 's#^\([A-Z0-9a-z_]\+\)\s*\([?:+]\?=\)\(\s*\\\)#\1 \2\3#'
Brief explanation of this command:
^\([A-Z0-9a-z_]\+\) a regular variable at the beginning of the line
\([?:+]\?=\) any assignment character =, :=, ?=, +=
\([^\\]\+\) any string not containing a line continuation
\([^\\ \t]\+\s*\\\) string, optional whitespace, followed by a
line continuation character
\(\s*\\\) optional whitespace, followed by a line
continuation character
Hence, the first subexpression handles empty assignments, the second
handles regular assignments, the third handles regular assignments with
line continuation, and the fourth empty assignments with line
continuation.
This expression was tested on following test text: (initial tab not
included)
FOO = spaces before
FOO = spaces before and after
FOO = tab before
FOO = tab and spaces before
FOO = tab after
FOO = tab and spaces after
FOO = spaces and tab after
FOO = \
FOO = bar \
FOO = bar space \
FOO = \
GENIMAGE_DEPENDENCIES = host-pkgconf libconfuse
FOO += spaces before
FOO ?= spaces before and after
FOO :=
FOO =
FOO =
FOO =
FOO =
$(MAKE1) CROSS_COMPILE=$(TARGET_CROSS) -C
AT91BOOTSTRAP3_DEFCONFIG = \
AXEL_DISABLE_I18N=--i18n=0
After this bulk change, following manual fixups were done:
- fix line continuation alignment in cegui06 and spice (the sed
expression leaves the number of whitespace between the value and line
continuation character intact, but the whitespace before that could have
changed, causing misalignment.
- qt5base was reverted, as this package uses extensive alignment which
actually makes the code more readable.
Finally, the end result was manually reviewed.
Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
Cc: Yann E. Morin <yann.morin.1998@free.fr>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-10-07 09:06:03 +02:00
|
|
|
NODEJS_CPU = ia32
|
2013-03-07 15:31:16 +00:00
|
|
|
else ifeq ($(BR2_x86_64),y)
|
.mk files: bulk aligment and whitespace cleanup of assignments
The Buildroot coding style defines one space around make assignments and
does not align the assignment symbols.
This patch does a bulk fix of offending packages. The package
infrastructures (or more in general assignments to calculated variable
names, like $(2)_FOO) are not touched.
Alignment of line continuation characters (\) is kept as-is.
The sed command used to do this replacement is:
find * -name "*.mk" | xargs sed -i \
-e 's#^\([A-Z0-9a-z_]\+\)\s*\([?:+]\?=\)\s*$#\1 \2#'
-e 's#^\([A-Z0-9a-z_]\+\)\s*\([?:+]\?=\)\s*\([^\\]\+\)$#\1 \2 \3#'
-e 's#^\([A-Z0-9a-z_]\+\)\s*\([?:+]\?=\)\s*\([^\\ \t]\+\s*\\\)\s*$#\1 \2 \3#'
-e 's#^\([A-Z0-9a-z_]\+\)\s*\([?:+]\?=\)\(\s*\\\)#\1 \2\3#'
Brief explanation of this command:
^\([A-Z0-9a-z_]\+\) a regular variable at the beginning of the line
\([?:+]\?=\) any assignment character =, :=, ?=, +=
\([^\\]\+\) any string not containing a line continuation
\([^\\ \t]\+\s*\\\) string, optional whitespace, followed by a
line continuation character
\(\s*\\\) optional whitespace, followed by a line
continuation character
Hence, the first subexpression handles empty assignments, the second
handles regular assignments, the third handles regular assignments with
line continuation, and the fourth empty assignments with line
continuation.
This expression was tested on following test text: (initial tab not
included)
FOO = spaces before
FOO = spaces before and after
FOO = tab before
FOO = tab and spaces before
FOO = tab after
FOO = tab and spaces after
FOO = spaces and tab after
FOO = \
FOO = bar \
FOO = bar space \
FOO = \
GENIMAGE_DEPENDENCIES = host-pkgconf libconfuse
FOO += spaces before
FOO ?= spaces before and after
FOO :=
FOO =
FOO =
FOO =
FOO =
$(MAKE1) CROSS_COMPILE=$(TARGET_CROSS) -C
AT91BOOTSTRAP3_DEFCONFIG = \
AXEL_DISABLE_I18N=--i18n=0
After this bulk change, following manual fixups were done:
- fix line continuation alignment in cegui06 and spice (the sed
expression leaves the number of whitespace between the value and line
continuation character intact, but the whitespace before that could have
changed, causing misalignment.
- qt5base was reverted, as this package uses extensive alignment which
actually makes the code more readable.
Finally, the end result was manually reviewed.
Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
Cc: Yann E. Morin <yann.morin.1998@free.fr>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-10-07 09:06:03 +02:00
|
|
|
NODEJS_CPU = x64
|
2015-12-08 14:18:14 +00:00
|
|
|
else ifeq ($(BR2_mips),y)
|
|
|
|
|
NODEJS_CPU = mips
|
2013-12-17 02:16:15 +01:00
|
|
|
else ifeq ($(BR2_mipsel),y)
|
.mk files: bulk aligment and whitespace cleanup of assignments
The Buildroot coding style defines one space around make assignments and
does not align the assignment symbols.
This patch does a bulk fix of offending packages. The package
infrastructures (or more in general assignments to calculated variable
names, like $(2)_FOO) are not touched.
Alignment of line continuation characters (\) is kept as-is.
The sed command used to do this replacement is:
find * -name "*.mk" | xargs sed -i \
-e 's#^\([A-Z0-9a-z_]\+\)\s*\([?:+]\?=\)\s*$#\1 \2#'
-e 's#^\([A-Z0-9a-z_]\+\)\s*\([?:+]\?=\)\s*\([^\\]\+\)$#\1 \2 \3#'
-e 's#^\([A-Z0-9a-z_]\+\)\s*\([?:+]\?=\)\s*\([^\\ \t]\+\s*\\\)\s*$#\1 \2 \3#'
-e 's#^\([A-Z0-9a-z_]\+\)\s*\([?:+]\?=\)\(\s*\\\)#\1 \2\3#'
Brief explanation of this command:
^\([A-Z0-9a-z_]\+\) a regular variable at the beginning of the line
\([?:+]\?=\) any assignment character =, :=, ?=, +=
\([^\\]\+\) any string not containing a line continuation
\([^\\ \t]\+\s*\\\) string, optional whitespace, followed by a
line continuation character
\(\s*\\\) optional whitespace, followed by a line
continuation character
Hence, the first subexpression handles empty assignments, the second
handles regular assignments, the third handles regular assignments with
line continuation, and the fourth empty assignments with line
continuation.
This expression was tested on following test text: (initial tab not
included)
FOO = spaces before
FOO = spaces before and after
FOO = tab before
FOO = tab and spaces before
FOO = tab after
FOO = tab and spaces after
FOO = spaces and tab after
FOO = \
FOO = bar \
FOO = bar space \
FOO = \
GENIMAGE_DEPENDENCIES = host-pkgconf libconfuse
FOO += spaces before
FOO ?= spaces before and after
FOO :=
FOO =
FOO =
FOO =
FOO =
$(MAKE1) CROSS_COMPILE=$(TARGET_CROSS) -C
AT91BOOTSTRAP3_DEFCONFIG = \
AXEL_DISABLE_I18N=--i18n=0
After this bulk change, following manual fixups were done:
- fix line continuation alignment in cegui06 and spice (the sed
expression leaves the number of whitespace between the value and line
continuation character intact, but the whitespace before that could have
changed, causing misalignment.
- qt5base was reverted, as this package uses extensive alignment which
actually makes the code more readable.
Finally, the end result was manually reviewed.
Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
Cc: Yann E. Morin <yann.morin.1998@free.fr>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-10-07 09:06:03 +02:00
|
|
|
NODEJS_CPU = mipsel
|
2013-03-07 15:31:16 +00:00
|
|
|
else ifeq ($(BR2_arm),y)
|
.mk files: bulk aligment and whitespace cleanup of assignments
The Buildroot coding style defines one space around make assignments and
does not align the assignment symbols.
This patch does a bulk fix of offending packages. The package
infrastructures (or more in general assignments to calculated variable
names, like $(2)_FOO) are not touched.
Alignment of line continuation characters (\) is kept as-is.
The sed command used to do this replacement is:
find * -name "*.mk" | xargs sed -i \
-e 's#^\([A-Z0-9a-z_]\+\)\s*\([?:+]\?=\)\s*$#\1 \2#'
-e 's#^\([A-Z0-9a-z_]\+\)\s*\([?:+]\?=\)\s*\([^\\]\+\)$#\1 \2 \3#'
-e 's#^\([A-Z0-9a-z_]\+\)\s*\([?:+]\?=\)\s*\([^\\ \t]\+\s*\\\)\s*$#\1 \2 \3#'
-e 's#^\([A-Z0-9a-z_]\+\)\s*\([?:+]\?=\)\(\s*\\\)#\1 \2\3#'
Brief explanation of this command:
^\([A-Z0-9a-z_]\+\) a regular variable at the beginning of the line
\([?:+]\?=\) any assignment character =, :=, ?=, +=
\([^\\]\+\) any string not containing a line continuation
\([^\\ \t]\+\s*\\\) string, optional whitespace, followed by a
line continuation character
\(\s*\\\) optional whitespace, followed by a line
continuation character
Hence, the first subexpression handles empty assignments, the second
handles regular assignments, the third handles regular assignments with
line continuation, and the fourth empty assignments with line
continuation.
This expression was tested on following test text: (initial tab not
included)
FOO = spaces before
FOO = spaces before and after
FOO = tab before
FOO = tab and spaces before
FOO = tab after
FOO = tab and spaces after
FOO = spaces and tab after
FOO = \
FOO = bar \
FOO = bar space \
FOO = \
GENIMAGE_DEPENDENCIES = host-pkgconf libconfuse
FOO += spaces before
FOO ?= spaces before and after
FOO :=
FOO =
FOO =
FOO =
FOO =
$(MAKE1) CROSS_COMPILE=$(TARGET_CROSS) -C
AT91BOOTSTRAP3_DEFCONFIG = \
AXEL_DISABLE_I18N=--i18n=0
After this bulk change, following manual fixups were done:
- fix line continuation alignment in cegui06 and spice (the sed
expression leaves the number of whitespace between the value and line
continuation character intact, but the whitespace before that could have
changed, causing misalignment.
- qt5base was reverted, as this package uses extensive alignment which
actually makes the code more readable.
Finally, the end result was manually reviewed.
Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
Cc: Yann E. Morin <yann.morin.1998@free.fr>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-10-07 09:06:03 +02:00
|
|
|
NODEJS_CPU = arm
|
2017-01-13 11:55:25 +01:00
|
|
|
else ifeq ($(BR2_aarch64),y)
|
|
|
|
|
NODEJS_CPU = arm64
|
2015-01-12 21:52:01 +01:00
|
|
|
# V8 needs to know what floating point ABI the target is using.
|
2018-09-12 11:22:53 +01:00
|
|
|
NODEJS_ARM_FP = $(GCC_TARGET_FLOAT_ABI)
|
2013-03-07 15:31:16 +00:00
|
|
|
endif
|
|
|
|
|
|
2015-12-08 14:24:47 +00:00
|
|
|
# MIPS architecture specific options
|
|
|
|
|
ifeq ($(BR2_mips)$(BR2_mipsel),y)
|
2016-09-30 10:36:49 +01:00
|
|
|
ifeq ($(BR2_MIPS_CPU_MIPS32R6),y)
|
2015-12-08 14:24:47 +00:00
|
|
|
NODEJS_MIPS_ARCH_VARIANT = r6
|
|
|
|
|
NODEJS_MIPS_FPU_MODE = fp64
|
2016-09-30 10:36:49 +01:00
|
|
|
else ifeq ($(BR2_MIPS_CPU_MIPS32R2),y)
|
2015-12-08 14:24:47 +00:00
|
|
|
NODEJS_MIPS_ARCH_VARIANT = r2
|
2016-09-30 10:36:49 +01:00
|
|
|
else ifeq ($(BR2_MIPS_CPU_MIPS32),y)
|
2015-12-08 14:24:47 +00:00
|
|
|
NODEJS_MIPS_ARCH_VARIANT = r1
|
|
|
|
|
endif
|
|
|
|
|
endif
|
|
|
|
|
|
2019-03-17 20:48:00 +00:00
|
|
|
NODEJS_LDFLAGS = $(TARGET_LDFLAGS)
|
|
|
|
|
|
|
|
|
|
ifeq ($(BR2_TOOLCHAIN_HAS_LIBATOMIC),y)
|
|
|
|
|
NODEJS_LDFLAGS += -latomic
|
|
|
|
|
endif
|
|
|
|
|
|
2013-03-07 15:31:16 +00:00
|
|
|
define NODEJS_CONFIGURE_CMDS
|
2016-03-03 22:29:27 +00:00
|
|
|
mkdir -p $(@D)/bin
|
2017-07-05 13:14:19 +02:00
|
|
|
ln -sf $(HOST_DIR)/bin/python2 $(@D)/bin/python
|
2016-03-03 22:29:27 +00:00
|
|
|
|
2013-03-07 15:31:16 +00:00
|
|
|
(cd $(@D); \
|
|
|
|
|
$(TARGET_CONFIGURE_OPTS) \
|
2016-03-03 22:29:27 +00:00
|
|
|
PATH=$(@D)/bin:$(BR_PATH) \
|
2019-03-17 20:48:00 +00:00
|
|
|
LDFLAGS="$(NODEJS_LDFLAGS)" \
|
2013-03-07 15:31:16 +00:00
|
|
|
LD="$(TARGET_CXX)" \
|
2017-07-05 13:14:19 +02:00
|
|
|
PYTHON=$(HOST_DIR)/bin/python2 \
|
|
|
|
|
$(HOST_DIR)/bin/python2 ./configure \
|
2013-03-07 15:31:16 +00:00
|
|
|
--prefix=/usr \
|
|
|
|
|
--dest-cpu=$(NODEJS_CPU) \
|
|
|
|
|
$(if $(NODEJS_ARM_FP),--with-arm-float-abi=$(NODEJS_ARM_FP)) \
|
2015-12-08 14:24:47 +00:00
|
|
|
$(if $(NODEJS_MIPS_ARCH_VARIANT),--with-mips-arch-variant=$(NODEJS_MIPS_ARCH_VARIANT)) \
|
|
|
|
|
$(if $(NODEJS_MIPS_FPU_MODE),--with-mips-fpu-mode=$(NODEJS_MIPS_FPU_MODE)) \
|
2016-06-03 20:15:43 +01:00
|
|
|
$(NODEJS_CONF_OPTS) \
|
2013-03-07 15:31:16 +00:00
|
|
|
)
|
2019-03-14 13:38:11 +00:00
|
|
|
|
|
|
|
|
# use host version of torque
|
|
|
|
|
sed "s#<(PRODUCT_DIR)/<(EXECUTABLE_PREFIX)torque<(EXECUTABLE_SUFFIX)#$(HOST_DIR)/bin/torque#" \
|
|
|
|
|
-i $(@D)/deps/v8/gypfiles/v8.gyp
|
2013-03-07 15:31:16 +00:00
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define NODEJS_BUILD_CMDS
|
2017-07-05 13:14:19 +02:00
|
|
|
$(TARGET_MAKE_ENV) PYTHON=$(HOST_DIR)/bin/python2 \
|
2014-04-15 00:09:48 +02:00
|
|
|
$(MAKE) -C $(@D) \
|
2014-04-15 00:09:47 +02:00
|
|
|
$(TARGET_CONFIGURE_OPTS) \
|
2017-06-20 09:39:01 +01:00
|
|
|
NO_LOAD=cctest.target.mk \
|
2016-03-03 22:29:27 +00:00
|
|
|
PATH=$(@D)/bin:$(BR_PATH) \
|
2019-03-17 20:48:00 +00:00
|
|
|
LDFLAGS="$(NODEJS_LDFLAGS)" \
|
2014-04-15 00:09:47 +02:00
|
|
|
LD="$(TARGET_CXX)"
|
2013-03-07 15:31:16 +00:00
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
#
|
2017-05-06 14:19:13 +01:00
|
|
|
# Build the list of modules to install.
|
2013-03-07 15:31:16 +00:00
|
|
|
#
|
|
|
|
|
NODEJS_MODULES_LIST= $(call qstrip,\
|
|
|
|
|
$(BR2_PACKAGE_NODEJS_MODULES_ADDITIONAL))
|
|
|
|
|
|
2015-07-02 10:43:27 +01:00
|
|
|
# Define NPM for other packages to use
|
|
|
|
|
NPM = $(TARGET_CONFIGURE_OPTS) \
|
2019-03-17 20:48:00 +00:00
|
|
|
LDFLAGS="$(NODEJS_LDFLAGS)" \
|
2015-07-02 10:43:27 +01:00
|
|
|
LD="$(TARGET_CXX)" \
|
|
|
|
|
npm_config_arch=$(NODEJS_CPU) \
|
|
|
|
|
npm_config_target_arch=$(NODEJS_CPU) \
|
|
|
|
|
npm_config_build_from_source=true \
|
|
|
|
|
npm_config_nodedir=$(BUILD_DIR)/nodejs-$(NODEJS_VERSION) \
|
2015-10-28 15:59:53 +00:00
|
|
|
npm_config_prefix=$(TARGET_DIR)/usr \
|
package/nodejs: use per-build cache directories
When two Buildroot builds run in parallel, and they both happen to call
npm at roughly the same time, the two npm instances may conflict when
accessing the npm cache, which is by default ~/.npm
Although npm is supposed to lock access to the cache, it seems it does
sometimes fail to do so properly, bailling out in error, when it would
never ever crash at all when not running in parallel. We suspect that
the sequence leading to such failures are something like:
npm-1 npm-2
lock(retry=few, sleep=short) .
does-stuff() .
. lock(retry=few, sleep=short)
. # can't lock local cache
. download-module()
. # can't download
. exit(1)
unlock()
As per the docs [0], few = 10, short = 10. So if the first npm (npm-1)
takes more than 100s (which can happen behind slow links and/or big
modules that contain native code that is compiled), then the second npm
(npm-2) will bail out (the download would fail if there is no network
access, for example, and only local modules are used).
Point npm to use a per-build cache directory, so they no longer compete
across builds.
That would still need some care when we do top-level parallel builds,
though.
Note also that the conflicts are not totally eliminated: two or more npm
instances may still compete for some other resource that has not yet
been identified.
But, at least, the conflict window has been drastically shortened now,
to the point where it now seldom occurs.
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-10-13 17:05:58 +02:00
|
|
|
npm_config_cache=$(BUILD_DIR)/.npm-cache \
|
2017-07-05 13:14:19 +02:00
|
|
|
$(HOST_DIR)/bin/npm
|
2015-07-02 10:43:27 +01:00
|
|
|
|
2013-03-07 15:31:16 +00:00
|
|
|
#
|
|
|
|
|
# We can only call NPM if there's something to install.
|
|
|
|
|
#
|
|
|
|
|
ifneq ($(NODEJS_MODULES_LIST),)
|
|
|
|
|
define NODEJS_INSTALL_MODULES
|
|
|
|
|
# If you're having trouble with module installation, adding -d to the
|
|
|
|
|
# npm install call below and setting npm_config_rollback=false can both
|
|
|
|
|
# help in diagnosing the problem.
|
2015-10-28 15:59:53 +00:00
|
|
|
$(NPM) install -g $(NODEJS_MODULES_LIST)
|
2013-03-07 15:31:16 +00:00
|
|
|
endef
|
|
|
|
|
endif
|
|
|
|
|
|
|
|
|
|
define NODEJS_INSTALL_TARGET_CMDS
|
2017-07-05 13:14:19 +02:00
|
|
|
$(TARGET_MAKE_ENV) PYTHON=$(HOST_DIR)/bin/python2 \
|
2014-04-15 00:09:48 +02:00
|
|
|
$(MAKE) -C $(@D) install \
|
2014-04-15 00:09:47 +02:00
|
|
|
DESTDIR=$(TARGET_DIR) \
|
|
|
|
|
$(TARGET_CONFIGURE_OPTS) \
|
2017-06-20 09:39:01 +01:00
|
|
|
NO_LOAD=cctest.target.mk \
|
2016-03-03 22:29:27 +00:00
|
|
|
PATH=$(@D)/bin:$(BR_PATH) \
|
2019-03-17 20:48:00 +00:00
|
|
|
LDFLAGS="$(NODEJS_LDFLAGS)" \
|
2014-04-15 00:09:47 +02:00
|
|
|
LD="$(TARGET_CXX)"
|
2013-03-07 15:31:16 +00:00
|
|
|
$(NODEJS_INSTALL_MODULES)
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
# node.js configure is a Python script and does not use autotools
|
|
|
|
|
$(eval $(generic-package))
|
|
|
|
|
$(eval $(host-generic-package))
|