Error when running npm run build
See original GitHub issueEnvironment info
- NooBaa Version: Master branch
Actual behavior
- Run
npm run build - Fails with errors
/home/yiannis/Workspaces/hybrid-storage/noobaa-core/src/native/third_party/isa-l/erasure_code/gf_vect_dot_prod_avx512.asm:142: error: parser: instruction expected
/home/yiannis/Workspaces/hybrid-storage/noobaa-core/src/native/third_party/isa-l/erasure_code/gf_vect_dot_prod_avx512.asm:148: error: parser: instruction expected
Attaching full logs in the end of the issue
Expected behavior
- Run
npm run build - Build successfully
More information - Screenshots / Logs / Other output
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Errors when running npm run build - node.js
If the build is defined in your package.json file, make sure that you are executing the 'npm run build' in the correct folder...
Read more >Execution of "npm run build" causes an error and can not ...
my "npm start" runs fine,even localhost:3000 is showing my project,but when I try to build the project for uploading netlify...I type "npm run...
Read more >Error when running npm run build : r/react
I have a react app done and am attempting to learn how to deploy it for the first time. I type npm run...
Read more >Common errors
Random errors · Some strange issues can be resolved by simply running npm cache clean and trying again. · If you are having...
Read more >Npm Run Build Failed
... I am deploying my app and the build failed with the following error. ... Dec 1 04:27:01 PM ==> Running build command...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Got it, my nasm version was old (2.10.x) due to RHEL 7.9 is a bit behind on some packages. In case anyone runs into the issue, I needed to update to nasm 2.14 for the npm run build to work. One side-question, the noobaa binary is build in this repo or in the noobaa-operator one?
@liranmauda We can improve this experience if we check the nasm version in asm.gypi:
similar to how we use node_arch in common.gypi:
https://github.com/noobaa/noobaa-core/blob/90ca221719245d97c08d69be37fbd6335cd012a8/src/native/common.gypi#L7
And then we can use it to warn somehow in asm.gypi … not sure exactly how though…