Requirements to install IJavascript using Node.js v9, v10, v11 and above

[n-riesco]

I'm opening this issue so that I can close a number of duplicate issues reporting a failure to install IJavascript on Node.js v9 and above:

• 165

• 179

• 182

• 183

IJavascript depends on zeromq v4 that only provides prebuilt binaries to Node.js versions up to 8.

Users of Node.js v9 and above need the following requirements to install IJavascript:

• the requirements to run node-gyp:
  • python v2.7 (note that it is possible to install python v2 and python v3 on the same machine)
  • make
  • a C/C++ compiler (e.g. gcc)
• the library libzmq:
  • (option 1) the user's machine has internet access to https://github.com/zeromq/libzmq and it isn't behind a proxy (see issue https://github.com/zeromq/zeromq.js/issues/260 ). This option should work by default
  • (option 2) libzmq is already installed in the user's machine. This option requires the use of the flag --zmq-external.

For example, on an Ubuntu machine without internet access, the user would need to run the following:

$ sudo apt install libzmq3-dev build-essential python2.7
$ npm install -g ijavascript --zmq-external

[n-riesco]

I'm considering the following solutions to this issue:

• Upgrade dependency to zeromq v5.

  • Pros:
  • quickest solution
  • Cons:
  • drop support for Node.js v4 and v0.10
  • @lgeiger I'm guessing from https://github.com/nteract/nteract/pull/3388 that the upcoming zeromq-ng requires changes in jmp, doesn't it?

• Provide missing prebuilt binaries for zeromq v4.

  • Pros:
  • keep support for Node.js v4 and v0.10
  • Cons:
  • not a solution for users that can't access github
  • not a solution, only postpones the decision on upgrading zeromq

• Distribute IJavascript as an electron app.

  • Pros:
  • users don't need to install any requirements
  • users can easily install kernels for different versions of Node.js on the same machine
  • Cons:
  • only postpones the decision on upgrading zeromq
  • electron apps are heavy

• ...

[rgbkrk]

Yay for dropping support for old node that is before the long term stable releases.

[whyboris]

This is not a con:

drop support for Node.js v4 and v0.10

We should be actively discouraging people from using Node versions (v6 and older) that have reached their end of life 👍

[johntron]

Yeah, get rid of those ancient versions!

[kaidatavis]

I am new to Mac and stuck on the second last step of the installation instruction (the first 4 steps went well): npm install -g ijavascript

I have the latest Node (12.4.0) and NPM (6.9.0). It seems that the error is the c compiler (where is the config.log?):

checking whether the C compiler works... no
configure: error: in `/usr/local/lib/node_modules/ijavascript/node_modules/zeromq/zmq/zeromq-4.2.2':
configure: error: C compiler cannot create executables
See `config.log' for more details

I do have the gcc compiler:

(base) Kais-MBP:~ kai$ gcc -v
Configured with: --prefix=/Library/Developer/CommandLineTools/usr --with-gxx-include-dir=/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/include/c++/4.2.1
Apple LLVM version 10.0.1 (clang-1001.0.46.4)
Target: x86_64-apple-darwin18.6.0
Thread model: posix
InstalledDir: /Library/Developer/CommandLineTools/usr/bin

Also, I have both python 2 (/usr/local/bin/python2) and python 3 (/anaconda3/bin/python3). Calling 'python' will run python 3 (3.7.3) not python 2 (2.7.16); I am not sure if this is an issue.

Below is the full output:

(base) Kais-MBP:~ kai$ npm install -g ijavascript
/usr/local/bin/ijs -> /usr/local/lib/node_modules/ijavascript/bin/ijavascript.js
/usr/local/bin/ijsconsole -> /usr/local/lib/node_modules/ijavascript/bin/ijsconsole.js
/usr/local/bin/ijsinstall -> /usr/local/lib/node_modules/ijavascript/bin/ijsinstall.js
/usr/local/bin/ijskernel -> /usr/local/lib/node_modules/ijavascript/lib/kernel.js
/usr/local/bin/ijsnotebook -> /usr/local/lib/node_modules/ijavascript/bin/ijsnotebook.js

> zeromq@4.6.0 install /usr/local/lib/node_modules/ijavascript/node_modules/zeromq
> node scripts/prebuild-install.js || (node scripts/preinstall.js && node-gyp rebuild)

prebuild-install WARN install No prebuilt binaries found (target=12.4.0 runtime=node arch=x64 platform=darwin)

Building libzmq for darwin
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... config/install-sh -c -d
checking for gawk... no
checking for mawk... no
checking for nawk... no
checking for awk... awk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether UID '501' is supported by ustar format... yes
checking whether GID '20' is supported by ustar format... yes
checking how to create a ustar tar archive... gnutar
checking whether make supports nested variables... (cached) yes
checking for gcc... x86_64-apple-darwin13.4.0-clang
checking whether the C compiler works... no
configure: error: in `/usr/local/lib/node_modules/ijavascript/node_modules/zeromq/zmq/zeromq-4.2.2':
configure: error: C compiler cannot create executables
See `config.log' for more details
child process exited with code 77
make: Entering directory '/usr/local/lib/node_modules/ijavascript/node_modules/zeromq/build'
  CXX(target) Release/obj.target/zmq/binding.o
../binding.cc:28:10: fatal error: 'zmq.h' file not found
#include <zmq.h>
         ^~~~~~~
1 error generated.
make: *** [zmq.target.mk:129: Release/obj.target/zmq/binding.o] Error 1
make: Leaving directory '/usr/local/lib/node_modules/ijavascript/node_modules/zeromq/build'
gyp ERR! build error 
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:262:23)
gyp ERR! stack     at ChildProcess.emit (events.js:200:13)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:272:12)
gyp ERR! System Darwin 18.6.0
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /usr/local/lib/node_modules/ijavascript/node_modules/zeromq
gyp ERR! node -v v12.4.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok 
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! zeromq@4.6.0 install: `node scripts/prebuild-install.js || (node scripts/preinstall.js && node-gyp rebuild)`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the zeromq@4.6.0 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/kai/.npm/_logs/2019-06-12T23_55_51_043Z-debug.log
(base) Kais-MBP:~ kai$ 

[n-riesco]

@kaimdx This may be an issue with your dev tools. Please, could you open a new issue?

To locate the 'config.log', I'd try to run:

find /usr/local/lib/node_modules/ijavascript/node_modules/zeromq -name config.log

[pytkr]

Hi! I successfully installed ijavascript as this:

conda update -c conda-forge nodejs
conda activate base
npm config set python "C:\Python27\python.exe"
(**open cmd as administrator**) npm install --global --production windows-build-tools
npm install -g node-gyp
npm install -g ijavascript
ijsinstall

However, I open jupyter notebook and create javascript notebook, and it can't execute js code cell, and cmd shows error:

[I 10:08:56.307 NotebookApp] KernelRestarter: restarting kernel (1/5), new random ports internal/modules/cjs/loader.js:613 throw err; ^

Error: Cannot find module '../build/Release/zmq.node' Require stack:

• C:\Users\welcome2\Miniconda3\node_modules\ijavascript\node_modules\zeromq\lib\index.js
• C:\Users\welcome2\Miniconda3\node_modules\ijavascript\node_modules\zeromq\index.js
• C:\Users\welcome2\Miniconda3\node_modules\ijavascript\node_modules\jmp\index.js
• C:\Users\welcome2\Miniconda3\node_modules\ijavascript\node_modules\jp-kernel\lib\jp-kernel.js
• C:\Users\welcome2\Miniconda3\node_modules\ijavascript\node_modules\jp-kernel\index.js
• C:\Users\welcome2\Miniconda3\node_modules\ijavascript\lib\kernel.js at Function.Module._resolveFilename (internal/modules/cjs/loader.js:610:15) at Function.Module._load (internal/modules/cjs/loader.js:526:27) at Module.require (internal/modules/cjs/loader.js:666:19) at require (internal/modules/cjs/helpers.js:16:16) at Object. (C:\Users\welcome2\Miniconda3\node_modules\ijavascript\node_modules\zeromq\lib\index.js:6:11) at Module._compile (internal/modules/cjs/loader.js:759:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:770:10) at Module.load (internal/modules/cjs/loader.js:628:32) at Function.Module._load (internal/modules/cjs/loader.js:555:12) at Module.require (internal/modules/cjs/loader.js:666:19)

Then, I download libzmq and build using vs 2019, now I get zeromq-4.3.2\bin2\bin\Release\libzmq-v141-mt-4_3_2.dll, how to use this to make npm install zeromq successful?

[n-riesco]

I've just released IJavascript@5.2 that depends jp-kernel@2 and uses the new prebuilt binaries for zeromq@5. This should make life easier for those using recent versions of Node.

[yozi-developer]

I had the same issue on MacOS and nvm. I guess something is wrong in this case with the global installation. So, I had to install it locally

npm init npm install --save ijavascript (without -g key) added "start": "ijsnotebook" to the package.json npm start

[sean-bai]

Not sure how this bug happens, but I still have this problem even you update to use zeromq@5. The way I solve this:

Step1. npm install -g zeromq
Step2. npm install -g ijavascript   

npm detect a newer version zeromq@6 so it skip the installation of dependency zeromq@5. And then every thing works. Maybe you should consider using zeromq@6?

[n-riesco]

I don't have plans to upgrade to zeromq@6 while it remains in beta.

