GCC 4.8 compatibility was lost moving from 10.15.1 to 10.15.3. Add
another wrapper for std::make_unique to restore it.
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
- do not drop target LDFLAGS
- even if the target LDFLAGS have been specified, tools like torque was
linked with system libraries
Signed-off-by: Andrej Valek <andrej.valek@siemens.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
- replace all occurrences of std::make_unique with wrapper
- sync indent level
Signed-off-by: Andrej Valek <andrej.valek@siemens.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Update nodejs to active 10.x LTS release 10.15.1.
- link atomic library
- make it compatible with gcc < 4.9
Signed-off-by: Andrej Valek <andrej.valek@siemens.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Since `36983fe umip: move to meta-networking' applied,
it was moved to invalid location.
Fix prior partial move to meta-networking
Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Node.js > 8.10 also compile with OpenSSL 1.1
License check sum changes because typo fix in LICENSE file.
No license change.
Signed-off-by: Pascal Bach <pascal.bach@siemens.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
If you want to perform an "npm install" and a module needs to be compiled,
these additional packages need to be on the target otherwise the compile might
fail with one or more of the following error messages:
ImportError: No module named compiler.ast
ImportError: No module named filecmp
ImportError: No module named multiprocessing
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
Signed-off-by: Armin Kuster <akuster808@gmail.com>
ppc64le is a little-endian mode of ppc64.
Nodejs determines the endianness of the system and
since it already supports bi-endian ppc64, just pass
nodejs "ppc64" when the TARGET_ARCH is ppc64le.
Signed-off-by: Gunnar Mills <gmills@linux.vnet.ibm.com>
Signed-off-by: Armin Kuster <akuster808@gmail.com>
LICENSE checksum updated due to copyright and formatting changes.
Signed-off-by: Jonathan Liu <net147@gmail.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
${bindir}/npx is a symbolic link to npm-cli.js in the npm module.
This avoids the nodejs package depending on nodejs-npm.
Signed-off-by: Jonathan Liu <net147@gmail.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
getVar() now defaults to expanding by default, thus remove the True
option from getVar() calls with a regex search and replace.
Search made with the following regex: getVar ?\(( ?[^,()]*), True\)
Signed-off-by: Joshua Lock <joshua.g.lock@intel.com>
LICENSE checksum updated due to change in ESLint copyright line:
- Copyright (c) 2013 Nicholas C. Zakas. All rights reserved.
+ Copyright jQuery Foundation and other contributors, https://jquery.org/
Signed-off-by: Jonathan Liu <net147@gmail.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
LICENSE checksum has changed due to OpenSSL copyright year being
bumped from 1998-2011 to 1998-2016.
Signed-off-by: Jonathan Liu <net147@gmail.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Fixes CVE-2016-2086 and CVE-2016-2216.
LICENSE checksum changed because it was regenerated using the new
tools/license-builder.sh script but the licensing remains the same.
Signed-off-by: Jonathan Liu <net147@gmail.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Additionally, the LICENSE file changed as follows:
- npm is a package manager program located at deps/npm.
npm's license follows:
"""
- Copyright (c) Isaac Z. Schlueter
- All rights reserved.
-
- npm is released under the Artistic 2.0 License.
- The text of the License follows:
+ The npm application
+ Copyright (c) npm, Inc. and Contributors
+ Licensed on the terms of The Artistic License 2.0
+
+ Node package dependencies of the npm application
+ Copyright (c) their respective copyright owners
+ Licensed on their respective license terms
+
+ The npm public registry at https://registry.npmjs.com
+ and the npm website at https://www.npmjs.com
+ Operated by npm, Inc.
+ Use governed by terms published on https://www.npmjs.com
+
+ "Node.js"
+ Trademark Joyent, Inc., https://joyent.com
+ Neither npm nor npm, Inc. are affiliated with Joyent, Inc.
+
+ The Node.js application
+ Project of Node Foundation, https://nodejs.org
+
+ The npm Logo
+ Copyright (c) Mathias Pettersson and Brian Hammond
+
+ "Gubblebum Blocky" typeface
+ Copyright (c) Tjarda Koster, https://jelloween.deviantart.com
+ Used with permission
...
- "Node.js" and "node" trademark Joyent, Inc. npm is not officially
- part of the Node.js project, and is neither owned by nor
- officially affiliated with Joyent, Inc.
-
- Packages published in the npm registry (other than the Software and
- its included dependencies) are not part of npm itself, are the sole
- property of their respective maintainers, and are not covered by
- this license.
+ The following additional terms shall apply to use of the npm software, the npm
+ website, the npm repository and any other services or products offered by npm,
+ Inc.:
+
+ "Node.js" trademark Joyent, Inc. npm is not officially part of the Node.js
+ project, and is neither owned by nor affiliated with Joyent, Inc.
+
+ "npm" and "The npm Registry" are owned by npm, Inc. All rights reserved.
+
+ Modules published on the npm registry are not officially endorsed by npm, Inc.
+ or the Node.js project.
+
+ Data published to the npm registry is not part of npm itself, and is the sole
+ property of the publisher. While every effort is made to ensure accountability,
+ there is absolutely no guarantee, warrantee, or assertion expressed or implied
+ as to the quality, fitness for a specific purpose, or lack of malice in any
+ given npm package. Packages downloaded through the npm registry are
+ independently licensed and are not covered by this license.
+
+ Additional policies relating to, and restrictions on use of, npm products and
+ services are available on the npm website. All such policies and restrictions,
+ as updated from time to time, are hereby incorporated into this license
+ agreement. By using npm, you acknowledge your agreement to all such policies
+ and restrictions.
+
+ If you have a complaint about a package in the public npm registry, and cannot
+ resolve it with the package owner, please email support@npmjs.com and explain
+ the situation. See the [npm Dispute Resolution
+ policy](https://github.com/npm/policies/blob/master/disputes.md) for more
+ details.
- "npm Logo" created by Mathias Pettersson and Brian Hammond,
- used with permission.
+ Any data published to The npm Registry (including user account information) may
+ be removed or modified at the sole discretion of the npm server administrators.
+
+ "npm Logo" contributed by Mathias Pettersson and Brian Hammond,
+ use is subject to https://www.npmjs.com/policies/trademark
"Gubblebum Blocky" font
- Copyright (c) by Tjarda Koster, http://jelloween.deviantart.com
+ Copyright (c) by Tjarda Koster, https://jelloween.deviantart.com
included for use in the npm website and documentation,
used with permission.
- This program uses several Node.js modules contained in the node_modules/
+ This program uses several Node modules contained in the node_modules/
subdirectory, according to the terms of their respective licenses.
"""
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Remove old nodejs4_0.4.12 and update nodejs_0.12.7 to the latest stable
nodejs_4.2.3.
Nodejs is picky about which architectures it supports. The supported arch
mapping required some updating to bring it up to date with the current nodejs
code. Add COMPATIBLE_MACHINE entries so it only builds for the supported
architectures.
ARM cores that don't support at least VFP2 have been dropped:
https://groups.google.com/forum/#!topic/v8-users/aSOFbaAQvMk
"Due the increasing cost of the keeping the "no-VFPv2" port of V8 working
on ARM, we are planning on making 3.17 the last V8 release that that
supports ARM chips without VFPv2. Starting with the 3.18 release, the
minimal V8 requirements will increase to ARMv6 + VFPv2. In order to
simplify maintenance, we will also remove the "pre-VFP2" ARM code from the
V8 code base."
Additionally, gcc no longer supports a VFPv2 option:
https://gcc.gnu.org/onlinedocs/gcc/ARM-Options.html#index-mfpu-1460
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
