From: Christof Marti <chrmarti@microsoft.com>
To: "musl@lists.openwall.com" <musl@lists.openwall.com>
Subject: Re: Loading of Node.js native module segfaults in Alpine 3.10 (works in 3.9)
Date: Tue, 10 Sep 2019 09:49:32 +0000 [thread overview]
Message-ID: <A3427473-3EA3-4C8D-886C-A1F6FEB5A744@microsoft.com> (raw)
In-Reply-To: <687f6c2b-8570-07b7-3e76-a7cdcbbb97dc@adelielinux.org>
Thanks everyone for the quick replies!
I recompiled nodejs with the below patch and checked with the machines we saw the issue with that this indeed fixes it.
I'll check on the issue for aports if they can include it in their build (https://gitlab.alpinelinux.org/alpine/aports/issues/10767).
Thanks,
Christof
On 9/6/19, 6:06 PM, "A. Wilcox" <awilfox@adelielinux.org> wrote:
On 06/09/2019 08:10, Christof Marti wrote:
> We have a Node.js native module that fails to load on Alpine 3.10
> (musl-1.1.22-r3). It loads fine on Alpine 3.9 (musl-1.1.20-r4) and other
> (Debian / CentOS base) Linux distros. I also specifically tested with
> alpine:3.10 and debian:8 Docker images and Node.js 10.16.3 to rule out
> differences between Node.js versions and the Debian image does not show
> the problem.
I am wondering if our patch (
https://code.foxkit.us/adelie/packages/blob/753435f2/user/node/stack-silliness.patch
) would fix this. Is there any way you can try to build the Node
package with this patch applied locally? Or, alternatively, you could
try to install our Node package directly (
https://distfiles.adelielinux.org/adelie/1.0-beta4/user/x86_64/node-10.16.3-r0.apk
- though I'm not sure this will install cleanly on an Alpine system ).
Best to you and yours,
--arw
--
A. Wilcox (awilfox)
Project Lead, Adélie Linux
https://www.adelielinux.org
prev parent reply other threads:[~2019-09-10 9:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 13:10 Christof Marti
2019-09-06 13:23 ` Rich Felker
2019-09-06 14:44 ` Szabolcs Nagy
2019-09-06 16:06 ` A. Wilcox
2019-09-10 9:49 ` Christof Marti [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=A3427473-3EA3-4C8D-886C-A1F6FEB5A744@microsoft.com \
--to=chrmarti@microsoft.com \
--cc=musl@lists.openwall.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).