-
-
Notifications
You must be signed in to change notification settings - Fork 214
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
node.addon is produced for wrong architecture, ignoring npm_config_arch #700
Comments
I don't know if this is link
But i get an error about architecture as well. I run this on a macos arm That build a docker image using I also got an error when building the project in CI -> https://github.com/kuzzleio/kuzzle/actions/runs/12674019449/job/35333641100#step:8:4357 In this case, the build is run on a ubuntu:24.04 (github action) and building against the image
|
Linux Arm64 is already supported as of 6.3.0. The prebuilds are provided and built inside Qemu/Docker. You won't need to build from the source. See the build directory under linux/arm64 Here's the CI config: zeromq.js/.github/workflows/CI.yml Line 176 in 4e561cf
Regardless, I've added some fixes for cross-compilation in #693 targeted for Windows Arm64. Next, we can try other cross-compilations for other architectures. |
Describe the bug A clear and concise description of what the bug is.
node.addon is produced for wrong architecture, ignoring npm_config_arch
Reproducing If possible, provide a list of commands or a code sample that
reproduces the bug that you are observing. Otherwise please describe as much as
possible in which circumstances the bug can be observed.
A
yarn workspaces focus
of a project withzeromq == "^6.1.2"
on arm64/armhf will produce a node.addon for x8664, ignoring npm_config_arch.Patching package.json to include the additional configuration for arm64/armhf does not change this situation.
Expected behavior A clear and concise description of what you expected to
happen.
The correct addon architecture is produced for the target system.
Tested on
The text was updated successfully, but these errors were encountered: