Summary: | dev-util/electron: node binary breaks after merge phase | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Sora Lee <soleera> |
Component: | Current packages | Assignee: | Elvis Pranskevichus <elvis> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | jstein, proxy-maint |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
Build Log (xz archive)
System Info |
Description
Sora Lee
2017-05-24 09:12:29 UTC
Please attach the two files (compressed, if large). The developers use tools which rely on attachments and we do not want to depend on third party servers. Created attachment 474210 [details]
Build Log (xz archive)
Created attachment 474212 [details]
System Info
Apologies for that, I hadn't used the attachment feature before. I also have an archive of the working directory if it's needed, although it's too big to upload as an attachment. As a side note, I wouldn't be surprised if there were issues with other files in the package too; I am unable to run any electron based app, even pre-compiled ones (e.g. AppImages). So far I've tested Hyper, Gitkraken, Discord, and Atom without success. Have you tried a newer GCC version? Given that you're on Ryzen I wouldn't be surprised that there's a mis-compilation issue somewhere. (In reply to Elvis Pranskevichus from comment #6) > Have you tried a newer GCC version? Given that you're on Ryzen I wouldn't > be surprised that there's a mis-compilation issue somewhere. Yes, I've tried gcc-6.3.0 and changed to --march=znver1, however it makes no difference. I just realised that I called node when testing the working directory, not ./node, so I was probably using my nodejs version of the binary instead (i.e., the binary was probably corrupted even before it was merged to the live system). For some reason I didn't notice the message when emerging electron the first time, but it looks like grkernsec is the the issue here. For some reason I didn't notice the message when emerging electron the first time, but it looks like grkernsec is the the issue here. |