[Pkg-javascript-devel] Bug#895672: nodejs: modules can build using ssl 1.0 symbols but will fail at runtime
Jérémy Lal
kapouer at melix.org
Sat Apr 14 12:29:53 BST 2018
Package: nodejs
Version: 8.11.1~dfsg-2
Severity: normal
I was building a module using openssl 1.0 (uws) and it doesn't fail
when compiling, but it fails at runtime:
uws_linux_57.node: undefined symbol: SSL_library_init
(the workaround is to just drop that call, but that's not the subject here).
I think the compilation should have failed instead.
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.15.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages nodejs depends on:
ii libc-ares2 1.14.0-1
ii libc6 2.27-3
ii libgcc1 1:8-20180402-1
ii libhttp-parser2.8 2.8.1-1
ii libicu57 57.1-9
ii libnghttp2-14 1.31.0-1
ii libssl1.1 1.1.0h-2
ii libstdc++6 8-20180402-1
ii libuv1 1.18.0-3
ii zlib1g 1:1.2.8.dfsg-5
Versions of packages nodejs recommends:
ii ca-certificates 20180409
ii nodejs-doc 8.11.1~dfsg-2
nodejs suggests no packages.
-- no debconf information
More information about the Pkg-javascript-devel
mailing list