Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#57913 - [node-gyp] uses incorrect OpenSSL headers
Attached to Project:
Community Packages
Opened by Akihiko Odaki (nekomanma) - Wednesday, 21 March 2018, 15:34 GMT
Last edited by Toolybird (Toolybird) - Sunday, 14 May 2023, 23:04 GMT
Opened by Akihiko Odaki (nekomanma) - Wednesday, 21 March 2018, 15:34 GMT
Last edited by Toolybird (Toolybird) - Sunday, 14 May 2023, 23:04 GMT
|
DetailsDescription:
node-gyp fetches headers including OpenSSL to build Node.js C++ addons. However, the fetched OpenSSL headers is of 1.0.2, while OpenSSL provided by Arch Linux is 1.1.0. This results in failure when loading an addon built with node-gyp. Additional info: * package version(s) npm 5.7.1-1 openssl 1.1.0.g-1 * config and/or log files etc See the below. Steps to reproduce: $ npm i uws > uws@9.14.0 install /home/aki/node_modules/uws > node-gyp rebuild > build_log.txt 2>&1 || exit 0 npm WARN saveError ENOENT: no such file or directory, open '/home/aki/package.json' npm WARN enoent ENOENT: no such file or directory, open '/home/aki/package.json' npm WARN aki No description npm WARN aki No repository field. npm WARN aki No README data npm WARN aki No license field. + uws@9.14.0 added 1 package from 1 contributor in 13.565s $ objdump -T node_modules/uws/build/Release/uws.node | grep SSL_library_init 0000000000000000 D *UND* 0000000000000000 SSL_library_init uws is a NPM package with a C++ addon which uses OpenSSL. SSL_library_init is a function provided until 1.0.x. It is not availble for 1.1.0. A patch is attached. 
npm.patch
(1.8 KiB)
|
This task depends upon
FS#57863resolved the problem for nodejs package, but not for nodejs-lts-carbon. I believe this is the best way to address the issue.Note that OpenSSL 1.1.0 is supported by LTS Carbon:
https://github.com/nodejs/node/pull/18622
The change suggested in this issue is the one proposed by an upstream node-gyp maintainer:
https://github.com/nodejs/node-gyp/pull/1395#issuecomment-385954232
Thank you for efforts to address the problem. I hope this issue is the last one remaining.
What is the use case of this patch, and how does it detect the actual correct location of the needed openssl headers? It seems like something that node-gyp would need to detect by detecting the actual version needed.