Open christianlupus opened 4 years ago
Hi @christianlupus, I can confirm under arch, and have been seeing similar v8 API errors with node projects that compile native modules. I don't know the specific causes, but I gather node-gyp / bundled v8 stuff is in a state of upheaval rn and there are breakages across the ecosystem (possibly related background: https://github.com/nodejs/node-gyp/issues/1791)
For this specific project, I am able to build native deps successfully using node v10 installed via nvm:
nvm install 10
nvm use 10
If anyone can provide further insight into where issues should be filed (can sodium-native do anything about this?) plz chime in.
Based on https://github.com/sodium-friends/sodium-native/issues/95#issuecomment-517346840, seems upgrading sodium native to >2.4.3. But there are several copies kicking around in node_modules. Y'all nodejs folks have normalized some pretty scary (for outsiders) dependency trees.
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
I just tried to rebuild and the problem seems to be still present.
I just tried compiling with node versions 14, 12, and 10 and they failed for me as well.
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
I just tried to compile and it still refused to compile here.
I have the problem that I try to compile patchbay on my Archlinux system. I get a whole lot of errors and warnings. I put it in a gist, as it is too lengthy to put it here.
I think the relevant (and first) error is around line 793 in the log file:
I guess this is due to an incompatible library/binary version. Can you hint me, where I can look? I did not find anything to solve this.
If you need any information about my system, please tell me.