iojs 2.3.0 name 'openssl_fips' is not defined"

[BlueWinds]

While iojs 2.2.1 has been working fine, I'm unable to install any node-gyp configured modules with --target=2.3.0

$ npm install --target=2.3.0
\
> [email protected] install /.../node_modules/usage
> node-gyp rebuild

gyp: name 'openssl_fips' is not defined while evaluating condition 'openssl_fips != ""' in binding.gyp while trying to load binding.gyp
gyp ERR! configure error 
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onCpExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:343:16)
gyp ERR! stack     at emitTwo (events.js:87:13)
gyp ERR! stack     at ChildProcess.emit (events.js:172:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:199:12)
gyp ERR! System Darwin 14.1.0
gyp ERR! command "/usr/local/bin/iojs" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /.../node_modules/usage
gyp ERR! node -v v2.2.1
gyp ERR! node-gyp -v v1.0.3
gyp ERR! not ok 

This is reproducible on both mac and a debian box. Just in case it's relevant or helpful:

$ for FLAG in cflags-only-I libs-only-L libs-only-l; do pkg-config --$FLAG openssl; done

-lssl -lcrypto -lz

[Fishrock123]

@BlueWinds does this still happen with a new version of io.js?

[Fishrock123]

Works for me on OS X:

Jeremiahs-MacBook-Pro:here-be-dragons Jeremiah$ npm -v
2.11.1
Jeremiahs-MacBook-Pro:here-be-dragons Jeremiah$ node -v
v2.3.0
Jeremiahs-MacBook-Pro:here-be-dragons Jeremiah$ npm i usage
/
> [email protected] install /Users/Jeremiah/node_modules/usage
> node-gyp rebuild

  CXX(target) Release/obj.target/sysinfo/src/binding.o
  SOLINK_MODULE(target) Release/sysinfo.node
[email protected] ../../node_modules/usage
├── [email protected]
└── [email protected]
Jeremiahs-MacBook-Pro:here-be-dragons Jeremiah$ 

Maybe it has to do with your config?

[bmeck]

Happens intermittently for most of us at NodeSource

[BlueWinds]

I realize now I forgot to include a very important piece of the bug report, for which I apologize:

$ node -v
v0.10.31

Globally, an older version of node has been installed. So in my case it's an issue compiling more recent versions using --target when an older version of node is installed globally.

The workaround we've ended up using is to put the version of node I wanted to compile against directly in the path.
PATH=/path/to/iojs-v2.3.3:$PATH npm i usage

[bmeck]

more clearly, node-gyp is creating a config from the current node's process.config not from the one targetted or used via --nodedir

[srlowe]

Has anyone made any progress on this? Having a similar issue with nw-gyp.

[cdaringe]

this is also affecting me as well, 100% of the time. specifically, electron-rebuild is failing, which calls:

node {/path/to/}npm-cli rebuild --target=version --arch=version

@BlueWinds, your suggestion seems reasonable, however, I dont have the binaries for the versions I need to build against all of the time, which is cumbersome. I'm on 0.12.7, and @mafintosh ref'd prebuild/prebuild#14. maybe it's time to upgrade?

[royalpinto]

An extra argument --openssl_fips=X worked for me on OS X. nwjs/nw.js#3786.

[bnoordhuis]

I'll close, I don't believe this is an issue any longer with the supported release lines.

[jakobrosenberg]

I seem to getting this error on AWS Lightsail (Ubuntu 20) with electron-rebuild -v 9.4.4.

[cclauss]

See: #2534

[cclauss]

#2673 (comment)