From: digitalagedragon <digitalagedragon@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: nodejs packages should be fixed to use more system libraries
Date: Sun, 25 Apr 2021 22:05:42 +0200 [thread overview]
Message-ID: <20210425200542.F2_63xpjjOZ5QmrWVh33fbjxUpEDI4w6ZcFXYb36gHY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29034@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 673 bytes --]
New comment by digitalagedragon on void-packages repository
https://github.com/void-linux/void-packages/issues/29034#issuecomment-826382047
Comment:
Oh, that's fun. I think I have some idea of how you could fix this (adapting `ppc32.patch` to link with `-latomic` on `arm` as well as mips/ppc32, though I don't know enough about libatomic to know if that would cause performance issues on armv7 where you do have native atomic, or enough about Node's build process to know if it's possible to target that more finely than just `arm`), but if it's not getting packaged anyways does it really matter? Maybe that should be its own issue in case the builders get sorted out?
next prev parent reply other threads:[~2021-04-25 20:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 18:51 [ISSUE] nodejs packages should be udpated " ericonr
2021-02-24 18:56 ` nodejs packages should be fixed " ericonr
2021-04-25 17:07 ` digitalagedragon
2021-04-25 18:14 ` digitalagedragon
2021-04-25 18:23 ` ericonr
2021-04-25 18:26 ` digitalagedragon
2021-04-25 18:26 ` digitalagedragon
2021-04-25 19:17 ` digitalagedragon
2021-04-25 19:36 ` digitalagedragon
2021-04-25 19:50 ` digitalagedragon
2021-04-25 19:59 ` ericonr
2021-04-25 20:05 ` digitalagedragon [this message]
2021-04-25 20:44 ` digitalagedragon
2021-04-25 22:46 ` digitalagedragon
2021-04-26 15:13 ` ericonr
2021-04-26 15:15 ` digitalagedragon
2021-04-26 15:19 ` ericonr
2021-04-26 15:22 ` digitalagedragon
2021-04-28 12:32 ` [ISSUE] [CLOSED] " ericonr
2021-04-28 12:32 ` ericonr
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=20210425200542.F2_63xpjjOZ5QmrWVh33fbjxUpEDI4w6ZcFXYb36gHY@z \
--to=digitalagedragon@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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.
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).