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

Tool fails in M1 intel machines #514

Closed
dcacenabes opened this issue Apr 7, 2022 · 2 comments
Closed

Tool fails in M1 intel machines #514

dcacenabes opened this issue Apr 7, 2022 · 2 comments
Labels
bug Something isn't working

Comments

@dcacenabes
Copy link

Describe what happened
Running the command in an M1 mac machine throws the error:

dyld[21938]: missing symbol called

Steps to reproduce the issue:
In an M1 machine:

  • install the package (either yarn or npm, does not matter) npm install -g @datadog/datadog-ci
  • call the tool: datadog-ci version

Expected behaviour:
Command outputs v1.2.0

Actual behaviour:

dyld[22320]: missing symbol called
[1]    22320 abort      datadog-ci version

Additional context

  • Monterrey 12.3 in M1
  • Node version tried with 16.13.0 and 17.8.0

I tried doing npx @datadog/[email protected] version and it worked
If I do npx @datadog/[email protected] version it fails
Installing npm install -g @datadog/[email protected] gives the error
Installing npm install -g @datadog/[email protected] also gives the error

@dcacenabes dcacenabes added the bug Something isn't working label Apr 7, 2022
@m-rousse
Copy link
Contributor

m-rousse commented Apr 7, 2022

Hi @dcacenabes,
Thanks for raising this issue.
This is an issue with the ssh2 and cpu-features libraries we rely on, it is tracked in the following issue: mscdex/cpu-features#7
TL;DR is that the maintainer of these packages is waiting on the support for M1s in Google’s cpu_feature tool.

Alternatively, you should be able to install the package by discarding the optional dependencies using --no-optional.

@dcacenabes
Copy link
Author

Hi @m-rousse , thanks for your quick reply!
Apparently --no-optional is not working when you install a package globally. (npm i -g --no-optional @datadog/datadog-ci)
We moved to installing it locally enforcing no optional parameter and launch with npx, then it worked!
Thanks for your support.

lefebvree added a commit that referenced this issue May 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants