PF4Public

> /usr/lib64/electron-26/node: line 3: 29 Segmentation fault Could Raptor fix this issue as well?

> Is this ppc64 specific? Doesn't sound like so. It never sagfaulted on amd64 on me, but I'll check it again with the latest electron. >If it ends up being...

No issues with `temp-fix` on x86 and latest electron: ``` [ebuild U *] app-editors/vscode-9999::pf4public [1.83.0::pf4public] USE="badge-providers build-online* electron-26 substitute-urls temp-fix -api-proposals -electron-19 -electron-20 -electron-21 -electron-22 -electron-23 -electron-24 -openvsx -reh -reh-web"...

Hmm, it gets even more interesting. GitHub workflow for 1.83.1 failed with ``` [12:39:21] 'vscode-linux-x64-min' errored after 23 min [12:39:21] Error: Command failed: yarn list --prod --json /usr/lib64/electron-25/node: line 3:...

After updating electron to 26.4.0 I couldn't build vscode-1.83.1 and got the same SEGFAULT. I've just added electron-27. Looks good so far, you can give it a try. 

>'-Dnode_gyp_dir=/home/niko/.nvm/versions/node/v18.15.0/lib/node_modules/npm/node_modules/node-gyp', Why is it there? Should't it be in node's dir of electron?

That should be the answer to build failure

If it wants to build electron module it should use electron and electron's node and electron's node-gyp, nothing else.

So, have you managed to make it work?

I've moved `/usr/include/electron-24/node/` into `/usr/include/electron-24/node/include/node/` and tried building element and vscode and they both succeeded, so maybe those includes should go into that folder at the first place? @darkbasic Could...