Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Facing issues while installing on ppc64le architeecture #719

Open
vinodk99 opened this issue May 13, 2024 · 2 comments
Open

Facing issues while installing on ppc64le architeecture #719

vinodk99 opened this issue May 13, 2024 · 2 comments
Labels
question Further information is requested

Comments

@vinodk99
Copy link

Describe the bug
Facing issues while installing on ppc64le architeecture
To Reproduce

Please fill the following code example:

Engine.IO server version: 6.5.3

Expected behavior
A clear and concise description of what you expected to happen.

Platform:--PPC64LE
NAME="Red Hat Enterprise Linux"
VERSION="9.3 (Plow)"
ID="rhel"
ID_LIKE="fedora"
VERSION_ID="9.3"
PLATFORM_ID="platform:el9"
PRETTY_NAME="Red Hat Enterprise Linux 9.3 (Plow)"
ANSI_COLOR="0;31"
LOGO="fedora-logo-icon"
CPE_NAME="cpe:/o:redhat:enterprise_linux:9::baseos"
HOME_URL="https://www.redhat.com/"
DOCUMENTATION_URL="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9"
BUG_REPORT_URL="https://bugzilla.redhat.com/"

REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 9"
REDHAT_BUGZILLA_PRODUCT_VERSION=9.3
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="9.3"

Additional context
Facing below issue:

