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 21:36:37 +0200 [thread overview]
Message-ID: <20210425193637.h7PJfr38JW_Kcg5vcqFv9zZfwbOKho18Z1D-lIvNfhY@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: 1150 bytes --]
New comment by digitalagedragon on void-packages repository
https://github.com/void-linux/void-packages/issues/29034#issuecomment-826378154
Comment:
Okay, cross-compiling for `armv6l` *from an i686 masterdir* works. In fact, it works so well that it generates a `/usr/bin/node` that depends on system `libatomic.so.1`.
```
morgan@dev-zone ~/src/void-packages 29034-nodejs-system-libraries
❯ file masterdir-x86/destdir/arm-linux-gnueabihf/nodejs-14.16.0/usr/bin/node
masterdir-x86/destdir/arm-linux-gnueabihf/nodejs-14.16.0/usr/bin/node: ELF 32-bit LSB pie executable, ARM, EABI5 version 1 (GNU/Linux), dynamically linked, interpreter /lib/ld-linux-armhf.so.3, BuildID[sha1]=2690603af7da094104bdd93eb17f3b10757d73af, for GNU/Linux 3.2.0, stripped
morgan@dev-zone ~/src/void-packages 29034-nodejs-system-libraries
❯ readelf -d masterdir-x86/destdir/arm-linux-gnueabihf/nodejs-14.16.0/usr/bin/node | grep libatomic
0x00000001 (NEEDED) Shared library: [libatomic.so.1]
```
I guess I'll try again targeting musl? If it only happens when building on armv6l native then I definitely won't be able to do anything...
next prev parent reply other threads:[~2021-04-25 19:36 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 [this message]
2021-04-25 19:50 ` digitalagedragon
2021-04-25 19:59 ` ericonr
2021-04-25 20:05 ` digitalagedragon
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=20210425193637.h7PJfr38JW_Kcg5vcqFv9zZfwbOKho18Z1D-lIvNfhY@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).