Re: pkg/51170: SIGSEGV during build of nodejs4 with netbsd/current

[Leonardo Taccari <leot%NetBSD.org@localhost>]

The following reply was made to PR pkg/51170; it has been noted by GNATS.

From: Leonardo Taccari <leot%NetBSD.org@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: pkg/51170: SIGSEGV during build of nodejs4 with netbsd/current
Date: Fri, 27 May 2016 11:00:47 +0200

 Hello Benjamin,
 
 netbsd@benjaminlorenz.email writes:
 > [...]
 > >Description:
 > 	While compiling nodejs 4.4.5 from pkgsrc, I get a segmentation fault wi=
 th
 > 	a current system.
 > =
 
 > 1]   Segmentation fault (core dumped) "/usr/pkg/src/la...
 > gmake[1]: *** [deps/v8/tools/gyp/v8_snapshot.target.mk:13: /usr/pkg/src/=
 lang/nodejs4/work/node-v4.4.5/out/Release/obj.target/v8_snaps
 > hot/geni/snapshot.cc] Error 139
 > gmake[1]: Leaving directory '/usr/pkg/src/lang/nodejs4/work/node-v4.4.5/=
 out'
 > gmake: *** [Makefile:45: node] Error 2
 > *** Error code 2
 > =
 
 > bash-4.3# pwd
 > /usr/pkg/src/lang/nodejs4/work/node-v4.4.5/deps/v8/tools/gyp
 > bash-4.3# ls -l
 > total 4180
 > -rw-------  1 root  wheel  2045528 May 26 13:59 mksnapshot.core
 > -rw-r--r--  1 root  wheel    74177 May 24 19:39 v8.gyp
 > bash-4.3# =
 
 > [...]
 JFT: unfortunately it seems that `mksnapshot' is compiled and then
 directly used during the build phase of lang/nodejs4 so unlike
 mongodb we can not use NOT_PAX_MPROTECT_SAFE here.
 
 For the moment the only work-around is to temporary disable PaX MPROTECT
 as Christos suggested and as you've done.
 
 
 Ciao,
 L.