Also note that zeromq@6 still lacks some binaries (e.g. see https://github.com/zeromq/zeromq.js/issues/396).

[ozbigcat]

I think I found the culprit of this problem. In my windows box, all the npm installed module are line up nicely in the folder: "C:\Users\\AppData\Roaming\npm\node_modules", including:

• ijavascript
• node-gyp
• zeromq

However, the kernel complains of not finding the zmq.node in the folder: "C:\Users\\AppData\Roaming\npm\node_modules\ijavascript\node_modules\"

So, I just copy manually the zeromq folder from [...\npm\node_modules] to [...\npm\node_modules\ijavascript\node_modules] and the kernel start working without a hitch in the notebook.

The zeromq folder was actually there, only missing the /Release folder that contains the zmq.node

In my opinion looks like just a matter of missing "/" in the path variable. The ijavascript is not supposed to have its own /node_modules/, isn't it?

As a recap, all the installation I did were: npm install --global --production windows-build-tools --vs2015 npm install -g zeromq@5 npm install -g node-gyp npm install -g ijavascript ijsinstall

Good stuff guys!

[talelamira]

Thank you @ozbigcat This solution worked for me

[diegoasanch]

Thanks @ozbigcat It worked for me too!

[KrishnarajT]

Thank you so much @ozbigcat The solution worked perfectly for me, id been digging for a day!

[L4yman43]

I am new to programming, and am attempting to setup my Jupyternotebook with the JS kernel as well.

After spending 5-6 hours trying everything I am completely stuck. The issue seems to be with compatibility.

npm install -g zeromq@5 npm ERR! code 1 npm ERR! path C:\Users\Kolo\AppData\Roaming\npm\node_modules\zeromq npm ERR! command failed npm ERR! command C:\Windows\system32\cmd.exe /d /s /c node-gyp-build || npm run build:libzmq npm ERR! prepare-build npm ERR! Downloading libzmq for Windows npm ERR! Download finished npm ERR! binding.cc npm ERR! C:\Users\Kolo\AppData\Roaming\npm\node_modules\zeromq\binding.cc(399,10): warning C4996: 'Nan::MakeCallback': was declared deprecated [C:\Users\Kolo\AppData\Roaming\npm\node_modules\zeromq\build\zmq.vcxproj] npm ERR! C:\Users\Kolo\AppData\Roaming\npm\node_modules\zeromq\binding.cc(407,10): warning C4996: 'Nan::MakeCallback': was declared deprecated [C:\Users\Kolo\AppData\Roaming\npm\node_modules\zeromq\build\zmq.vcxproj] npm ERR! C:\Users\Kolo\AppData\Roaming\npm\node_modules\zeromq\binding.cc(458,10): warning C4996: 'Nan::MakeCallback': was declared deprecated [C:\Users\Kolo\AppData\Roaming\npm\node_modules\zeromq\build\zmq.vcxproj] npm ERR! C:\Users\Kolo\AppData\Roaming\npm\node_modules\zeromq\binding.cc(473,10): warning C4996: 'Nan::MakeCallback': was declared deprecated [C:\Users\Kolo\AppData\Roaming\npm\node_modules\zeromq\build\zmq.vcxproj] npm ERR! C:\Users\Kolo\AppData\Roaming\npm\node_modules\zeromq\binding.cc(814,10): warning C4996: 'Nan::MakeCallback': was declared deprecated [C:\Users\Kolo\AppData\Roaming\npm\node_modules\zeromq\build\zmq.vcxproj] npm ERR! C:\Users\Kolo\AppData\Roaming\npm\node_modules\zeromq\binding.cc(893,10): warning C4996: 'Nan::MakeCallback': was declared deprecated [C:\Users\Kolo\AppData\Roaming\npm\node_modules\zeromq\build\zmq.vcxproj] npm ERR! C:\Users\Kolo\AppData\Local\node-gyp\Cache\21.6.2\include\node\v8-local-handle.h(253,42): error C2338: static_assert failed: 'type check' [C:\Users\Kolo\AppData\Roaming\npm\node_modules\zeromq\build\zmq.vcxproj] npm ERR! (compiling source file '../binding.cc') npm ERR! C:\Users\Kolo\AppData\Local\node-gyp\Cache\21.6.2\include\node\v8-local-handle.h(253,42): npm ERR! the template instantiation context (the oldest one first) is npm ERR! C:\Users\Kolo\AppData\Roaming\npm\node_modules\zeromq\node_modules\nan\nan_callbacks_12_inl.h(175,41): npm ERR! see reference to function template instantiation 'v8::Local::Local(v8::Local)' being compiled npm ERR! C:\Users\Kolo\AppData\Roaming\npm\node_modules\zeromq\node_modules\nan\nan_callbacks_12_inl.h(175,13): npm ERR! see the first reference to 'v8::Local::Local' in 'Nan::imp::FunctionCallbackWrapper' npm ERR! npm ERR! npm ERR! > zeromq@5.3.1 build:libzmq npm ERR! > node-gyp rebuild npm ERR! npm ERR! npm ERR! npm ERR! prepare-build npm ERR! binding.cc npm ERR! C:\Users\Kolo\AppData\Roaming\npm\node_modules\zeromq\binding.cc(399,10): warning C4996: 'Nan::MakeCallback': was declared deprecated [C:\Users\Kolo\AppData\Roaming\npm\node_modules\zeromq\build\zmq.vcxproj] npm ERR! C:\Users\Kolo\AppData\Roaming\npm\node_modules\zeromq\binding.cc(407,10): warning C4996: 'Nan::MakeCallback': was declared deprecated [C:\Users\Kolo\AppData\Roaming\npm\node_modules\zeromq\build\zmq.vcxproj] npm ERR! C:\Users\Kolo\AppData\Roaming\npm\node_modules\zeromq\binding.cc(458,10): warning C4996: 'Nan::MakeCallback': was declared deprecated [C:\Users\Kolo\AppData\Roaming\npm\node_modules\zeromq\build\zmq.vcxproj] npm ERR! C:\Users\Kolo\AppData\Roaming\npm\node_modules\zeromq\binding.cc(473,10): warning C4996: 'Nan::MakeCallback': was declared deprecated [C:\Users\Kolo\AppData\Roaming\npm\node_modules\zeromq\build\zmq.vcxproj] npm ERR! C:\Users\Kolo\AppData\Roaming\npm\node_modules\zeromq\binding.cc(814,10): warning C4996: 'Nan::MakeCallback': was declared deprecated [C:\Users\Kolo\AppData\Roaming\npm\node_modules\zeromq\build\zmq.vcxproj] npm ERR! C:\Users\Kolo\AppData\Roaming\npm\node_modules\zeromq\binding.cc(893,10): warning C4996: 'Nan::MakeCallback': was declared deprecated [C:\Users\Kolo\AppData\Roaming\npm\node_modules\zeromq\build\zmq.vcxproj] npm ERR! C:\Users\Kolo\AppData\Local\node-gyp\Cache\21.6.2\include\node\v8-local-handle.h(253,42): error C2338: static_assert failed: 'type check' [C:\Users\Kolo\AppData\Roaming\npm\node_modules\zeromq\build\zmq.vcxproj] npm ERR! (compiling source file '../binding.cc') npm ERR! C:\Users\Kolo\AppData\Local\node-gyp\Cache\21.6.2\include\node\v8-local-handle.h(253,42): npm ERR! the template instantiation context (the oldest one first) is npm ERR! C:\Users\Kolo\AppData\Roaming\npm\node_modules\zeromq\node_modules\nan\nan_callbacks_12_inl.h(175,41): npm ERR! see reference to function template instantiation 'v8::Local::Local(v8::Local)' being compiled npm ERR! C:\Users\Kolo\AppData\Roaming\npm\node_modules\zeromq\node_modules\nan\nan_callbacks_12_inl.h(175,13): npm ERR! see the first reference to 'v8::Local::Local' in 'Nan::imp::FunctionCallbackWrapper' npm ERR! gyp info it worked if it ends with ok npm ERR! gyp info using node-gyp@10.0.1 npm ERR! gyp info using node@21.6.2 | win32 | x64 npm ERR! gyp info find Python using Python version 3.12.2 found at "C:\Users\Kolo\AppData\Local\Programs\Python\Python312\python.exe" npm ERR! gyp info find VS using VS2022 (17.9.34616.47) found at: npm ERR! gyp info find VS "C:\Program Files\Microsoft Visual Studio\2022\Community" npm ERR! gyp info find VS run with --verbose for detailed information npm ERR! gyp info spawn C:\Users\Kolo\AppData\Local\Programs\Python\Python312\python.exe npm ERR! gyp info spawn args [ npm ERR! gyp info spawn args 'C:\Users\Kolo\AppData\Roaming\npm\node_modules\node-gyp\gyp\gyp_main.py', npm ERR! gyp info spawn args 'binding.gyp', npm ERR! gyp info spawn args '-f', npm ERR! gyp info spawn args 'msvs', npm ERR! gyp info spawn args '-I', npm ERR! gyp info spawn args 'C:\Users\Kolo\AppData\Roaming\npm\node_modules\zeromq\build\config.gypi', npm ERR! gyp info spawn args '-I', npm ERR! gyp info spawn args 'C:\Users\Kolo\AppData\Roaming\npm\node_modules\node-gyp\addon.gypi', npm ERR! gyp info spawn args '-I', npm ERR! gyp info spawn args 'C:\Users\Kolo\AppData\Local\node-gyp\Cache\21.6.2\include\node\common.gypi', npm ERR! gyp info spawn args '-Dlibrary=shared_library', npm ERR! gyp info spawn args '-Dvisibility=default', npm ERR! gyp info spawn args '-Dnode_root_dir=C:\Users\Kolo\AppData\Local\node-gyp\Cache\21.6.2', npm ERR! gyp info spawn args '-Dnode_gyp_dir=C:\Users\Kolo\AppData\Roaming\npm\node_modules\node-gyp', npm ERR! gyp info spawn args '-Dnode_lib_file=C:\\Users\\Kolo\\AppData\\Local\\node-gyp\\Cache\\21.6.2\\<(target_arch)\\node.lib', npm ERR! gyp info spawn args '-Dmodule_root_dir=C:\Users\Kolo\AppData\Roaming\npm\node_modules\zeromq', npm ERR! gyp info spawn args '-Dnode_engine=v8', npm ERR! gyp info spawn args '--depth=.', npm ERR! gyp info spawn args '--no-parallel', npm ERR! gyp info spawn args '--generator-output', npm ERR! gyp info spawn args 'C:\Users\Kolo\AppData\Roaming\npm\node_modules\zeromq\build', npm ERR! gyp info spawn args '-Goutput_dir=.' npm ERR! gyp info spawn args ] npm ERR! gyp info spawn C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Current\Bin\MSBuild.exe npm ERR! gyp info spawn args [ npm ERR! gyp info spawn args 'build\binding.sln', npm ERR! gyp info spawn args '/clp:Verbosity=minimal', npm ERR! gyp info spawn args '/nologo', npm ERR! gyp info spawn args '/p:Configuration=Release;Platform=x64' npm ERR! gyp info spawn args ] npm ERR! gyp ERR! build error npm ERR! gyp ERR! stack Error: C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Current\Bin\MSBuild.exe failed with exit code: 1 npm ERR! gyp ERR! stack at ChildProcess. (C:\Users\Kolo\AppData\Roaming\npm\node_modules\node-gyp\lib\build.js:209:23) npm ERR! gyp ERR! stack at ChildProcess.emit (node:events:519:28) npm ERR! gyp ERR! stack at ChildProcess._handle.onexit (node:internal/child_process:294:12) npm ERR! gyp ERR! System Windows_NT 10.0.22631 npm ERR! gyp ERR! command "C:\Program Files\nodejs\node.exe" "C:\Users\Kolo\AppData\Roaming\npm\node_modules\node-gyp\bin\node-gyp.js" "rebuild" npm ERR! gyp ERR! cwd C:\Users\Kolo\AppData\Roaming\npm\node_modules\zeromq npm ERR! gyp ERR! node -v v21.6.2 npm ERR! gyp ERR! node-gyp -v v10.0.1 npm ERR! gyp ERR! not ok npm ERR! gyp info it worked if it ends with ok npm ERR! gyp info using node-gyp@10.0.1 npm ERR! gyp info using node@21.6.2 | win32 | x64 npm ERR! gyp info find Python using Python version 3.12.2 found at "C:\Users\Kolo\AppData\Local\Programs\Python\Python312\python.exe" npm ERR! gyp info find VS using VS2022 (17.9.34616.47) found at: npm ERR! gyp info find VS "C:\Program Files\Microsoft Visual Studio\2022\Community" npm ERR! gyp info find VS run with --verbose for detailed information npm ERR! gyp info spawn C:\Users\Kolo\AppData\Local\Programs\Python\Python312\python.exe npm ERR! gyp info spawn args [ npm ERR! gyp info spawn args 'C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\gyp\gyp_main.py', npm ERR! gyp info spawn args 'binding.gyp', npm ERR! gyp info spawn args '-f', npm ERR! gyp info spawn args 'msvs', npm ERR! gyp info spawn args '-I', npm ERR! gyp info spawn args 'C:\Users\Kolo\AppData\Roaming\npm\node_modules\zeromq\build\config.gypi', npm ERR! gyp info spawn args '-I', npm ERR! gyp info spawn args 'C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\addon.gypi', npm ERR! gyp info spawn args '-I', npm ERR! gyp info spawn args 'C:\Users\Kolo\AppData\Local\node-gyp\Cache\21.6.2\include\node\common.gypi', npm ERR! gyp info spawn args '-Dlibrary=shared_library', npm ERR! gyp info spawn args '-Dvisibility=default', npm ERR! gyp info spawn args '-Dnode_root_dir=C:\Users\Kolo\AppData\Local\node-gyp\Cache\21.6.2', npm ERR! gyp info spawn args '-Dnode_gyp_dir=C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp', npm ERR! gyp info spawn args '-Dnode_lib_file=C:\\Users\\Kolo\\AppData\\Local\\node-gyp\\Cache\\21.6.2\\<(target_arch)\\node.lib', npm ERR! gyp info spawn args '-Dmodule_root_dir=C:\Users\Kolo\AppData\Roaming\npm\node_modules\zeromq', npm ERR! gyp info spawn args '-Dnode_engine=v8', npm ERR! gyp info spawn args '--depth=.', npm ERR! gyp info spawn args '--no-parallel', npm ERR! gyp info spawn args '--generator-output', npm ERR! gyp info spawn args 'C:\Users\Kolo\AppData\Roaming\npm\node_modules\zeromq\build', npm ERR! gyp info spawn args '-Goutput_dir=.' npm ERR! gyp info spawn args ] npm ERR! gyp info spawn C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Current\Bin\MSBuild.exe npm ERR! gyp info spawn args [ npm ERR! gyp info spawn args 'build\binding.sln', npm ERR! gyp info spawn args '/clp:Verbosity=minimal', npm ERR! gyp info spawn args '/nologo', npm ERR! gyp info spawn args '/p:Configuration=Release;Platform=x64' npm ERR! gyp info spawn args ] npm ERR! gyp ERR! build error npm ERR! gyp ERR! stack Error: C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Current\Bin\MSBuild.exe failed with exit code: 1 npm ERR! gyp ERR! stack at ChildProcess. (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\build.js:209:23) npm ERR! gyp ERR! stack at ChildProcess.emit (node:events:519:28) npm ERR! gyp ERR! stack at ChildProcess._handle.onexit (node:internal/child_process:294:12) npm ERR! gyp ERR! System Windows_NT 10.0.22631 npm ERR! gyp ERR! command "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" "rebuild" npm ERR! gyp ERR! cwd C:\Users\Kolo\AppData\Roaming\npm\node_modules\zeromq npm ERR! gyp ERR! node -v v21.6.2 npm ERR! gyp ERR! node-gyp -v v10.0.1 npm ERR! gyp ERR! not ok

npm ERR! A complete log of this run can be found in: C:\Users\Kolo\AppData\Local\npm-cache_logs\2024-02-24T23_40_00_007Z-debug-0.log vi These are my Visual Studio 22 with all the C++ Developmental Tools and Node.js tools (Optional also) +-- node-gyp@10.0.1 `-- zeromq@6.0.0-beta.19 node -v v21.6.2

Can anybody suggest whats the next step. Seems the issue is in installing zeromq@5 not 6, and it simply wont install.

[n-riesco]

@L4yman43 It's likely an issue with Node.js v21 (unstable). I've just tested the installation on Node.js 20 (linux) and it's working. Please, try with Node.js v20 and let me know if it doesn't work for you.

[scarela]

Tried with Node 18 and Node 20 on macOS, same issue.

[n-riesco]

@Evand3r I've just tested ijavascript using Node 20 on linux and it's working for me. Could you open a new issue and post the error message, please?

[scarela]

Sorry but it's too annoying, tried some of the steps here and some of the other stuff mentioned in this thread but still got different issues on different scenarios. I gave up and installed Deno, has a working kernel out of the box that just needs one command.

[n-riesco]

@Evand3r It's nice to see that Deno supports a jupyter kernel with their own bindings to zeromq!

[chusc123]

Tried with Node 18 and Node 20 on macOS, same issue.

Mine works great on MacOS with Node 20.

You should consider typing "!node -v" and "!which node" and "!which npm" and "!npm version" in your Jupyter notebook cells to make sure that your jupyter notebook environment is working from and installing on the same node version that you installed with home-brew for instance, because I had an issue on linux where I installed node 20 on the system directly, but anaconda was linked to it's own version of node 22 and thus I was getting the node 22 error and using node 22 even though I thought I was working from node 20.

[disarticulate]

I'm getting this still on node 20:

v20.17.0

1.71 npm error code 1
81.71 npm error path /opt/conda/lib/node_modules/ijavascript/node_modules/zeromq
81.71 npm error command failed
81.71 npm error command sh -c node-gyp-build || npm run build:libzmq
81.71 npm error make: Entering directory '/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/build'
81.71 npm error   ACTION binding_gyp_libzmq_target_prepare_build zmq/BUILD_SUCCESS
81.71 npm error Building libzmq for linux
81.71 npm error build_libzmq.sh: Building version 4.2.2 for architecture x64
81.71 npm error checking for a BSD-compatible install... /usr/bin/install -c
81.71 npm error checking whether build environment is sane... yes
81.71 npm error checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
81.71 npm error checking for gawk... no
81.71 npm error checking for mawk... mawk
81.71 npm error checking whether make sets $(MAKE)... yes
81.71 npm error checking whether make supports nested variables... yes
81.71 npm error checking whether UID '0' is supported by ustar format... yes
81.71 npm error checking whether GID '0' is supported by ustar format... yes
81.71 npm error checking how to create a ustar tar archive... gnutar
81.71 npm error checking whether make supports nested variables... (cached) yes
81.71 npm error checking for gcc... gcc
81.71 npm error checking whether the C compiler works... yes
81.71 npm error checking for C compiler default output file name... a.out
81.71 npm error checking for suffix of executables...
81.71 npm error checking whether we are cross compiling... no
81.71 npm error checking for suffix of object files... o
81.71 npm error checking whether we are using the GNU C compiler... yes
81.71 npm error checking whether gcc accepts -g... yes
81.71 npm error checking for gcc option to accept ISO C89... none needed
81.71 npm error checking whether gcc understands -c and -o together... yes
81.71 npm error checking for style of include used by make... GNU
81.71 npm error checking dependency style of gcc... gcc3
81.71 npm error checking whether C compiler accepts -std=gnu11... yes
81.71 npm error checking for g++... g++
81.71 npm error checking whether we are using the GNU C++ compiler... yes
81.71 npm error checking whether g++ accepts -g... yes
81.71 npm error checking dependency style of g++... gcc3
81.71 npm error checking whether g++ supports C++11 features by default... yes
81.71 npm error checking for a sed that does not truncate output... /usr/bin/sed
81.71 npm error checking whether to build with code coverage support... no
81.71 npm error checking for a sed that does not truncate output... (cached) /usr/bin/sed
81.71 npm error checking for gawk... (cached) mawk
81.71 npm error checking for pkg-config... /usr/bin/pkg-config
81.71 npm error checking pkg-config is at least version 0.9.0... yes
81.71 npm error checking for xmlto... no
81.71 npm error checking for asciidoc... no
81.71 npm error checking build system type... x86_64-unknown-linux-gnu
81.71 npm error checking host system type... x86_64-unknown-linux-gnu
81.71 npm error checking how to print strings... printf
81.71 npm error checking for a sed that does not truncate output... (cached) /usr/bin/sed
81.71 npm error checking for grep that handles long lines and -e... /usr/bin/grep
81.71 npm error checking for egrep... /usr/bin/grep -E
81.71 npm error checking for fgrep... /usr/bin/grep -F
81.71 npm error checking for ld used by gcc... /usr/bin/ld
81.71 npm error checking if the linker (/usr/bin/ld) is GNU ld... yes
81.71 npm error checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
81.71 npm error checking the name lister (/usr/bin/nm -B) interface... BSD nm
81.71 npm error checking whether ln -s works... yes
81.71 npm error checking the maximum length of command line arguments... 1572864
81.71 npm error checking whether the shell understands some XSI constructs... yes
81.71 npm error checking whether the shell understands "+="... yes
81.71 npm error checking how to convert x86_64-unknown-linux-gnu file names to x86_64-unknown-linux-gnu format... func_convert_file_noop
81.71 npm error checking how to convert x86_64-unknown-linux-gnu file names to toolchain format... func_convert_file_noop
81.71 npm error checking for /usr/bin/ld option to reload object files... -r
81.71 npm error checking for objdump... objdump
81.71 npm error checking how to recognize dependent libraries... pass_all
81.71 npm error checking for dlltool... dlltool
81.71 npm error checking how to associate runtime and link libraries... printf %s\n
81.71 npm error checking for ar... ar
81.71 npm error checking for archiver @FILE support... @
81.71 npm error checking for strip... strip
81.71 npm error checking for ranlib... ranlib
81.71 npm error checking command to parse /usr/bin/nm -B output from gcc object... ok
81.71 npm error checking for sysroot... no
81.71 npm error checking for mt... mt
81.71 npm error checking if mt is a manifest tool... no
81.71 npm error checking how to run the C preprocessor... gcc -E
81.71 npm error checking for ANSI C header files... yes
81.71 npm error checking for sys/types.h... yes
81.71 npm error checking for sys/stat.h... yes
81.71 npm error checking for stdlib.h... yes
81.71 npm error checking for string.h... yes
81.71 npm error checking for memory.h... yes
81.71 npm error checking for strings.h... yes
81.71 npm error checking for inttypes.h... yes
81.71 npm error checking for stdint.h... yes
81.71 npm error checking for unistd.h... yes
81.71 npm error checking for dlfcn.h... yes
81.71 npm error checking for objdir... .libs
81.71 npm error checking if gcc supports -fno-rtti -fno-exceptions... no
81.71 npm error checking for gcc option to produce PIC... -fPIC -DPIC
81.71 npm error checking if gcc PIC flag -fPIC -DPIC works... yes
81.71 npm error checking if gcc static flag -static works... yes
81.71 npm error checking if gcc supports -c -o file.o... yes
81.71 npm error checking if gcc supports -c -o file.o... (cached) yes
81.71 npm error checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
81.71 npm error checking dynamic linker characteristics... GNU/Linux ld.so
81.71 npm error checking how to hardcode library paths into programs... immediate
81.71 npm error checking whether stripping libraries is possible... yes
81.71 npm error checking if libtool supports shared libraries... yes
81.71 npm error checking whether to build shared libraries... no
81.71 npm error checking whether to build static libraries... yes
81.71 npm error checking how to run the C++ preprocessor... g++ -E
81.71 npm error checking for ld used by g++... /usr/bin/ld -m elf_x86_64
81.71 npm error checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes
81.71 npm error checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
81.71 npm error checking for g++ option to produce PIC... -fPIC -DPIC
81.71 npm error checking if g++ PIC flag -fPIC -DPIC works... yes
81.71 npm error checking if g++ static flag -static works... yes
81.71 npm error checking if g++ supports -c -o file.o... yes
81.71 npm error checking if g++ supports -c -o file.o... (cached) yes
81.71 npm error checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
81.71 npm error checking dynamic linker characteristics... (cached) GNU/Linux ld.so
81.71 npm error checking how to hardcode library paths into programs... immediate
81.71 npm error checking for valgrind... no
81.71 npm error checking whether the C compiler works... yes
81.71 npm error checking whether we are using Intel C compiler... no
81.71 npm error checking whether we are using Sun Studio C compiler... no
81.71 npm error checking whether we are using clang C compiler... no
81.71 npm error checking whether we are using gcc >= 4 C compiler... yes
81.71 npm error checking whether the C++ compiler works... yes
81.71 npm error checking whether we are using Intel C++ compiler... no
81.71 npm error checking whether we are using Sun Studio C++ compiler... no
81.71 npm error checking whether we are using clang C++ compiler... no
81.71 npm error checking whether we are using gcc >= 4 C++ compiler... yes
81.71 npm error checking whether to enable debugging information... no
81.71 npm error checking whether to enable code coverage... no
81.71 npm error checking if TIPC is available and supports nonblocking connect... no
81.71 npm error checking for library containing dladdr... none required
81.71 npm error checking for pthread_create in -lpthread... yes
81.71 npm error checking for clock_gettime in -lrt... yes
81.71 npm error checking whether C++ compiler supports -fvisibility=hidden... yes
81.71 npm error checking whether C++ compiler supports dso visibility... yes
81.71 npm error checking whether to build documentation... no
81.71 npm error checking whether to install manpages... no
81.71 npm error configure: Choosing polling system from 'kqueue epoll devpoll pollset poll select'...
81.71 npm error configure: Using 'epoll' polling system with CLOEXEC
81.71 npm error checking for ANSI C header files... (cached) yes
81.71 npm error checking errno.h usability... yes
81.71 npm error checking errno.h presence... yes
81.71 npm error checking for errno.h... yes
81.71 npm error checking time.h usability... yes
81.71 npm error checking time.h presence... yes
81.71 npm error checking for time.h... yes
81.71 npm error checking for unistd.h... (cached) yes
81.71 npm error checking limits.h usability... yes
81.71 npm error checking limits.h presence... yes
81.71 npm error checking for limits.h... yes
81.71 npm error checking stddef.h usability... yes
81.71 npm error checking stddef.h presence... yes
81.71 npm error checking for stddef.h... yes
81.71 npm error checking for stdlib.h... (cached) yes
81.71 npm error checking for string.h... (cached) yes
81.71 npm error checking arpa/inet.h usability... yes
81.71 npm error checking arpa/inet.h presence... yes
81.71 npm error checking for arpa/inet.h... yes
81.71 npm error checking netinet/tcp.h usability... yes
81.71 npm error checking netinet/tcp.h presence... yes
81.71 npm error checking for netinet/tcp.h... yes
81.71 npm error checking netinet/in.h usability... yes
81.71 npm error checking netinet/in.h presence... yes
81.71 npm error checking for netinet/in.h... yes
81.71 npm error checking sys/socket.h usability... yes
81.71 npm error checking sys/socket.h presence... yes
81.71 npm error checking for sys/socket.h... yes
81.71 npm error checking sys/time.h usability... yes
81.71 npm error checking sys/time.h presence... yes
81.71 npm error checking for sys/time.h... yes
81.71 npm error checking ifaddrs.h usability... yes
81.71 npm error checking ifaddrs.h presence... yes
81.71 npm error checking for ifaddrs.h... yes
81.71 npm error checking sys/uio.h usability... yes
81.71 npm error checking sys/uio.h presence... yes
81.71 npm error checking for sys/uio.h... yes
81.71 npm error checking sys/eventfd.h usability... yes
81.71 npm error checking sys/eventfd.h presence... yes
81.71 npm error checking for sys/eventfd.h... yes
81.71 npm error checking whether EFD_CLOEXEC is supported... yes
81.71 npm error checking whether SO_PEERCRED is declared... yes
81.71 npm error checking whether LOCAL_PEERCRED is declared... no
81.71 npm error checking for stdbool.h that conforms to C99... no
81.71 npm error checking for _Bool... no
81.71 npm error checking for an ANSI C-conforming const... yes
81.71 npm error checking for inline... inline
81.71 npm error checking for size_t... yes
81.71 npm error checking for ssize_t... yes
81.71 npm error checking whether time.h and sys/time.h may both be included... yes
81.71 npm error checking for uint32_t... yes
81.71 npm error checking for working volatile... yes
81.71 npm error configure: Using tweetnacl for CURVE security
81.71 npm error checking "with_norm_ext = no"... no
81.71 npm error checking how to enable additional warnings for C++ compiler... -Wall
81.71 npm error checking how to turn warnings to errors in C++ compiler... -Werror
81.71 npm error checking whether compiler supports __atomic_Xxx intrinsics... yes
81.71 npm error checking return type of signal handlers... void
81.71 npm error checking for perror... yes
81.71 npm error checking for gettimeofday... yes
81.71 npm error checking for clock_gettime... yes
81.71 npm error checking for memset... no
81.71 npm error checking for socket... yes
81.71 npm error checking for getifaddrs... yes
81.71 npm error checking for freeifaddrs... yes
81.71 npm error checking for fork... no
81.71 npm error checking for posix_memalign... no
81.71 npm error checking for mkdtemp... yes
81.71 npm error checking alloca.h usability... yes
81.71 npm error checking alloca.h presence... yes
81.71 npm error checking for alloca.h... yes
81.71 npm error checking whether SOCK_CLOEXEC is supported... yes
81.71 npm error checking whether SO_KEEPALIVE is supported... yes
81.71 npm error checking whether TCP_KEEPCNT is supported... yes
81.71 npm error checking whether TCP_KEEPIDLE is supported... yes
81.71 npm error checking whether TCP_KEEPINTVL is supported... yes
81.71 npm error checking whether TCP_KEEPALIVE is supported... no
81.71 npm error checking for ./.git... no
81.71 npm error configure: Building stable and legacy API (no draft API)
81.71 npm error checking for LIBUNWIND... no
81.71 npm error checking that generated files are newer than configure... done
81.71 npm error configure: creating ./config.status
81.71 npm error config.status: creating Makefile
81.71 npm error config.status: creating src/libzmq.pc
81.71 npm error config.status: creating doc/Makefile
81.71 npm error config.status: creating builds/Makefile
81.71 npm error config.status: creating builds/msvc/Makefile
81.71 npm error config.status: creating src/platform.hpp
81.71 npm error config.status: executing depfiles commands
81.71 npm error config.status: executing libtool commands
81.71 npm error make[1]: Entering directory '/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/zeromq-4.2.2'
81.71 npm error Making all in doc
81.71 npm error make[2]: Entering directory '/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/zeromq-4.2.2/doc'
81.71 npm error make[2]: Nothing to be done for 'all'.
81.71 npm error make[2]: Leaving directory '/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/zeromq-4.2.2/doc'
81.71 npm error make[2]: Entering directory '/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/zeromq-4.2.2'
81.71 npm error   CXX      src/src_libzmq_la-address.lo
81.71 npm error   CXX      src/src_libzmq_la-client.lo
81.71 npm error   CXX      src/src_libzmq_la-clock.lo
81.71 npm error   CXX      src/src_libzmq_la-ctx.lo
81.71 npm error   CXX      src/src_libzmq_la-curve_client.lo
81.71 npm error   CXX      src/src_libzmq_la-curve_server.lo
81.71 npm error   CXX      src/src_libzmq_la-dealer.lo
81.71 npm error   CXX      src/src_libzmq_la-devpoll.lo
81.71 npm error   CXX      src/src_libzmq_la-dgram.lo
81.71 npm error   CXX      src/src_libzmq_la-dish.lo
81.71 npm error   CXX      src/src_libzmq_la-dist.lo
81.71 npm error   CXX      src/src_libzmq_la-epoll.lo
81.71 npm error   CXX      src/src_libzmq_la-err.lo
81.71 npm error   CXX      src/src_libzmq_la-fq.lo
81.71 npm error   CXX      src/src_libzmq_la-gather.lo
81.71 npm error   CXX      src/src_libzmq_la-gssapi_mechanism_base.lo
81.71 npm error   CXX      src/src_libzmq_la-gssapi_client.lo
81.71 npm error   CXX      src/src_libzmq_la-gssapi_server.lo
81.71 npm error   CXX      src/src_libzmq_la-io_object.lo
81.71 npm error   CXX      src/src_libzmq_la-io_thread.lo
81.71 npm error   CXX      src/src_libzmq_la-ip.lo
81.71 npm error   CXX      src/src_libzmq_la-ipc_address.lo
81.71 npm error   CXX      src/src_libzmq_la-ipc_connecter.lo
81.71 npm error   CXX      src/src_libzmq_la-ipc_listener.lo
81.71 npm error   CXX      src/src_libzmq_la-kqueue.lo
81.71 npm error   CXX      src/src_libzmq_la-lb.lo
81.71 npm error   CXX      src/src_libzmq_la-mailbox.lo
81.71 npm error   CXX      src/src_libzmq_la-mailbox_safe.lo
81.71 npm error   CXX      src/src_libzmq_la-mechanism.lo
81.71 npm error   CXX      src/src_libzmq_la-metadata.lo
81.71 npm error   CXX      src/src_libzmq_la-msg.lo
81.71 npm error   CXX      src/src_libzmq_la-mtrie.lo
81.71 npm error   CXX      src/src_libzmq_la-norm_engine.lo
81.71 npm error   CXX      src/src_libzmq_la-null_mechanism.lo
81.71 npm error   CXX      src/src_libzmq_la-object.lo
81.71 npm error   CXX      src/src_libzmq_la-options.lo
81.71 npm error   CXX      src/src_libzmq_la-own.lo
81.71 npm error   CXX      src/src_libzmq_la-pair.lo
81.71 npm error   CXX      src/src_libzmq_la-pgm_receiver.lo
81.71 npm error   CXX      src/src_libzmq_la-pgm_sender.lo
81.71 npm error   CXX      src/src_libzmq_la-pgm_socket.lo
81.71 npm error   CXX      src/src_libzmq_la-pipe.lo
81.71 npm error   CXX      src/src_libzmq_la-plain_client.lo
81.71 npm error   CXX      src/src_libzmq_la-plain_server.lo
81.71 npm error   CXX      src/src_libzmq_la-poll.lo
81.71 npm error   CXX      src/src_libzmq_la-poller_base.lo
81.71 npm error   CXX      src/src_libzmq_la-pollset.lo
81.71 npm error   CXX      src/src_libzmq_la-precompiled.lo
81.71 npm error   CXX      src/src_libzmq_la-proxy.lo
81.71 npm error   CXX      src/src_libzmq_la-pub.lo
81.71 npm error   CXX      src/src_libzmq_la-pull.lo
81.71 npm error   CXX      src/src_libzmq_la-push.lo
81.71 npm error   CXX      src/src_libzmq_la-radio.lo
81.71 npm error   CXX      src/src_libzmq_la-random.lo
81.71 npm error   CXX      src/src_libzmq_la-raw_decoder.lo
81.71 npm error   CXX      src/src_libzmq_la-raw_encoder.lo
81.71 npm error   CXX      src/src_libzmq_la-reaper.lo
81.71 npm error   CXX      src/src_libzmq_la-rep.lo
81.71 npm error   CXX      src/src_libzmq_la-req.lo
81.71 npm error   CXX      src/src_libzmq_la-router.lo
81.71 npm error   CXX      src/src_libzmq_la-scatter.lo
81.71 npm error   CXX      src/src_libzmq_la-select.lo
81.71 npm error   CXX      src/src_libzmq_la-server.lo
81.71 npm error   CXX      src/src_libzmq_la-session_base.lo
81.71 npm error   CXX      src/src_libzmq_la-signaler.lo
81.71 npm error   CXX      src/src_libzmq_la-socket_base.lo
81.71 npm error   CXX      src/src_libzmq_la-socks.lo
81.71 npm error   CXX      src/src_libzmq_la-socks_connecter.lo
81.71 npm error   CXX      src/src_libzmq_la-stream.lo
81.71 npm error   CXX      src/src_libzmq_la-stream_engine.lo
81.71 npm error   CXX      src/src_libzmq_la-sub.lo
81.71 npm error   CXX      src/src_libzmq_la-tcp.lo
81.71 npm error   CXX      src/src_libzmq_la-tcp_address.lo
81.71 npm error   CXX      src/src_libzmq_la-tcp_connecter.lo
81.71 npm error   CXX      src/src_libzmq_la-tcp_listener.lo
81.71 npm error   CXX      src/src_libzmq_la-thread.lo
81.71 npm error   CXX      src/src_libzmq_la-timers.lo
81.71 npm error   CXX      src/src_libzmq_la-tipc_address.lo
81.71 npm error   CXX      src/src_libzmq_la-tipc_connecter.lo
81.71 npm error   CXX      src/src_libzmq_la-tipc_listener.lo
81.71 npm error   CXX      src/src_libzmq_la-trie.lo
81.71 npm error   CXX      src/src_libzmq_la-udp_address.lo
81.71 npm error   CXX      src/src_libzmq_la-udp_engine.lo
81.71 npm error   CXX      src/src_libzmq_la-v1_decoder.lo
81.71 npm error   CXX      src/src_libzmq_la-v2_decoder.lo
81.71 npm error   CXX      src/src_libzmq_la-v1_encoder.lo
81.71 npm error   CXX      src/src_libzmq_la-v2_encoder.lo
81.71 npm error   CXX      src/src_libzmq_la-vmci.lo
81.71 npm error   CXX      src/src_libzmq_la-vmci_address.lo
81.71 npm error   CXX      src/src_libzmq_la-vmci_connecter.lo
81.71 npm error   CXX      src/src_libzmq_la-vmci_listener.lo
81.71 npm error   CXX      src/src_libzmq_la-xpub.lo
81.71 npm error   CXX      src/src_libzmq_la-xsub.lo
81.71 npm error   CXX      src/src_libzmq_la-zmq.lo
81.71 npm error   CXX      src/src_libzmq_la-zmq_utils.lo
81.71 npm error   CXX      src/src_libzmq_la-decoder_allocators.lo
81.71 npm error   CXX      src/src_libzmq_la-socket_poller.lo
81.71 npm error   CC       src/src_libzmq_la-tweetnacl.lo
81.71 npm error   CXX      tools/curve_keygen.o
81.71 npm error   CXX      perf/local_lat.o
81.71 npm error   CXX      perf/remote_lat.o
81.71 npm error   CXX      perf/local_thr.o
81.71 npm error   CXX      perf/remote_thr.o
81.71 npm error   CXX      perf/inproc_lat.o
81.71 npm error   CXX      perf/inproc_thr.o
81.71 npm error   CXXLD    src/libzmq.la
81.71 npm error   CXXLD    tools/curve_keygen
81.71 npm error   CXXLD    perf/local_lat
81.71 npm error   CXXLD    perf/remote_lat
81.71 npm error   CXXLD    perf/local_thr
81.71 npm error   CXXLD    perf/remote_thr
81.71 npm error   CXXLD    perf/inproc_lat
81.71 npm error   CXXLD    perf/inproc_thr
81.71 npm error make[2]: Leaving directory '/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/zeromq-4.2.2'
81.71 npm error make[1]: Leaving directory '/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/zeromq-4.2.2'
81.71 npm error make[1]: Entering directory '/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/zeromq-4.2.2'
81.71 npm error Making install in doc
81.71 npm error make[2]: Entering directory '/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/zeromq-4.2.2/doc'
81.71 npm error make[3]: Entering directory '/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/zeromq-4.2.2/doc'
81.71 npm error make[3]: Nothing to be done for 'install-exec-am'.
81.71 npm error make[3]: Leaving directory '/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/zeromq-4.2.2/doc'
81.71 npm error make[2]: Leaving directory '/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/zeromq-4.2.2/doc'
81.71 npm error make[2]: Entering directory '/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/zeromq-4.2.2'
81.71 npm error make[3]: Entering directory '/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/zeromq-4.2.2'
81.71 npm error  /usr/bin/mkdir -p '/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/lib'
81.71 npm error  /bin/bash ./libtool   --mode=install /usr/bin/install -c   src/libzmq.la '/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/lib'
81.71 npm error libtool: install: /usr/bin/install -c src/.libs/libzmq.lai /opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/lib/libzmq.la
81.71 npm error libtool: install: /usr/bin/install -c src/.libs/libzmq.a /opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/lib/libzmq.a
81.71 npm error libtool: install: chmod 644 /opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/lib/libzmq.a
81.71 npm error libtool: install: ranlib /opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/lib/libzmq.a
81.71 npm error libtool: finish: PATH="/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/build/node_gyp_bins:/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/node_modules/.bin:/opt/conda/lib/node_modules/ijavascript/node_modules/node_modules/.bin:/opt/conda/lib/node_modules/ijavascript/node_modules/.bin:/opt/conda/lib/node_modules/node_modules/.bin:/opt/conda/lib/node_modules/.bin:/opt/conda/node_modules/.bin:/opt/node_modules/.bin:/node_modules/.bin:/opt/conda/lib/node_modules/npm/node_modules/@npmcli/run-script/lib/node-gyp-bin:/opt/conda/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/sbin" ldconfig -n /opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/lib
81.71 npm error ----------------------------------------------------------------------
81.71 npm error Libraries have been installed in:
81.71 npm error    /opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/lib
81.71 npm error
81.71 npm error If you ever happen to want to link against installed libraries
81.71 npm error in a given directory, LIBDIR, you must either use libtool, and
81.71 npm error specify the full pathname of the library, or use the `-LLIBDIR'
81.71 npm error flag during linking and do at least one of the following:
81.71 npm error    - add LIBDIR to the `LD_LIBRARY_PATH' environment variable
81.71 npm error      during execution
81.71 npm error    - add LIBDIR to the `LD_RUN_PATH' environment variable
81.71 npm error      during linking
81.71 npm error    - use the `-Wl,-rpath -Wl,LIBDIR' linker flag
81.71 npm error    - have your system administrator add LIBDIR to `/etc/ld.so.conf'
81.71 npm error
81.71 npm error See any operating system documentation about shared libraries for
81.71 npm error more information, such as the ld(1) and ld.so(8) manual pages.
81.71 npm error ----------------------------------------------------------------------
81.71 npm error  /usr/bin/mkdir -p '/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/bin'
81.71 npm error   /bin/bash ./libtool   --mode=install /usr/bin/install -c tools/curve_keygen '/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/bin'
81.71 npm error libtool: install: /usr/bin/install -c tools/curve_keygen /opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/bin/curve_keygen
81.71 npm error  /usr/bin/mkdir -p '/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/include'
81.71 npm error  /usr/bin/install -c -m 644 include/zmq.h include/zmq_utils.h '/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/include'
81.71 npm error  /usr/bin/mkdir -p '/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/lib/pkgconfig'
81.71 npm error  /usr/bin/install -c -m 644 src/libzmq.pc '/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/lib/pkgconfig'
81.71 npm error make[3]: Leaving directory '/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/zeromq-4.2.2'
81.71 npm error make[2]: Leaving directory '/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/zeromq-4.2.2'
81.71 npm error make[1]: Leaving directory '/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/zeromq-4.2.2'
81.71 npm error   TOUCH Release/obj.target/libzmq.stamp
81.71 npm error   CXX(target) Release/obj.target/zmq/binding.o
81.71 npm error make: Leaving directory '/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/build'
81.71 npm error
81.71 npm error > zeromq@5.3.1 build:libzmq
81.71 npm error > node-gyp rebuild
81.71 npm error
81.71 npm error
81.71 npm error make: Entering directory '/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/build'
81.71 npm error   ACTION binding_gyp_libzmq_target_prepare_build zmq/BUILD_SUCCESS
81.71 npm error Building libzmq for linux
81.71 npm error build_libzmq.sh: Building version 4.2.2 for architecture x64
81.71 npm error checking for a BSD-compatible install... /usr/bin/install -c
81.71 npm error checking whether build environment is sane... yes
81.71 npm error checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
81.71 npm error checking for gawk... no
81.71 npm error checking for mawk... mawk
81.71 npm error checking whether make sets $(MAKE)... yes
81.71 npm error checking whether make supports nested variables... yes
81.71 npm error checking whether UID '0' is supported by ustar format... yes
81.71 npm error checking whether GID '0' is supported by ustar format... yes
81.71 npm error checking how to create a ustar tar archive... gnutar
81.71 npm error checking whether make supports nested variables... (cached) yes
81.71 npm error checking for gcc... gcc
81.71 npm error checking whether the C compiler works... yes
81.71 npm error checking for C compiler default output file name... a.out
81.71 npm error checking for suffix of executables...
81.71 npm error checking whether we are cross compiling... no
81.71 npm error checking for suffix of object files... o
81.71 npm error checking whether we are using the GNU C compiler... yes
81.71 npm error checking whether gcc accepts -g... yes
81.71 npm error checking for gcc option to accept ISO C89... none needed
81.71 npm error checking whether gcc understands -c and -o together... yes
81.71 npm error checking for style of include used by make... GNU
81.71 npm error checking dependency style of gcc... gcc3
81.71 npm error checking whether C compiler accepts -std=gnu11... yes
81.71 npm error checking for g++... g++
81.71 npm error checking whether we are using the GNU C++ compiler... yes
81.71 npm error checking whether g++ accepts -g... yes
81.71 npm error checking dependency style of g++... gcc3
81.71 npm error checking whether g++ supports C++11 features by default... yes
81.71 npm error checking for a sed that does not truncate output... /usr/bin/sed
81.71 npm error checking whether to build with code coverage support... no
81.71 npm error checking for a sed that does not truncate output... (cached) /usr/bin/sed
81.71 npm error checking for gawk... (cached) mawk
81.71 npm error checking for pkg-config... /usr/bin/pkg-config
81.71 npm error checking pkg-config is at least version 0.9.0... yes
81.71 npm error checking for xmlto... no
81.71 npm error checking for asciidoc... no
81.71 npm error checking build system type... x86_64-unknown-linux-gnu
81.71 npm error checking host system type... x86_64-unknown-linux-gnu
81.71 npm error checking how to print strings... printf
81.71 npm error checking for a sed that does not truncate output... (cached) /usr/bin/sed
81.71 npm error checking for grep that handles long lines and -e... /usr/bin/grep
81.71 npm error checking for egrep... /usr/bin/grep -E
81.71 npm error checking for fgrep... /usr/bin/grep -F
81.71 npm error checking for ld used by gcc... /usr/bin/ld
81.71 npm error checking if the linker (/usr/bin/ld) is GNU ld... yes
81.71 npm error checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
81.71 npm error checking the name lister (/usr/bin/nm -B) interface... BSD nm
81.71 npm error checking whether ln -s works... yes
81.71 npm error checking the maximum length of command line arguments... 1572864
81.71 npm error checking whether the shell understands some XSI constructs... yes
81.71 npm error checking whether the shell understands "+="... yes
81.71 npm error checking how to convert x86_64-unknown-linux-gnu file names to x86_64-unknown-linux-gnu format... func_convert_file_noop
81.71 npm error checking how to convert x86_64-unknown-linux-gnu file names to toolchain format... func_convert_file_noop
81.71 npm error checking for /usr/bin/ld option to reload object files... -r
81.71 npm error checking for objdump... objdump
81.71 npm error checking how to recognize dependent libraries... pass_all
81.71 npm error checking for dlltool... dlltool
81.71 npm error checking how to associate runtime and link libraries... printf %s\n
81.71 npm error checking for ar... ar
81.71 npm error checking for archiver @FILE support... @
81.71 npm error checking for strip... strip
81.71 npm error checking for ranlib... ranlib
81.71 npm error checking command to parse /usr/bin/nm -B output from gcc object... ok
81.71 npm error checking for sysroot... no
81.71 npm error checking for mt... mt
81.71 npm error checking if mt is a manifest tool... no
81.71 npm error checking how to run the C preprocessor... gcc -E
81.71 npm error checking for ANSI C header files... yes
81.71 npm error checking for sys/types.h... yes
81.71 npm error checking for sys/stat.h... yes
81.71 npm error checking for stdlib.h... yes
81.71 npm error checking for string.h... yes
81.71 npm error checking for memory.h... yes
81.71 npm error checking for strings.h... yes
81.71 npm error checking for inttypes.h... yes
81.71 npm error checking for stdint.h... yes
81.71 npm error checking for unistd.h... yes
81.71 npm error checking for dlfcn.h... yes
81.71 npm error checking for objdir... .libs
81.71 npm error checking if gcc supports -fno-rtti -fno-exceptions... no
81.71 npm error checking for gcc option to produce PIC... -fPIC -DPIC
81.71 npm error checking if gcc PIC flag -fPIC -DPIC works... yes
81.71 npm error checking if gcc static flag -static works... yes
81.71 npm error checking if gcc supports -c -o file.o... yes
81.71 npm error checking if gcc supports -c -o file.o... (cached) yes
81.71 npm error checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
81.71 npm error checking dynamic linker characteristics... GNU/Linux ld.so
81.71 npm error checking how to hardcode library paths into programs... immediate
81.71 npm error checking whether stripping libraries is possible... yes
81.71 npm error checking if libtool supports shared libraries... yes
81.71 npm error checking whether to build shared libraries... no
81.71 npm error checking whether to build static libraries... yes
81.71 npm error checking how to run the C++ preprocessor... g++ -E
81.71 npm error checking for ld used by g++... /usr/bin/ld -m elf_x86_64
81.71 npm error checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes
81.71 npm error checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
81.71 npm error checking for g++ option to produce PIC... -fPIC -DPIC
81.71 npm error checking if g++ PIC flag -fPIC -DPIC works... yes
81.71 npm error checking if g++ static flag -static works... yes
81.71 npm error checking if g++ supports -c -o file.o... yes
81.71 npm error checking if g++ supports -c -o file.o... (cached) yes
81.71 npm error checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
81.71 npm error checking dynamic linker characteristics... (cached) GNU/Linux ld.so
81.71 npm error checking how to hardcode library paths into programs... immediate
81.71 npm error checking for valgrind... no
81.71 npm error checking whether the C compiler works... yes
81.71 npm error checking whether we are using Intel C compiler... no
81.71 npm error checking whether we are using Sun Studio C compiler... no
81.71 npm error checking whether we are using clang C compiler... no
81.71 npm error checking whether we are using gcc >= 4 C compiler... yes
81.71 npm error checking whether the C++ compiler works... yes
81.71 npm error checking whether we are using Intel C++ compiler... no
81.71 npm error checking whether we are using Sun Studio C++ compiler... no
81.71 npm error checking whether we are using clang C++ compiler... no
81.71 npm error checking whether we are using gcc >= 4 C++ compiler... yes
81.71 npm error checking whether to enable debugging information... no
81.71 npm error checking whether to enable code coverage... no
81.71 npm error checking if TIPC is available and supports nonblocking connect... no
81.71 npm error checking for library containing dladdr... none required
81.71 npm error checking for pthread_create in -lpthread... yes
81.71 npm error checking for clock_gettime in -lrt... yes
81.71 npm error checking whether C++ compiler supports -fvisibility=hidden... yes
81.71 npm error checking whether C++ compiler supports dso visibility... yes
81.71 npm error checking whether to build documentation... no
81.71 npm error checking whether to install manpages... no
81.71 npm error configure: Choosing polling system from 'kqueue epoll devpoll pollset poll select'...
81.71 npm error configure: Using 'epoll' polling system with CLOEXEC
81.71 npm error checking for ANSI C header files... (cached) yes
81.71 npm error checking errno.h usability... yes
81.71 npm error checking errno.h presence... yes
81.71 npm error checking for errno.h... yes
81.71 npm error checking time.h usability... yes
81.71 npm error checking time.h presence... yes
81.71 npm error checking for time.h... yes
81.71 npm error checking for unistd.h... (cached) yes
81.71 npm error checking limits.h usability... yes
81.71 npm error checking limits.h presence... yes
81.71 npm error checking for limits.h... yes
81.71 npm error checking stddef.h usability... yes
81.71 npm error checking stddef.h presence... yes
81.71 npm error checking for stddef.h... yes
81.71 npm error checking for stdlib.h... (cached) yes
81.71 npm error checking for string.h... (cached) yes
81.71 npm error checking arpa/inet.h usability... yes
81.71 npm error checking arpa/inet.h presence... yes
81.71 npm error checking for arpa/inet.h... yes
81.71 npm error checking netinet/tcp.h usability... yes
81.71 npm error checking netinet/tcp.h presence... yes
81.71 npm error checking for netinet/tcp.h... yes
81.71 npm error checking netinet/in.h usability... yes
81.71 npm error checking netinet/in.h presence... yes
81.71 npm error checking for netinet/in.h... yes
81.71 npm error checking sys/socket.h usability... yes
81.71 npm error checking sys/socket.h presence... yes
81.71 npm error checking for sys/socket.h... yes
81.71 npm error checking sys/time.h usability... yes
81.71 npm error checking sys/time.h presence... yes
81.71 npm error checking for sys/time.h... yes
81.71 npm error checking ifaddrs.h usability... yes
81.71 npm error checking ifaddrs.h presence... yes
81.71 npm error checking for ifaddrs.h... yes
81.71 npm error checking sys/uio.h usability... yes
81.71 npm error checking sys/uio.h presence... yes
81.71 npm error checking for sys/uio.h... yes
81.71 npm error checking sys/eventfd.h usability... yes
81.71 npm error checking sys/eventfd.h presence... yes
81.71 npm error checking for sys/eventfd.h... yes
81.71 npm error checking whether EFD_CLOEXEC is supported... yes
81.71 npm error checking whether SO_PEERCRED is declared... yes
81.71 npm error checking whether LOCAL_PEERCRED is declared... no
81.71 npm error checking for stdbool.h that conforms to C99... no
81.71 npm error checking for _Bool... no
81.71 npm error checking for an ANSI C-conforming const... yes
81.71 npm error checking for inline... inline
81.71 npm error checking for size_t... yes
81.71 npm error checking for ssize_t... yes
81.71 npm error checking whether time.h and sys/time.h may both be included... yes
81.71 npm error checking for uint32_t... yes
81.71 npm error checking for working volatile... yes
81.71 npm error configure: Using tweetnacl for CURVE security
81.71 npm error checking "with_norm_ext = no"... no
81.71 npm error checking how to enable additional warnings for C++ compiler... -Wall
81.71 npm error checking how to turn warnings to errors in C++ compiler... -Werror
81.71 npm error checking whether compiler supports __atomic_Xxx intrinsics... yes
81.71 npm error checking return type of signal handlers... void
81.71 npm error checking for perror... yes
81.71 npm error checking for gettimeofday... yes
81.71 npm error checking for clock_gettime... yes
81.71 npm error checking for memset... no
81.71 npm error checking for socket... yes
81.71 npm error checking for getifaddrs... yes
81.71 npm error checking for freeifaddrs... yes
81.71 npm error checking for fork... no
81.71 npm error checking for posix_memalign... no
81.71 npm error checking for mkdtemp... yes
81.71 npm error checking alloca.h usability... yes
81.71 npm error checking alloca.h presence... yes
81.71 npm error checking for alloca.h... yes
81.71 npm error checking whether SOCK_CLOEXEC is supported... yes
81.71 npm error checking whether SO_KEEPALIVE is supported... yes
81.71 npm error checking whether TCP_KEEPCNT is supported... yes
81.71 npm error checking whether TCP_KEEPIDLE is supported... yes
81.71 npm error checking whether TCP_KEEPINTVL is supported... yes
81.71 npm error checking whether TCP_KEEPALIVE is supported... no
81.71 npm error checking for ./.git... no
81.71 npm error configure: Building stable and legacy API (no draft API)
81.71 npm error checking for LIBUNWIND... no
81.71 npm error checking that generated files are newer than configure... done
81.71 npm error configure: creating ./config.status
81.71 npm error config.status: creating Makefile
81.71 npm error config.status: creating src/libzmq.pc
81.71 npm error config.status: creating doc/Makefile
81.71 npm error config.status: creating builds/Makefile
81.71 npm error config.status: creating builds/msvc/Makefile
81.71 npm error config.status: creating src/platform.hpp
81.71 npm error config.status: executing depfiles commands
81.71 npm error config.status: executing libtool commands
81.71 npm error make[1]: Entering directory '/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/zeromq-4.2.2'
81.71 npm error Making all in doc
81.71 npm error make[2]: Entering directory '/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/zeromq-4.2.2/doc'
81.71 npm error make[2]: Nothing to be done for 'all'.
81.71 npm error make[2]: Leaving directory '/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/zeromq-4.2.2/doc'
81.71 npm error make[2]: Entering directory '/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/zeromq-4.2.2'
81.71 npm error   CXX      src/src_libzmq_la-address.lo
81.71 npm error   CXX      src/src_libzmq_la-client.lo
81.71 npm error   CXX      src/src_libzmq_la-clock.lo
81.71 npm error   CXX      src/src_libzmq_la-ctx.lo
81.71 npm error   CXX      src/src_libzmq_la-curve_client.lo
81.71 npm error   CXX      src/src_libzmq_la-curve_server.lo
81.71 npm error   CXX      src/src_libzmq_la-dealer.lo
81.71 npm error   CXX      src/src_libzmq_la-devpoll.lo
81.71 npm error   CXX      src/src_libzmq_la-dgram.lo
81.71 npm error   CXX      src/src_libzmq_la-dish.lo
81.71 npm error   CXX      src/src_libzmq_la-dist.lo
81.71 npm error   CXX      src/src_libzmq_la-epoll.lo
81.71 npm error   CXX      src/src_libzmq_la-err.lo
81.71 npm error   CXX      src/src_libzmq_la-fq.lo
81.71 npm error   CXX      src/src_libzmq_la-gather.lo
81.71 npm error   CXX      src/src_libzmq_la-gssapi_mechanism_base.lo
81.71 npm error   CXX      src/src_libzmq_la-gssapi_client.lo
81.71 npm error   CXX      src/src_libzmq_la-gssapi_server.lo
81.71 npm error   CXX      src/src_libzmq_la-io_object.lo
81.71 npm error   CXX      src/src_libzmq_la-io_thread.lo
81.71 npm error   CXX      src/src_libzmq_la-ip.lo
81.71 npm error   CXX      src/src_libzmq_la-ipc_address.lo
81.71 npm error   CXX      src/src_libzmq_la-ipc_connecter.lo
81.71 npm error   CXX      src/src_libzmq_la-ipc_listener.lo
81.71 npm error   CXX      src/src_libzmq_la-kqueue.lo
81.71 npm error   CXX      src/src_libzmq_la-lb.lo
81.71 npm error   CXX      src/src_libzmq_la-mailbox.lo
81.71 npm error   CXX      src/src_libzmq_la-mailbox_safe.lo
81.71 npm error   CXX      src/src_libzmq_la-mechanism.lo
81.71 npm error   CXX      src/src_libzmq_la-metadata.lo
81.71 npm error   CXX      src/src_libzmq_la-msg.lo
81.71 npm error   CXX      src/src_libzmq_la-mtrie.lo
81.71 npm error   CXX      src/src_libzmq_la-norm_engine.lo
81.71 npm error   CXX      src/src_libzmq_la-null_mechanism.lo
81.71 npm error   CXX      src/src_libzmq_la-object.lo
81.71 npm error   CXX      src/src_libzmq_la-options.lo
81.71 npm error   CXX      src/src_libzmq_la-own.lo
81.71 npm error   CXX      src/src_libzmq_la-pair.lo
81.71 npm error   CXX      src/src_libzmq_la-pgm_receiver.lo
81.71 npm error   CXX      src/src_libzmq_la-pgm_sender.lo
81.71 npm error   CXX      src/src_libzmq_la-pgm_socket.lo
81.71 npm error   CXX      src/src_libzmq_la-pipe.lo
81.71 npm error   CXX      src/src_libzmq_la-plain_client.lo
81.71 npm error   CXX      src/src_libzmq_la-plain_server.lo
81.71 npm error   CXX      src/src_libzmq_la-poll.lo
81.71 npm error   CXX      src/src_libzmq_la-poller_base.lo
81.71 npm error   CXX      src/src_libzmq_la-pollset.lo
81.71 npm error   CXX      src/src_libzmq_la-precompiled.lo
81.71 npm error   CXX      src/src_libzmq_la-proxy.lo
81.71 npm error   CXX      src/src_libzmq_la-pub.lo
81.71 npm error   CXX      src/src_libzmq_la-pull.lo
81.71 npm error   CXX      src/src_libzmq_la-push.lo
81.71 npm error   CXX      src/src_libzmq_la-radio.lo
81.71 npm error   CXX      src/src_libzmq_la-random.lo
81.71 npm error   CXX      src/src_libzmq_la-raw_decoder.lo
81.71 npm error   CXX      src/src_libzmq_la-raw_encoder.lo
81.71 npm error   CXX      src/src_libzmq_la-reaper.lo
81.71 npm error   CXX      src/src_libzmq_la-rep.lo
81.71 npm error   CXX      src/src_libzmq_la-req.lo
81.71 npm error   CXX      src/src_libzmq_la-router.lo
81.71 npm error   CXX      src/src_libzmq_la-scatter.lo
81.71 npm error   CXX      src/src_libzmq_la-select.lo
81.71 npm error   CXX      src/src_libzmq_la-server.lo
81.71 npm error   CXX      src/src_libzmq_la-session_base.lo
81.71 npm error   CXX      src/src_libzmq_la-signaler.lo
81.71 npm error   CXX      src/src_libzmq_la-socket_base.lo
81.71 npm error   CXX      src/src_libzmq_la-socks.lo
81.71 npm error   CXX      src/src_libzmq_la-socks_connecter.lo
81.71 npm error   CXX      src/src_libzmq_la-stream.lo
81.71 npm error   CXX      src/src_libzmq_la-stream_engine.lo
81.71 npm error   CXX      src/src_libzmq_la-sub.lo
81.71 npm error   CXX      src/src_libzmq_la-tcp.lo
81.71 npm error   CXX      src/src_libzmq_la-tcp_address.lo
81.71 npm error   CXX      src/src_libzmq_la-tcp_connecter.lo
81.71 npm error   CXX      src/src_libzmq_la-tcp_listener.lo
81.71 npm error   CXX      src/src_libzmq_la-thread.lo
81.71 npm error   CXX      src/src_libzmq_la-timers.lo
81.71 npm error   CXX      src/src_libzmq_la-tipc_address.lo
81.71 npm error   CXX      src/src_libzmq_la-tipc_connecter.lo
81.71 npm error   CXX      src/src_libzmq_la-tipc_listener.lo
81.71 npm error   CXX      src/src_libzmq_la-trie.lo
81.71 npm error   CXX      src/src_libzmq_la-udp_address.lo
81.71 npm error   CXX      src/src_libzmq_la-udp_engine.lo
81.71 npm error   CXX      src/src_libzmq_la-v1_decoder.lo
81.71 npm error   CXX      src/src_libzmq_la-v2_decoder.lo
81.71 npm error   CXX      src/src_libzmq_la-v1_encoder.lo
81.71 npm error   CXX      src/src_libzmq_la-v2_encoder.lo
81.71 npm error   CXX      src/src_libzmq_la-vmci.lo
81.71 npm error   CXX      src/src_libzmq_la-vmci_address.lo
81.71 npm error   CXX      src/src_libzmq_la-vmci_connecter.lo
81.71 npm error   CXX      src/src_libzmq_la-vmci_listener.lo
81.71 npm error   CXX      src/src_libzmq_la-xpub.lo
81.71 npm error   CXX      src/src_libzmq_la-xsub.lo
81.71 npm error   CXX      src/src_libzmq_la-zmq.lo
81.71 npm error   CXX      src/src_libzmq_la-zmq_utils.lo
81.71 npm error   CXX      src/src_libzmq_la-decoder_allocators.lo
81.71 npm error   CXX      src/src_libzmq_la-socket_poller.lo
81.71 npm error   CC       src/src_libzmq_la-tweetnacl.lo
81.71 npm error   CXX      tools/curve_keygen.o
81.71 npm error   CXX      perf/local_lat.o
81.71 npm error   CXX      perf/remote_lat.o
81.71 npm error   CXX      perf/local_thr.o
81.71 npm error   CXX      perf/remote_thr.o
81.71 npm error   CXX      perf/inproc_lat.o
81.71 npm error   CXX      perf/inproc_thr.o
81.71 npm error   CXXLD    src/libzmq.la
81.71 npm error   CXXLD    tools/curve_keygen
81.71 npm error   CXXLD    perf/local_lat
81.71 npm error   CXXLD    perf/remote_lat
81.71 npm error   CXXLD    perf/local_thr
81.71 npm error   CXXLD    perf/remote_thr
81.71 npm error   CXXLD    perf/inproc_lat
81.71 npm error   CXXLD    perf/inproc_thr
81.71 npm error make[2]: Leaving directory '/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/zeromq-4.2.2'
81.71 npm error make[1]: Leaving directory '/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/zeromq-4.2.2'
81.71 npm error make[1]: Entering directory '/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/zeromq-4.2.2'
81.71 npm error Making install in doc
81.71 npm error make[2]: Entering directory '/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/zeromq-4.2.2/doc'
81.71 npm error make[3]: Entering directory '/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/zeromq-4.2.2/doc'
81.71 npm error make[3]: Nothing to be done for 'install-exec-am'.
81.71 npm error make[3]: Leaving directory '/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/zeromq-4.2.2/doc'
81.71 npm error make[2]: Leaving directory '/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/zeromq-4.2.2/doc'
81.71 npm error make[2]: Entering directory '/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/zeromq-4.2.2'
81.71 npm error make[3]: Entering directory '/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/zeromq-4.2.2'
81.71 npm error  /usr/bin/mkdir -p '/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/lib'
81.71 npm error  /bin/bash ./libtool   --mode=install /usr/bin/install -c   src/libzmq.la '/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/lib'
81.71 npm error libtool: install: /usr/bin/install -c src/.libs/libzmq.lai /opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/lib/libzmq.la
81.71 npm error libtool: install: /usr/bin/install -c src/.libs/libzmq.a /opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/lib/libzmq.a
81.71 npm error libtool: install: chmod 644 /opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/lib/libzmq.a
81.71 npm error libtool: install: ranlib /opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/lib/libzmq.a
81.71 npm error libtool: finish: PATH="/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/build/node_gyp_bins:/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/node_modules/.bin:/opt/conda/lib/node_modules/ijavascript/node_modules/node_modules/.bin:/opt/conda/lib/node_modules/ijavascript/node_modules/.bin:/opt/conda/lib/node_modules/node_modules/.bin:/opt/conda/lib/node_modules/.bin:/opt/conda/node_modules/.bin:/opt/node_modules/.bin:/node_modules/.bin:/opt/conda/lib/node_modules/npm/node_modules/@npmcli/run-script/lib/node-gyp-bin:/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/node_modules/.bin:/opt/conda/lib/node_modules/ijavascript/node_modules/node_modules/.bin:/opt/conda/lib/node_modules/ijavascript/node_modules/.bin:/opt/conda/lib/node_modules/node_modules/.bin:/opt/conda/lib/node_modules/.bin:/opt/conda/node_modules/.bin:/opt/node_modules/.bin:/node_modules/.bin:/opt/conda/lib/node_modules/npm/node_modules/@npmcli/run-script/lib/node-gyp-bin:/opt/conda/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/sbin" ldconfig -n /opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/lib
81.71 npm error ----------------------------------------------------------------------
81.71 npm error Libraries have been installed in:
81.71 npm error    /opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/lib
81.71 npm error
81.71 npm error If you ever happen to want to link against installed libraries
81.71 npm error in a given directory, LIBDIR, you must either use libtool, and
81.71 npm error specify the full pathname of the library, or use the `-LLIBDIR'
81.71 npm error flag during linking and do at least one of the following:
81.71 npm error    - add LIBDIR to the `LD_LIBRARY_PATH' environment variable
81.71 npm error      during execution
81.71 npm error    - add LIBDIR to the `LD_RUN_PATH' environment variable
81.71 npm error      during linking
81.71 npm error    - use the `-Wl,-rpath -Wl,LIBDIR' linker flag
81.71 npm error    - have your system administrator add LIBDIR to `/etc/ld.so.conf'
81.71 npm error
81.71 npm error See any operating system documentation about shared libraries for
81.71 npm error more information, such as the ld(1) and ld.so(8) manual pages.
81.71 npm error ----------------------------------------------------------------------
81.71 npm error  /usr/bin/mkdir -p '/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/bin'
81.71 npm error   /bin/bash ./libtool   --mode=install /usr/bin/install -c tools/curve_keygen '/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/bin'
81.71 npm error libtool: install: /usr/bin/install -c tools/curve_keygen /opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/bin/curve_keygen
81.71 npm error  /usr/bin/mkdir -p '/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/include'
81.71 npm error  /usr/bin/install -c -m 644 include/zmq.h include/zmq_utils.h '/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/include'
81.71 npm error  /usr/bin/mkdir -p '/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/lib/pkgconfig'
81.71 npm error  /usr/bin/install -c -m 644 src/libzmq.pc '/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/lib/pkgconfig'
81.71 npm error make[3]: Leaving directory '/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/zeromq-4.2.2'
81.71 npm error make[2]: Leaving directory '/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/zeromq-4.2.2'
81.71 npm error make[1]: Leaving directory '/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/zmq/zeromq-4.2.2'
81.71 npm error   TOUCH Release/obj.target/libzmq.stamp
81.71 npm error   CXX(target) Release/obj.target/zmq/binding.o
81.71 npm error make: Leaving directory '/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/build'
81.71 npm error gyp info it worked if it ends with ok
81.71 npm error gyp info using node-gyp@10.1.0
81.71 npm error gyp info using node@22.7.0 | linux | x64
81.71 npm error gyp info find Python using Python version 3.11.9 found at "/opt/conda/bin/python3"
81.71 npm error gyp http GET https://nodejs.org/download/release/v22.7.0/node-v22.7.0-headers.tar.gz
81.71 npm error gyp http 200 https://nodejs.org/download/release/v22.7.0/node-v22.7.0-headers.tar.gz
81.71 npm error gyp http GET https://nodejs.org/download/release/v22.7.0/SHASUMS256.txt
81.71 npm error gyp http 200 https://nodejs.org/download/release/v22.7.0/SHASUMS256.txt
81.71 npm error gyp info spawn /opt/conda/bin/python3
81.71 npm error gyp info spawn args [
81.71 npm error gyp info spawn args '/opt/conda/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py',
81.71 npm error gyp info spawn args 'binding.gyp',
81.71 npm error gyp info spawn args '-f',
81.71 npm error gyp info spawn args 'make',
81.71 npm error gyp info spawn args '-I',
81.71 npm error gyp info spawn args '/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/build/config.gypi',
81.71 npm error gyp info spawn args '-I',
81.71 npm error gyp info spawn args '/opt/conda/lib/node_modules/npm/node_modules/node-gyp/addon.gypi',
81.71 npm error gyp info spawn args '-I',
81.71 npm error gyp info spawn args '/home/jovyan/.cache/node-gyp/22.7.0/include/node/common.gypi',
81.71 npm error gyp info spawn args '-Dlibrary=shared_library',
81.71 npm error gyp info spawn args '-Dvisibility=default',
81.71 npm error gyp info spawn args '-Dnode_root_dir=/home/jovyan/.cache/node-gyp/22.7.0',
81.71 npm error gyp info spawn args '-Dnode_gyp_dir=/opt/conda/lib/node_modules/npm/node_modules/node-gyp',
81.71 npm error gyp info spawn args '-Dnode_lib_file=/home/jovyan/.cache/node-gyp/22.7.0/<(target_arch)/node.lib',
81.71 npm error gyp info spawn args '-Dmodule_root_dir=/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq',
81.71 npm error gyp info spawn args '-Dnode_engine=v8',
81.71 npm error gyp info spawn args '--depth=.',
81.71 npm error gyp info spawn args '--no-parallel',
81.71 npm error gyp info spawn args '--generator-output',
81.71 npm error gyp info spawn args 'build',
81.71 npm error gyp info spawn args '-Goutput_dir=.'
81.71 npm error gyp info spawn args ]
81.71 npm error gyp info spawn make
81.71 npm error gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
81.71 npm error configure: WARNING: Cannot find libunwind
81.71 npm error ar: `u' modifier ignored since `D' is the default (see `U')
81.71 npm error child process exited with code 0
81.71 npm error In file included from ../binding.cc:40:
81.71 npm error ../../nan/nan.h: In function ‘void Nan::SetAccessor(v8::Local<v8::ObjectTemplate>, v8::Local<v8::String>, Nan::GetterCallback, Nan::SetterCallback, v8::Local<v8::Value>, v8::AccessControl, v8::PropertyAttribute, Nan::imp::Sig)’:
81.71 npm error ../../nan/nan.h:2546:19: error: no matching function for call to ‘v8::ObjectTemplate::SetAccessor(v8::Local<v8::String>&, void (*&)(v8::Local<v8::Name>, const v8::PropertyCallbackInfo<v8::Value>&), void (*&)(v8::Local<v8::Name>, v8::Local<v8::Value>, const v8::PropertyCallbackInfo<void>&), v8::Local<v8::Object>&, v8::AccessControl&, v8::PropertyAttribute&)’
81.71 npm error  2546 |   tpl->SetAccessor(
81.71 npm error       |   ~~~~~~~~~~~~~~~~^
81.71 npm error  2547 |       name
81.71 npm error       |       ~~~~
81.71 npm error  2548 |     , getter_
81.71 npm error       |     ~~~~~~~~~
81.71 npm error  2549 |     , setter_
81.71 npm error       |     ~~~~~~~~~
81.71 npm error  2550 |     , obj
81.71 npm error       |     ~~~~~
81.71 npm error  2551 |     , settings
81.71 npm error       |     ~~~~~~~~~~
81.71 npm error  2552 |     , attribute
81.71 npm error       |     ~~~~~~~~~~~
81.71 npm error  2553 | #if (NODE_MODULE_VERSION < NODE_16_0_MODULE_VERSION)
81.71 npm error       | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
81.71 npm error  2554 |     , signature
81.71 npm error       |     ~~~~~~~~~~~
81.71 npm error  2555 | #endif
81.71 npm error       | ~~~~~~
81.71 npm error  2556 |   );
81.71 npm error       |   ~
81.71 npm error In file included from /home/jovyan/.cache/node-gyp/22.7.0/include/node/v8-function.h:15,
81.71 npm error                  from /home/jovyan/.cache/node-gyp/22.7.0/include/node/v8.h:33,
81.71 npm error                  from ../binding.cc:24:
81.71 npm error /home/jovyan/.cache/node-gyp/22.7.0/include/node/v8-template.h:1049:8: note: candidate: ‘void v8::ObjectTemplate::SetAccessor(v8::Local<v8::String>, v8::AccessorGetterCallback, v8::AccessorSetterCallback, v8::Local<v8::Value>, v8::PropertyAttribute, v8::SideEffectType, v8::SideEffectType)’
81.71 npm error  1049 |   void SetAccessor(
81.71 npm error       |        ^~~~~~~~~~~
81.71 npm error /home/jovyan/.cache/node-gyp/22.7.0/include/node/v8-template.h:1052:61: note:   no known conversion for argument 5 from ‘v8::AccessControl’ to ‘v8::PropertyAttribute’
81.71 npm error  1052 |       Local<Value> data = Local<Value>(), PropertyAttribute attribute = None,
81.71 npm error       |                                           ~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~
81.71 npm error /home/jovyan/.cache/node-gyp/22.7.0/include/node/v8-template.h:1055:8: note: candidate: ‘void v8::ObjectTemplate::SetAccessor(v8::Local<v8::Name>, v8::AccessorNameGetterCallback, v8::AccessorNameSetterCallback, v8::Local<v8::Value>, v8::PropertyAttribute, v8::SideEffectType, v8::SideEffectType)’
81.71 npm error  1055 |   void SetAccessor(
81.71 npm error       |        ^~~~~~~~~~~
81.71 npm error /home/jovyan/.cache/node-gyp/22.7.0/include/node/v8-template.h:1058:61: note:   no known conversion for argument 5 from ‘v8::AccessControl’ to ‘v8::PropertyAttribute’
81.71 npm error  1058 |       Local<Value> data = Local<Value>(), PropertyAttribute attribute = None,
81.71 npm error       |                                           ~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~
81.71 npm error In file included from ../binding.cc:40:
81.71 npm error ../../nan/nan.h: In function ‘void Nan::SetAccessor(v8::Local<v8::ObjectTemplate>, v8::Local<v8::String>, Nan::GetterCallback, Nan::SetterCallback, v8::Local<v8::Value>, v8::AccessControl, v8::PropertyAttribute)’:
81.71 npm error ../../nan/nan.h:2592:19: error: no matching function for call to ‘v8::ObjectTemplate::SetAccessor(v8::Local<v8::String>&, void (*&)(v8::Local<v8::Name>, const v8::PropertyCallbackInfo<v8::Value>&), void (*&)(v8::Local<v8::Name>, v8::Local<v8::Value>, const v8::PropertyCallbackInfo<void>&), v8::Local<v8::Object>&, v8::AccessControl&, v8::PropertyAttribute&)’
81.71 npm error  2592 |   tpl->SetAccessor(
81.71 npm error       |   ~~~~~~~~~~~~~~~~^
81.71 npm error  2593 |       name
81.71 npm error       |       ~~~~
81.71 npm error  2594 |     , getter_
81.71 npm error       |     ~~~~~~~~~
81.71 npm error  2595 |     , setter_
81.71 npm error       |     ~~~~~~~~~
81.71 npm error  2596 |     , obj
81.71 npm error       |     ~~~~~
81.71 npm error  2597 |     , settings
81.71 npm error       |     ~~~~~~~~~~
81.71 npm error  2598 |     , attribute
81.71 npm error       |     ~~~~~~~~~~~
81.71 npm error  2599 |   );
81.71 npm error       |   ~
81.71 npm error In file included from /home/jovyan/.cache/node-gyp/22.7.0/include/node/v8-function.h:15,
81.71 npm error                  from /home/jovyan/.cache/node-gyp/22.7.0/include/node/v8.h:33,
81.71 npm error                  from ../binding.cc:24:
81.71 npm error /home/jovyan/.cache/node-gyp/22.7.0/include/node/v8-template.h:1049:8: note: candidate: ‘void v8::ObjectTemplate::SetAccessor(v8::Local<v8::String>, v8::AccessorGetterCallback, v8::AccessorSetterCallback, v8::Local<v8::Value>, v8::PropertyAttribute, v8::SideEffectType, v8::SideEffectType)’
81.71 npm error  1049 |   void SetAccessor(
81.71 npm error       |        ^~~~~~~~~~~
81.71 npm error /home/jovyan/.cache/node-gyp/22.7.0/include/node/v8-template.h:1052:61: note:   no known conversion for argument 5 from ‘v8::AccessControl’ to ‘v8::PropertyAttribute’
81.71 npm error  1052 |       Local<Value> data = Local<Value>(), PropertyAttribute attribute = None,
81.71 npm error       |                                           ~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~
81.71 npm error /home/jovyan/.cache/node-gyp/22.7.0/include/node/v8-template.h:1055:8: note: candidate: ‘void v8::ObjectTemplate::SetAccessor(v8::Local<v8::Name>, v8::AccessorNameGetterCallback, v8::AccessorNameSetterCallback, v8::Local<v8::Value>, v8::PropertyAttribute, v8::SideEffectType, v8::SideEffectType)’
81.71 npm error  1055 |   void SetAccessor(
81.71 npm error       |        ^~~~~~~~~~~
81.71 npm error /home/jovyan/.cache/node-gyp/22.7.0/include/node/v8-template.h:1058:61: note:   no known conversion for argument 5 from ‘v8::AccessControl’ to ‘v8::PropertyAttribute’
81.71 npm error  1058 |       Local<Value> data = Local<Value>(), PropertyAttribute attribute = None,
81.71 npm error       |                                           ~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~
81.71 npm error ../binding.cc: In member function ‘void zmq::Socket::NotifyReadReady()’:
81.71 npm error ../binding.cc:399:22: warning: ‘v8::Local<v8::Value> Nan::MakeCallback(v8::Local<v8::Object>, v8::Local<v8::Function>, int, v8::Local<v8::Value>*)’ is deprecated [-Wdeprecated-declarations]
81.71 npm error   399 |     Nan::MakeCallback(this->handle(), callback_v.As<Function>(), 0, NULL);
81.71 npm error       |     ~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
81.71 npm error In file included from ../binding.cc:40:
81.71 npm error ../../nan/nan.h:1030:46: note: declared here
81.71 npm error  1030 |   NAN_DEPRECATED inline v8::Local<v8::Value> MakeCallback(
81.71 npm error       |                                              ^~~~~~~~~~~~
81.71 npm error ../binding.cc: In member function ‘void zmq::Socket::NotifySendReady()’:
81.71 npm error ../binding.cc:407:22: warning: ‘v8::Local<v8::Value> Nan::MakeCallback(v8::Local<v8::Object>, v8::Local<v8::Function>, int, v8::Local<v8::Value>*)’ is deprecated [-Wdeprecated-declarations]
81.71 npm error   407 |     Nan::MakeCallback(this->handle(), callback_v.As<Function>(), 0, NULL);
81.71 npm error       |     ~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
81.71 npm error In file included from ../binding.cc:40:
81.71 npm error ../../nan/nan.h:1030:46: note: declared here
81.71 npm error  1030 |   NAN_DEPRECATED inline v8::Local<v8::Value> MakeCallback(
81.71 npm error       |                                              ^~~~~~~~~~~~
81.71 npm error ../binding.cc: In member function ‘void zmq::Socket::MonitorEvent(uint16_t, int32_t, char*)’:
81.71 npm error ../binding.cc:458:22: warning: ‘v8::Local<v8::Value> Nan::MakeCallback(v8::Local<v8::Object>, v8::Local<v8::Function>, int, v8::Local<v8::Value>*)’ is deprecated [-Wdeprecated-declarations]
81.71 npm error   458 |     Nan::MakeCallback(this->handle(), callback_v.As<Function>(), 4, argv);
81.71 npm error       |     ~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
81.71 npm error In file included from ../binding.cc:40:
81.71 npm error ../../nan/nan.h:1030:46: note: declared here
81.71 npm error  1030 |   NAN_DEPRECATED inline v8::Local<v8::Value> MakeCallback(
81.71 npm error       |                                              ^~~~~~~~~~~~
81.71 npm error ../binding.cc: In member function ‘void zmq::Socket::MonitorError(const char*)’:
81.71 npm error ../binding.cc:473:22: warning: ‘v8::Local<v8::Value> Nan::MakeCallback(v8::Local<v8::Object>, v8::Local<v8::Function>, int, v8::Local<v8::Value>*)’ is deprecated [-Wdeprecated-declarations]
81.71 npm error   473 |     Nan::MakeCallback(this->handle(), callback_v.As<Function>(), 1, argv);
81.71 npm error       |     ~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
81.71 npm error In file included from ../binding.cc:40:
81.71 npm error ../../nan/nan.h:1030:46: note: declared here
81.71 npm error  1030 |   NAN_DEPRECATED inline v8::Local<v8::Value> MakeCallback(
81.71 npm error       |                                              ^~~~~~~~~~~~
81.71 npm error ../binding.cc: In static member function ‘static void zmq::Socket::UV_MonitorCallback(uv_timer_t*, int)’:
81.71 npm error ../binding.cc:545:42: warning: cast between incompatible function types from ‘void (*)(uv_timer_t*, int)’ {aka ‘void (*)(uv_timer_s*, int)’} to ‘uv_timer_cb’ {aka ‘void (*)(uv_timer_s*)’} [-Wcast-function-type]
81.71 npm error   545 |       uv_timer_start(s->monitor_handle_, reinterpret_cast<uv_timer_cb>(Socket::UV_MonitorCallback), s->timer_interval_, 0);
81.71 npm error       |                                          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
81.71 npm error ../binding.cc: In static member function ‘static Nan::NAN_METHOD_RETURN_TYPE zmq::Socket::Bind(Nan::NAN_METHOD_ARGS_TYPE)’:
81.71 npm error ../binding.cc:779:19: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
81.71 npm error   779 |                   (uv_after_work_cb)UV_BindAsyncAfter);
81.71 npm error       |                   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
81.71 npm error ../binding.cc: In static member function ‘static void zmq::Socket::UV_BindAsyncAfter(uv_work_t*)’:
81.71 npm error ../binding.cc:814:22: warning: ‘v8::Local<v8::Value> Nan::MakeCallback(v8::Local<v8::Object>, v8::Local<v8::Function>, int, v8::Local<v8::Value>*)’ is deprecated [-Wdeprecated-declarations]
81.71 npm error   814 |     Nan::MakeCallback(Nan::GetCurrentContext()->Global(), cb, 1, argv);
81.71 npm error       |     ~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
81.71 npm error In file included from ../binding.cc:40:
81.71 npm error ../../nan/nan.h:1030:46: note: declared here
81.71 npm error  1030 |   NAN_DEPRECATED inline v8::Local<v8::Value> MakeCallback(
81.71 npm error       |                                              ^~~~~~~~~~~~
81.71 npm error ../binding.cc: In static member function ‘static Nan::NAN_METHOD_RETURN_TYPE zmq::Socket::Unbind(Nan::NAN_METHOD_ARGS_TYPE)’:
81.71 npm error ../binding.cc:860:19: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
81.71 npm error   860 |                   (uv_after_work_cb)UV_UnbindAsyncAfter);
81.71 npm error       |                   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
81.71 npm error ../binding.cc: In static member function ‘static void zmq::Socket::UV_UnbindAsyncAfter(uv_work_t*)’:
81.71 npm error ../binding.cc:893:22: warning: ‘v8::Local<v8::Value> Nan::MakeCallback(v8::Local<v8::Object>, v8::Local<v8::Function>, int, v8::Local<v8::Value>*)’ is deprecated [-Wdeprecated-declarations]
81.71 npm error   893 |     Nan::MakeCallback(Nan::GetCurrentContext()->Global(), cb, 1, argv);
81.71 npm error       |     ~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
81.71 npm error In file included from ../binding.cc:40:
81.71 npm error ../../nan/nan.h:1030:46: note: declared here
81.71 npm error  1030 |   NAN_DEPRECATED inline v8::Local<v8::Value> MakeCallback(
81.71 npm error       |                                              ^~~~~~~~~~~~
81.71 npm error ../binding.cc: In static member function ‘static Nan::NAN_METHOD_RETURN_TYPE zmq::Socket::Monitor(Nan::NAN_METHOD_ARGS_TYPE)’:
81.71 npm error ../binding.cc:1122:47: warning: cast between incompatible function types from ‘void (*)(uv_timer_t*, int)’ {aka ‘void (*)(uv_timer_s*, int)’} to ‘uv_timer_cb’ {aka ‘void (*)(uv_timer_s*)’} [-Wcast-function-type]
81.71 npm error  1122 |       uv_timer_start(socket->monitor_handle_, reinterpret_cast<uv_timer_cb>(Socket::UV_MonitorCallback), timer_interval, 0);
81.71 npm error       |                                               ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
81.71 npm error In file included from /home/jovyan/.cache/node-gyp/22.7.0/include/node/v8-array-buffer.h:12,
81.71 npm error                  from /home/jovyan/.cache/node-gyp/22.7.0/include/node/v8.h:24,
81.71 npm error                  from ../binding.cc:24:
81.71 npm error /home/jovyan/.cache/node-gyp/22.7.0/include/node/v8-local-handle.h: In instantiation of ‘v8::Local<T>::Local(v8::Local<S>) [with S = v8::Data; T = v8::Value]’:
81.71 npm error ../../nan/nan_callbacks_12_inl.h:175:53:   required from here
81.71 npm error /home/jovyan/.cache/node-gyp/22.7.0/include/node/v8-local-handle.h:269:42: error: static assertion failed: type check
81.71 npm error   269 |     static_assert(std::is_base_of<T, S>::value, "type check");
81.71 npm error       |                                          ^~~~~
81.71 npm error /home/jovyan/.cache/node-gyp/22.7.0/include/node/v8-local-handle.h:269:42: note: ‘std::integral_constant<bool, false>::value’ evaluates to false
81.71 npm error make: *** [zmq.target.mk:113: Release/obj.target/zmq/binding.o] Error 1
81.71 npm error gyp ERR! build error
81.71 npm error gyp ERR! stack Error: `make` failed with exit code: 2
81.71 npm error gyp ERR! stack at ChildProcess.<anonymous> (/opt/conda/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:209:23)
81.71 npm error gyp ERR! System Linux 6.8.0-44-generic
81.71 npm error gyp ERR! command "/opt/conda/bin/node" "/opt/conda/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
81.71 npm error gyp ERR! cwd /opt/conda/lib/node_modules/ijavascript/node_modules/zeromq
81.71 npm error gyp ERR! node -v v22.7.0
81.71 npm error gyp ERR! node-gyp -v v10.1.0
81.71 npm error gyp ERR! not ok
81.71 npm error gyp info it worked if it ends with ok
81.71 npm error gyp info using node-gyp@10.1.0
81.71 npm error gyp info using node@22.7.0 | linux | x64
81.71 npm error gyp info find Python using Python version 3.11.9 found at "/opt/conda/bin/python3"
81.71 npm error gyp info spawn /opt/conda/bin/python3
81.71 npm error gyp info spawn args [
81.71 npm error gyp info spawn args '/opt/conda/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py',
81.71 npm error gyp info spawn args 'binding.gyp',
81.71 npm error gyp info spawn args '-f',
81.71 npm error gyp info spawn args 'make',
81.71 npm error gyp info spawn args '-I',
81.71 npm error gyp info spawn args '/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq/build/config.gypi',
81.71 npm error gyp info spawn args '-I',
81.71 npm error gyp info spawn args '/opt/conda/lib/node_modules/npm/node_modules/node-gyp/addon.gypi',
81.71 npm error gyp info spawn args '-I',
81.71 npm error gyp info spawn args '/home/jovyan/.cache/node-gyp/22.7.0/include/node/common.gypi',
81.71 npm error gyp info spawn args '-Dlibrary=shared_library',
81.71 npm error gyp info spawn args '-Dvisibility=default',
81.71 npm error gyp info spawn args '-Dnode_root_dir=/home/jovyan/.cache/node-gyp/22.7.0',
81.71 npm error gyp info spawn args '-Dnode_gyp_dir=/opt/conda/lib/node_modules/npm/node_modules/node-gyp',
81.71 npm error gyp info spawn args '-Dnode_lib_file=/home/jovyan/.cache/node-gyp/22.7.0/<(target_arch)/node.lib',
81.71 npm error gyp info spawn args '-Dmodule_root_dir=/opt/conda/lib/node_modules/ijavascript/node_modules/zeromq',
81.71 npm error gyp info spawn args '-Dnode_engine=v8',
81.71 npm error gyp info spawn args '--depth=.',
81.71 npm error gyp info spawn args '--no-parallel',
81.71 npm error gyp info spawn args '--generator-output',
81.71 npm error gyp info spawn args 'build',
81.71 npm error gyp info spawn args '-Goutput_dir=.'
81.71 npm error gyp info spawn args ]
81.71 npm error gyp info spawn make
81.71 npm error gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
81.71 npm error configure: WARNING: Cannot find libunwind
81.71 npm error ar: `u' modifier ignored since `D' is the default (see `U')
81.71 npm error child process exited with code 0
81.71 npm error In file included from ../binding.cc:40:
81.71 npm error ../../nan/nan.h: In function ‘void Nan::SetAccessor(v8::Local<v8::ObjectTemplate>, v8::Local<v8::String>, Nan::GetterCallback, Nan::SetterCallback, v8::Local<v8::Value>, v8::AccessControl, v8::PropertyAttribute, Nan::imp::Sig)’:
81.71 npm error ../../nan/nan.h:2546:19: error: no matching function for call to ‘v8::ObjectTemplate::SetAccessor(v8::Local<v8::String>&, void (*&)(v8::Local<v8::Name>, const v8::PropertyCallbackInfo<v8::Value>&), void (*&)(v8::Local<v8::Name>, v8::Local<v8::Value>, const v8::PropertyCallbackInfo<void>&), v8::Local<v8::Object>&, v8::AccessControl&, v8::PropertyAttribute&)’
81.71 npm error  2546 |   tpl->SetAccessor(
81.71 npm error       |   ~~~~~~~~~~~~~~~~^
81.71 npm error  2547 |       name
81.71 npm error       |       ~~~~
81.71 npm error  2548 |     , getter_
81.71 npm error       |     ~~~~~~~~~
81.71 npm error  2549 |     , setter_
81.71 npm error       |     ~~~~~~~~~
81.71 npm error  2550 |     , obj
81.71 npm error       |     ~~~~~
81.71 npm error  2551 |     , settings
81.71 npm error       |     ~~~~~~~~~~
81.71 npm error  2552 |     , attribute
81.71 npm error       |     ~~~~~~~~~~~
81.71 npm error  2553 | #if (NODE_MODULE_VERSION < NODE_16_0_MODULE_VERSION)
81.71 npm error       | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
81.71 npm error  2554 |     , signature
81.71 npm error       |     ~~~~~~~~~~~
81.71 npm error  2555 | #endif
81.71 npm error       | ~~~~~~
81.71 npm error  2556 |   );
81.71 npm error       |   ~
81.71 npm error In file included from /home/jovyan/.cache/node-gyp/22.7.0/include/node/v8-function.h:15,
81.71 npm error                  from /home/jovyan/.cache/node-gyp/22.7.0/include/node/v8.h:33,
81.71 npm error                  from ../binding.cc:24:
81.71 npm error /home/jovyan/.cache/node-gyp/22.7.0/include/node/v8-template.h:1049:8: note: candidate: ‘void v8::ObjectTemplate::SetAccessor(v8::Local<v8::String>, v8::AccessorGetterCallback, v8::AccessorSetterCallback, v8::Local<v8::Value>, v8::PropertyAttribute, v8::SideEffectType, v8::SideEffectType)’
81.71 npm error  1049 |   void SetAccessor(
81.71 npm error       |        ^~~~~~~~~~~
81.71 npm error /home/jovyan/.cache/node-gyp/22.7.0/include/node/v8-template.h:1052:61: note:   no known conversion for argument 5 from ‘v8::AccessControl’ to ‘v8::PropertyAttribute’
81.71 npm error  1052 |       Local<Value> data = Local<Value>(), PropertyAttribute attribute = None,
81.71 npm error       |                                           ~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~
81.71 npm error /home/jovyan/.cache/node-gyp/22.7.0/include/node/v8-template.h:1055:8: note: candidate: ‘void v8::ObjectTemplate::SetAccessor(v8::Local<v8::Name>, v8::AccessorNameGetterCallback, v8::AccessorNameSetterCallback, v8::Local<v8::Value>, v8::PropertyAttribute, v8::SideEffectType, v8::SideEffectType)’
81.71 npm error  1055 |   void SetAccessor(
81.71 npm error       |        ^~~~~~~~~~~
81.71 npm error /home/jovyan/.cache/node-gyp/22.7.0/include/node/v8-template.h:1058:61: note:   no known conversion for argument 5 from ‘v8::AccessControl’ to ‘v8::PropertyAttribute’
81.71 npm error  1058 |       Local<Value> data = Local<Value>(), PropertyAttribute attribute = None,
81.71 npm error       |                                           ~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~
81.71 npm error In file included from ../binding.cc:40:
81.71 npm error ../../nan/nan.h: In function ‘void Nan::SetAccessor(v8::Local<v8::ObjectTemplate>, v8::Local<v8::String>, Nan::GetterCallback, Nan::SetterCallback, v8::Local<v8::Value>, v8::AccessControl, v8::PropertyAttribute)’:
81.71 npm error ../../nan/nan.h:2592:19: error: no matching function for call to ‘v8::ObjectTemplate::SetAccessor(v8::Local<v8::String>&, void (*&)(v8::Local<v8::Name>, const v8::PropertyCallbackInfo<v8::Value>&), void (*&)(v8::Local<v8::Name>, v8::Local<v8::Value>, const v8::PropertyCallbackInfo<void>&), v8::Local<v8::Object>&, v8::AccessControl&, v8::PropertyAttribute&)’
81.71 npm error  2592 |   tpl->SetAccessor(
81.71 npm error       |   ~~~~~~~~~~~~~~~~^
81.71 npm error  2593 |       name
81.71 npm error       |       ~~~~
81.71 npm error  2594 |     , getter_
81.71 npm error       |     ~~~~~~~~~
81.71 npm error  2595 |     , setter_
81.71 npm error       |     ~~~~~~~~~
81.71 npm error  2596 |     , obj
81.71 npm error       |     ~~~~~
81.71 npm error  2597 |     , settings
81.71 npm error       |     ~~~~~~~~~~
81.71 npm error  2598 |     , attribute
81.71 npm error       |     ~~~~~~~~~~~
81.71 npm error  2599 |   );
81.71 npm error       |   ~
81.71 npm error In file included from /home/jovyan/.cache/node-gyp/22.7.0/include/node/v8-function.h:15,
81.71 npm error                  from /home/jovyan/.cache/node-gyp/22.7.0/include/node/v8.h:33,
81.71 npm error                  from ../binding.cc:24:
81.71 npm error /home/jovyan/.cache/node-gyp/22.7.0/include/node/v8-template.h:1049:8: note: candidate: ‘void v8::ObjectTemplate::SetAccessor(v8::Local<v8::String>, v8::AccessorGetterCallback, v8::AccessorSetterCallback, v8::Local<v8::Value>, v8::PropertyAttribute, v8::SideEffectType, v8::SideEffectType)’
81.71 npm error  1049 |   void SetAccessor(
81.71 npm error       |        ^~~~~~~~~~~
81.71 npm error /home/jovyan/.cache/node-gyp/22.7.0/include/node/v8-template.h:1052:61: note:   no known conversion for argument 5 from ‘v8::AccessControl’ to ‘v8::PropertyAttribute’
81.71 npm error  1052 |       Local<Value> data = Local<Value>(), PropertyAttribute attribute = None,
81.71 npm error       |                                           ~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~
81.71 npm error /home/jovyan/.cache/node-gyp/22.7.0/include/node/v8-template.h:1055:8: note: candidate: ‘void v8::ObjectTemplate::SetAccessor(v8::Local<v8::Name>, v8::AccessorNameGetterCallback, v8::AccessorNameSetterCallback, v8::Local<v8::Value>, v8::PropertyAttribute, v8::SideEffectType, v8::SideEffectType)’
81.71 npm error  1055 |   void SetAccessor(
81.71 npm error       |        ^~~~~~~~~~~
81.71 npm error /home/jovyan/.cache/node-gyp/22.7.0/include/node/v8-template.h:1058:61: note:   no known conversion for argument 5 from ‘v8::AccessControl’ to ‘v8::PropertyAttribute’
81.71 npm error  1058 |       Local<Value> data = Local<Value>(), PropertyAttribute attribute = None,
81.71 npm error       |                                           ~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~
81.71 npm error ../binding.cc: In member function ‘void zmq::Socket::NotifyReadReady()’:
81.71 npm error ../binding.cc:399:22: warning: ‘v8::Local<v8::Value> Nan::MakeCallback(v8::Local<v8::Object>, v8::Local<v8::Function>, int, v8::Local<v8::Value>*)’ is deprecated [-Wdeprecated-declarations]
81.71 npm error   399 |     Nan::MakeCallback(this->handle(), callback_v.As<Function>(), 0, NULL);
81.71 npm error       |     ~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
81.71 npm error In file included from ../binding.cc:40:
81.71 npm error ../../nan/nan.h:1030:46: note: declared here
81.71 npm error  1030 |   NAN_DEPRECATED inline v8::Local<v8::Value> MakeCallback(
81.71 npm error       |                                              ^~~~~~~~~~~~
81.71 npm error ../binding.cc: In member function ‘void zmq::Socket::NotifySendReady()’:
81.71 npm error ../binding.cc:407:22: warning: ‘v8::Local<v8::Value> Nan::MakeCallback(v8::Local<v8::Object>, v8::Local<v8::Function>, int, v8::Local<v8::Value>*)’ is deprecated [-Wdeprecated-declarations]
81.71 npm error   407 |     Nan::MakeCallback(this->handle(), callback_v.As<Function>(), 0, NULL);
81.71 npm error       |     ~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
81.71 npm error In file included from ../binding.cc:40:
81.71 npm error ../../nan/nan.h:1030:46: note: declared here
81.71 npm error  1030 |   NAN_DEPRECATED inline v8::Local<v8::Value> MakeCallback(
81.71 npm error       |                                              ^~~~~~~~~~~~
81.71 npm error ../binding.cc: In member function ‘void zmq::Socket::MonitorEvent(uint16_t, int32_t, char*)’:
81.71 npm error ../binding.cc:458:22: warning: ‘v8::Local<v8::Value> Nan::MakeCallback(v8::Local<v8::Object>, v8::Local<v8::Function>, int, v8::Local<v8::Value>*)’ is deprecated [-Wdeprecated-declarations]
81.71 npm error   458 |     Nan::MakeCallback(this->handle(), callback_v.As<Function>(), 4, argv);
81.71 npm error       |     ~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
81.71 npm error In file included from ../binding.cc:40:
81.71 npm error ../../nan/nan.h:1030:46: note: declared here
81.71 npm error  1030 |   NAN_DEPRECATED inline v8::Local<v8::Value> MakeCallback(
81.71 npm error       |                                              ^~~~~~~~~~~~
81.71 npm error ../binding.cc: In member function ‘void zmq::Socket::MonitorError(const char*)’:
81.71 npm error ../binding.cc:473:22: warning: ‘v8::Local<v8::Value> Nan::MakeCallback(v8::Local<v8::Object>, v8::Local<v8::Function>, int, v8::Local<v8::Value>*)’ is deprecated [-Wdeprecated-declarations]
81.71 npm error   473 |     Nan::MakeCallback(this->handle(), callback_v.As<Function>(), 1, argv);
81.71 npm error       |     ~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
81.71 npm error In file included from ../binding.cc:40:
81.71 npm error ../../nan/nan.h:1030:46: note: declared here
81.71 npm error  1030 |   NAN_DEPRECATED inline v8::Local<v8::Value> MakeCallback(
81.71 npm error       |                                              ^~~~~~~~~~~~
81.71 npm error ../binding.cc: In static member function ‘static void zmq::Socket::UV_MonitorCallback(uv_timer_t*, int)’:
81.71 npm error ../binding.cc:545:42: warning: cast between incompatible function types from ‘void (*)(uv_timer_t*, int)’ {aka ‘void (*)(uv_timer_s*, int)’} to ‘uv_timer_cb’ {aka ‘void (*)(uv_timer_s*)’} [-Wcast-function-type]
81.71 npm error   545 |       uv_timer_start(s->monitor_handle_, reinterpret_cast<uv_timer_cb>(Socket::UV_MonitorCallback), s->timer_interval_, 0);
81.71 npm error       |                                          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
81.71 npm error ../binding.cc: In static member function ‘static Nan::NAN_METHOD_RETURN_TYPE zmq::Socket::Bind(Nan::NAN_METHOD_ARGS_TYPE)’:
81.71 npm error ../binding.cc:779:19: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
81.71 npm error   779 |                   (uv_after_work_cb)UV_BindAsyncAfter);
81.71 npm error       |                   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
81.71 npm error ../binding.cc: In static member function ‘static void zmq::Socket::UV_BindAsyncAfter(uv_work_t*)’:
81.71 npm error ../binding.cc:814:22: warning: ‘v8::Local<v8::Value> Nan::MakeCallback(v8::Local<v8::Object>, v8::Local<v8::Function>, int, v8::Local<v8::Value>*)’ is deprecated [-Wdeprecated-declarations]
81.71 npm error   814 |     Nan::MakeCallback(Nan::GetCurrentContext()->Global(), cb, 1, argv);
81.71 npm error       |     ~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
81.71 npm error In file included from ../binding.cc:40:
81.71 npm error ../../nan/nan.h:1030:46: note: declared here
81.71 npm error  1030 |   NAN_DEPRECATED inline v8::Local<v8::Value> MakeCallback(
81.71 npm error       |                                              ^~~~~~~~~~~~
81.71 npm error ../binding.cc: In static member function ‘static Nan::NAN_METHOD_RETURN_TYPE zmq::Socket::Unbind(Nan::NAN_METHOD_ARGS_TYPE)’:
81.71 npm error ../binding.cc:860:19: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
81.71 npm error   860 |                   (uv_after_work_cb)UV_UnbindAsyncAfter);
81.71 npm error       |                   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
81.71 npm error ../binding.cc: In static member function ‘static void zmq::Socket::UV_UnbindAsyncAfter(uv_work_t*)’:
81.71 npm error ../binding.cc:893:22: warning: ‘v8::Local<v8::Value> Nan::MakeCallback(v8::Local<v8::Object>, v8::Local<v8::Function>, int, v8::Local<v8::Value>*)’ is deprecated [-Wdeprecated-declarations]
81.71 npm error   893 |     Nan::MakeCallback(Nan::GetCurrentContext()->Global(), cb, 1, argv);
81.71 npm error       |     ~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
81.71 npm error In file included from ../binding.cc:40:
81.71 npm error ../../nan/nan.h:1030:46: note: declared here
81.71 npm error  1030 |   NAN_DEPRECATED inline v8::Local<v8::Value> MakeCallback(
81.71 npm error       |                                              ^~~~~~~~~~~~
81.71 npm error ../binding.cc: In static member function ‘static Nan::NAN_METHOD_RETURN_TYPE zmq::Socket::Monitor(Nan::NAN_METHOD_ARGS_TYPE)’:
81.71 npm error ../binding.cc:1122:47: warning: cast between incompatible function types from ‘void (*)(uv_timer_t*, int)’ {aka ‘void (*)(uv_timer_s*, int)’} to ‘uv_timer_cb’ {aka ‘void (*)(uv_timer_s*)’} [-Wcast-function-type]
81.71 npm error  1122 |       uv_timer_start(socket->monitor_handle_, reinterpret_cast<uv_timer_cb>(Socket::UV_MonitorCallback), timer_interval, 0);
81.71 npm error       |                                               ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
81.71 npm error In file included from /home/jovyan/.cache/node-gyp/22.7.0/include/node/v8-array-buffer.h:12,
81.71 npm error                  from /home/jovyan/.cache/node-gyp/22.7.0/include/node/v8.h:24,
81.71 npm error                  from ../binding.cc:24:
81.71 npm error /home/jovyan/.cache/node-gyp/22.7.0/include/node/v8-local-handle.h: In instantiation of ‘v8::Local<T>::Local(v8::Local<S>) [with S = v8::Data; T = v8::Value]’:
81.71 npm error ../../nan/nan_callbacks_12_inl.h:175:53:   required from here
81.71 npm error /home/jovyan/.cache/node-gyp/22.7.0/include/node/v8-local-handle.h:269:42: error: static assertion failed: type check
81.71 npm error   269 |     static_assert(std::is_base_of<T, S>::value, "type check");
81.71 npm error       |                                          ^~~~~
81.71 npm error /home/jovyan/.cache/node-gyp/22.7.0/include/node/v8-local-handle.h:269:42: note: ‘std::integral_constant<bool, false>::value’ evaluates to false
81.71 npm error make: *** [zmq.target.mk:113: Release/obj.target/zmq/binding.o] Error 1
81.71 npm error gyp ERR! build error
81.71 npm error gyp ERR! stack Error: `make` failed with exit code: 2
81.71 npm error gyp ERR! stack at ChildProcess.<anonymous> (/opt/conda/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:209:23)
81.71 npm error gyp ERR! System Linux 6.8.0-44-generic
81.71 npm error gyp ERR! command "/opt/conda/bin/node" "/opt/conda/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
81.71 npm error gyp ERR! cwd /opt/conda/lib/node_modules/ijavascript/node_modules/zeromq
81.71 npm error gyp ERR! node -v v22.7.0
81.71 npm error gyp ERR! node-gyp -v v10.1.0
81.71 npm error gyp ERR! not ok
81.71 npm error A complete log of this run can be found in: /home/jovyan/.npm/_logs/2024-10-17T14_04_29_696Z-debug-0.log
------
failed to solve: process "/bin/bash -o pipefail -c cat /home/jovyan/libs/npm.txt | xargs npm install -g" did not complete successfully: exit code: 123

I noted somewhere else searching for zeromq, that if other packages include zeromq, there's some conflict causing the build to fail.