'openssl_fips' is not defined while evaluating condition 'openssl_fips != ""'
See original GitHub issueAfter creating an Ubuntu 20 instance on AWS Lightsail, I’m unable to use electron-rebuild
.
Running
npm init
npm install serialport
npm install electron-rebuild
npx electron-rebuild -v 9.4.4
will produce the following error
⠧ Building module: bindings, Completed: 0gyp: name 'openssl_fips' is not defined while evaluating condition 'openssl_fips != ""' in binding.gyp while trying to load binding.gyp
✖ Rebuild Failed
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:6
Top Results From Across the Web
npm ERR! gyp: name 'openssl_fips' is not defined #2673
Solution: #2673 (comment) • electron-builder version=22.14.13 • rebuilding native dependencies dependencies=ffi-napi@4.0.3, ref-napi@3.0.3 ...
Read more >How to rebuild epoll package in electron? - Stack Overflow
gyp: name 'openssl_fips' is not defined while evaluating condition 'openssl_fips != ""' in binding.gyp while trying to load binding.gyp.
Read more >Trouble in nw-gyp with 0.13 - Google Groups
When I run nw-gyp configure --target=0.13.0-beta4 , I get the following error: gyp: name 'openssl_fips' is not defined while evaluating condition ...
Read more >window 下生成NodeJs(v8.9.3) 的VS2015 解决方案node.sln
... -Dtarget_arch=x64 -f msvs gyp: name 'openssl_fips' is not defined while evaluating condition 'openssl_fips !
Read more >OpenSSL 3.0.0 Design
FIPS, which implements the OpenSSL FIPS Cryptographic Module 3.0; ... property setting methods and evaluation approaches will be defined during the ...
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 FreeTop 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
Top GitHub Comments
Updated, bumping to v3.2.5 works for me.
Okay, as mentioned in https://github.com/marktext/marktext/issues/2812 and other places downgrading to Node 16 is a possible workaround.