[root@1b179e371443 engine.io-client]# npm ci npm WARN deprecated request@2.11.4: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated forEachAsync@2.2.1: Please use 'foreachasync' instead. See https://www.npmjs.com/package/foreachasync npm WARN deprecated natives@1.1.6: This module relies on Node.js's internals and will break at some point. Do not use it, and update to graceful-fs@4.x. npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated npm WARN deprecated tar.gz@1.0.7: ⚠️ WARNING ⚠️ tar.gz module has been deprecated and your application is vulnerable. Please use tar module instead: https://npmjs.com/tar npm WARN deprecated har-validator@5.1.3: this library is no longer supported npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated npm WARN deprecated graceful-fs@1.2.3: please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js npm WARN deprecated cryptiles@0.2.2: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated npm WARN deprecated chokidar@1.7.0: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies. npm WARN deprecated source-map-url@0.4.0: See https://github.com/lydell/source-map-url#deprecated npm WARN deprecated boom@0.4.2: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated sntp@0.2.4: This module moved to @hapi/sntp. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues. npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue npm WARN deprecated chokidar@2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies npm WARN deprecated minimatch@0.4.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue npm WARN deprecated minimatch@0.3.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue npm WARN deprecated minimatch@0.3.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead. npm WARN deprecated minimatch@1.0.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue npm WARN deprecated mkdirp@0.3.5: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.) npm WARN deprecated mkdirp@0.3.5: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.) npm WARN deprecated hoek@0.9.1: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated uuid@3.3.3: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm WARN deprecated node-uuid@1.4.8: Use uuid module instead npm WARN deprecated superagent@0.15.7: Please upgrade to v7.0.2+ of superagent. We have fixed numerous issues with streams, form-data, attach(), filesystem errors not bubbling up (ENOENT on attach()), and all tests are now passing. See the releases tab for more information at <https://github.com/visionmedia/superagent/releases>. npm WARN deprecated request@2.46.0: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated request@2.88.0: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated wrench@1.5.9: wrench.js is deprecated! You should check out fs-extra (https://github.com/jprichardson/node-fs-extra) for any operations you were using wrench for. Thanks for all the usage over the years. npm WARN deprecated hawk@1.1.1: This module moved to @hapi/hawk. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues. npm WARN deprecated formidable@1.0.14: Please upgrade to latest, formidable@v2 or formidable@v3! Check these notes: https://bit.ly/2ZEqIau npm WARN deprecated istanbul@0.2.16: This module is no longer maintained, try this instead: npm WARN deprecated npm i nyc npm WARN deprecated Visit https://istanbul.js.org/integrations for other alternatives. npm WARN deprecated highlight.js@7.5.0: Version no longer supported. Upgrade to @latest npm WARN deprecated istanbul@0.4.5: This module is no longer maintained, try this instead: npm WARN deprecated npm i nyc npm WARN deprecated Visit https://istanbul.js.org/integrations for other alternatives. npm WARN deprecated connect@2.12.0: connect 2.x series is deprecated npm WARN deprecated tar@2.2.2: This version of tar is no longer supported, and will not receive security updates. Please upgrade asap. npm ERR! code 1 npm ERR! path /engine.io-client/node_modules/@fails-components/webtransport npm ERR! command failed npm ERR! command sh -c -- node build.js install npm ERR! Webtransport binary handler: We are working on platform linux_ppc64 npm ERR! child process exited with code 1 npm ERR! tmpdir /tmp npm ERR! child process exited with code 127 npm ERR! (node:3403) ExperimentalWarning: Importing JSON modules is an experimental feature. This feature could change at any time npm ERR! (Use node --trace-warnings ...` to show where the warning was created)
npm ERR! prebuild-install info begin Prebuild-install version 7.1.1
npm ERR! prebuild-install info looking for local prebuild @ prebuilds/webtransport-v0.1.7-napi-v6-linux-ppc64.tar.gz
npm ERR! prebuild-install info looking for cached prebuild @ /root/.npm/_prebuilds/891a77-webtransport-v0.1.7-napi-v6-linux-ppc64.tar.gz
npm ERR! prebuild-install http request GET https://github.com/fails-components/webtransport/releases/download/v0.1.7/webtransport-v0.1.7-napi-v6-linux-ppc64.tar.gz
npm ERR! prebuild-install http 404 https://github.com/fails-components/webtransport/releases/download/v0.1.7/webtransport-v0.1.7-napi-v6-linux-ppc64.tar.gz
npm ERR! prebuild-install warn install No prebuilt binaries found (target=6 runtime=napi arch=ppc64 libc= platform=linux)
npm ERR! No prebuild available, building binary, this may take more than 20 minutes
npm ERR! Now extracting third party lib code from git....
npm ERR! Cloning into 'webtransport'...
npm ERR!
npm ERR! Note: switching to '02112777c583e7f106fdbeda72cf11bd755179be'.
npm ERR!
npm ERR! You are in 'detached HEAD' state. You can look around, make experimental
npm ERR! changes and commit them, and you can discard any commits you make in this
npm ERR! state without impacting any branches by switching back to a branch.
npm ERR!
npm ERR! If you want to create a new branch to retain commits you create, you may
npm ERR! do so (now or later) by using -c with the switch command. Example:
npm ERR!
npm ERR! git switch -c
npm ERR!
npm ERR! Or undo this operation with:
npm ERR!
npm ERR! git switch -
npm ERR!
npm ERR! Turn off this advice by setting config variable advice.detachedHead to false
npm ERR!
npm ERR!
npm ERR! Submodule 'third_party/boringssl/src' (https://github.com/google/boringssl.git) registered for path 'third_party/boringssl/src'
npm ERR!
npm ERR! Cloning into '/tmp/wtbuild-KdGBa1/webtransport/third_party/boringssl/src'...
npm ERR!
npm ERR! From https://github.com/google/boringssl
npm ERR! * branch b0a026f8541c551854efd617021bb276f1fe5c23 -> FETCH_HEAD
npm ERR!
npm ERR! Submodule 'third_party/abseil-cpp' (https://github.com/abseil/abseil-cpp.git) registered for path 'third_party/abseil-cpp'
npm ERR!
npm ERR! Cloning into '/tmp/wtbuild-KdGBa1/webtransport/third_party/abseil-cpp'...
npm ERR!
npm ERR! From https://github.com/abseil/abseil-cpp
npm ERR! * branch c2435f8342c2d0ed8101cb43adfd605fdc52dca2 -> FETCH_HEAD
npm ERR!
npm ERR! Submodule 'third_party/quiche' (https://github.com/google/quiche.git) registered for path 'third_party/quiche'
npm ERR!
npm ERR! Cloning into '/tmp/wtbuild-KdGBa1/webtransport/third_party/quiche'...
npm ERR!
npm ERR! From https://github.com/google/quiche
npm ERR! * branch 8f410c8be441323715e200c7a1c211ba9fdd73c9 -> FETCH_HEAD
npm ERR!
npm ERR! Submodule 'third_party/zlib' (https://github.com/madler/zlib.git) registered for path 'third_party/zlib'
npm ERR!
npm ERR! Cloning into '/tmp/wtbuild-KdGBa1/webtransport/third_party/zlib'...
npm ERR!
npm ERR! From https://github.com/madler/zlib
npm ERR! * branch 04f42ceca40f73e2978b50e93806c2a18c1281fc -> FETCH_HEAD
npm ERR!
npm ERR! Submodule 'third_party/googleurl' (https://quiche.googlesource.com/googleurl) registered for path 'third_party/googleurl'
npm ERR!
npm ERR! Cloning into '/tmp/wtbuild-KdGBa1/webtransport/third_party/googleurl'...
npm ERR!
npm ERR! From https://quiche.googlesource.com/googleurl
npm ERR! * branch ef6a4f8b2f5a418313cfae6471ed9734b5fcea91 -> FETCH_HEAD
npm ERR!
npm ERR! Submodule 'third_party/libevent' (https://github.com/libevent/libevent.git) registered for path 'third_party/libevent'
npm ERR!
npm ERR! Cloning into '/tmp/wtbuild-KdGBa1/webtransport/third_party/libevent'...
npm ERR!
npm ERR! From https://github.com/libevent/libevent
npm ERR! * branch e7ff4ef2b4fc950a765008c18e74281cdb5e7668 -> FETCH_HEAD
npm ERR!
npm ERR! Submodule 'third_party/protobuf' (https://github.com/protocolbuffers/protobuf.git) registered for path 'third_party/protobuf'
npm ERR!
npm ERR! Cloning into '/tmp/wtbuild-KdGBa1/webtransport/third_party/protobuf'...
npm ERR!
npm ERR! From https://github.com/protocolbuffers/protobuf
npm ERR! * branch 90b73ac3f0b10320315c2ca0d03a5a9b095d2f66 -> FETCH_HEAD
npm ERR!
npm ERR! Submodule 'third_party/benchmark' (https://github.com/google/benchmark.git) registered for path 'third_party/protobuf/third_party/benchmark'
npm ERR!
npm ERR! Submodule 'third_party/googletest' (https://github.com/google/googletest.git) registered for path 'third_party/protobuf/third_party/googletest'
npm ERR!
npm ERR! Cloning into '/tmp/wtbuild-KdGBa1/webtransport/third_party/protobuf/third_party/benchmark'...
npm ERR!
npm ERR! Cloning into '/tmp/wtbuild-KdGBa1/webtransport/third_party/protobuf/third_party/googletest'...
npm ERR!
npm ERR! error: pathspec 'third_party/icu' did not match any file(s) known to git
npm ERR!
npm ERR! failed to get third party code from git
npm ERR! Building binary failed: Error: Cannot get thirdparty code
npm ERR! at extractthirdparty (file:///engine.io-client/node_modules/@fails-components/webtransport/build.js:127:20)
npm ERR! at async file:///engine.io-client/node_modules/@fails-components/webtransport/build.js:257:9
npm ERR! /bin/sh: line 1: cmake-js: command not found
npm ERR! Building binary failed: 127

npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2024-05-13T07_12_22_238Z-debug-0.log
`

@vinodk99 vinodk99 added the bug Something isn't working label May 13, 2024
@darrachequesne
Copy link
Member

Hi!

Could you please explain what you are trying to do? It seems there is an error when installing the @fails-components/webtransport dev dependency.

@darrachequesne darrachequesne added question Further information is requested and removed bug Something isn't working labels May 17, 2024
@vinodk99
Copy link
Author

Hi!

Could you please explain what you are trying to do? It seems there is an error when installing the @fails-components/webtransport dev dependency.

@darrachequesne while executing npm install facing above issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants