Re: seg fault building npm

[maya%netbsd.org@localhost]

Hello people in this thread,
I can build npm fine if I use, in the nodejs package options.mk

So, I think that fhajny wishes he can test all variations of pkg
options, and we're somewhat at an impasse/complicated setup.

alternative suggestion: we update openssl to 1.1.x. netbsd-current has
been using a pretty shiny openssl for a while, so most things should be
fine. python34 is the major fallout.


Index: options.mk
===================================================================
RCS file: /cvsroot/pkgsrc/lang/nodejs/options.mk,v
retrieving revision 1.11
diff -u -r1.11 options.mk
--- options.mk	3 May 2018 21:19:16 -0000	1.11
+++ options.mk	21 Feb 2019 20:42:38 -0000
@@ -2,10 +2,15 @@
 
 PKG_OPTIONS_VAR=	PKG_OPTIONS.node
 PKG_SUPPORTED_OPTIONS=	openssl dtrace
-PKG_SUGGESTED_OPTIONS=	openssl
+PKG_SUGGESTED_OPTIONS=	
 
 .include "../../mk/bsd.prefs.mk"
 
+# Crashes with builtin openssl
+.if ${OPSYS} != "NetBSD"
+PKG_SUGGESTED_OPTIONS+=	openssl
+.endif
+
 .if (${OPSYS} == "SunOS" || ${OPSYS} == "Darwin") \
     && exists(/usr/sbin/dtrace)
 PKG_SUGGESTED_OPTIONS+=	dtrace
@@ -30,5 +35,6 @@
 # nodejs 10.x requires OpenSSL 1.1.x. Use embedded source until we have such.
 PLIST.openssl=		yes
 .else
-CONFIGURE_ARGS+=	--without-ssl
+CONFIGURE_ARGS+=	--shared-openssl
+.include "../../security/openssl/buildlink3.mk"
 .endif