Summary: | net-libs/nodejs-0.12.0 on hardened - /bin/sh: line 1: 11066 Segmentation fault [in] ".../work/node-v0.12.0/out/Release/mksnapshot" --log-snapshot-positions --logfile ".../work/node-v0.12.0/out/Release/obj.target/v8_snapshot/geni/snapshot.log" ... | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | Johan Bergström <bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | fordfrog, hardened, mva, patrick, proxy-maint |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | emerge log |
Description
Toralf Förster
2015-02-20 12:16:19 UTC
Still applicable to 0.12.2. Btw, I just discussed with Hardened Team and they suggested to patch buildsystem to use paxmark.sh for paxmarking mksnapshot. (I guess, they mean paxmark.sh from elfix package). (In reply to Vadim A. Misbakh-Soloviov (mva) from comment #1) > Still applicable to 0.12.2. > > Btw, I just discussed with Hardened Team and they suggested to patch > buildsystem to use paxmark.sh for paxmarking mksnapshot. > (I guess, they mean paxmark.sh from elfix package). Yes. These annoying bugs require pax marking during build under a pax kernel. So if you were to build this under a vanilla kernl, and pax mark at the end, it would work too, the problem is *during* the build. I don't know nodejs internals, but I assume that if you can figure out where in the build system it runs mksnapshot the first time, just do `paxmark.sh m mksnapshot` the line before and you should be good. (In reply to Anthony Basile from comment #2) > (In reply to Vadim A. Misbakh-Soloviov (mva) from comment #1) > > Still applicable to 0.12.2. > > > > Btw, I just discussed with Hardened Team and they suggested to patch > > buildsystem to use paxmark.sh for paxmarking mksnapshot. > > (I guess, they mean paxmark.sh from elfix package). > > Yes. These annoying bugs require pax marking during build under a pax > kernel. So if you were to build this under a vanilla kernl, and pax mark at > the end, it would work too, the problem is *during* the build. > > I don't know nodejs internals, but I assume that if you can figure out where > in the build system it runs mksnapshot the first time, just do `paxmark.sh m > mksnapshot` the line before and you should be good. I'll have a look at this. Here's a work in progress of an ebuild that means to address these problems (and all other open nodejs issues). It's the latest version of iojs and once this is merge I'll port it back to the nodejs 0.12.x branch. Please let me know if pax-marking works for you: https://github.com/gentoo/gentoo-portage-rsync-mirror/pull/95 (In reply to Johan Bergström from comment #4) > Here's a work in progress of an ebuild that means to address these problems > (and all other open nodejs issues). It's the latest version of iojs and once > this is merge I'll port it back to the nodejs 0.12.x branch. Please let me > know if pax-marking works for you: > https://github.com/gentoo/gentoo-portage-rsync-mirror/pull/95 So, you're suggesting to try to install iojs-1.6.4 from PR instead of nodejs? (In reply to Vadim A. Misbakh-Soloviov (mva) from comment #5) > So, you're suggesting to try to install iojs-1.6.4 from PR instead of nodejs? Correct. As you may or may not know, iojs is a fork of nodejs with a much more active community. If the PR ebuild works for you, I'll port all changes to a nodejs 0.12.x ebuild as well. It seems to install fine with both enabled and disabled "snapshot" USE flag ;) (In reply to Vadim A. Misbakh-Soloviov (mva) from comment #7) > It seems to install fine with both enabled and disabled "snapshot" USE flag > ;) great news. *** Bug 539342 has been marked as a duplicate of this bug. *** This should be fixed since 0.12.2-r2. |