From: ejolson2005 <ejolson2005@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: qemu-aarch64-static works in glibc but the musl version is missing certain network functions.
Date: Tue, 14 Jul 2020 05:52:42 +0200 [thread overview]
Message-ID: <20200714035242.q48lYegb3aPP8B3zlGVLcguzmLd6K-GQB8wyprwS1D0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23557@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 773 bytes --]
New comment by ejolson2005 on void-packages repository
https://github.com/void-linux/void-packages/issues/23557#issuecomment-657950605
Comment:
The resolv.conf in the chroot looks like
```
domain wulf
search wulf math.unr.edu
nameserver 192.168.174.129
```
The name server is running on the internal LAN but accessing one of the Google public name servers doesn't change the behavior.
Note the root filesystem in the chroot did not come from an aarch64 version of Void Linux but is aarch64 Debian. My understanding is that qemu-aarch64-static is statically linked (whether from glibc or musl versions of Void), so copying them around should just work, and it does at least copying the one from the glibc system to the musl system. Everything else is the same.
next prev parent reply other threads:[~2020-07-14 3:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-14 3:42 [ISSUE] " ejolson2005
2020-07-14 3:44 ` ericonr
2020-07-14 3:51 ` ejolson2005
2020-07-14 3:52 ` ejolson2005
2020-07-14 3:52 ` ejolson2005 [this message]
2020-07-14 3:55 ` ejolson2005
2020-07-14 4:00 ` ejolson2005
2020-07-18 5:24 ` sgn
2020-10-29 2:31 ` ericonr
2020-10-29 2:48 ` richfelker
2020-10-29 5:13 ` ericonr
2020-10-29 6:32 ` richfelker
2021-02-11 18:22 ` [ISSUE] [CLOSED] " 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=20200714035242.q48lYegb3aPP8B3zlGVLcguzmLd6K-GQB8wyprwS1D0@z \
--to=ejolson2005@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).