From: ericonr <ericonr@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: Thu, 29 Oct 2020 06:13:59 +0100 [thread overview]
Message-ID: <20201029051359.3OvpFUUj0GdHmJSFIhPRqMWBKGIGunzSs-Qo6Mf197U@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: 986 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/issues/23557#issuecomment-718364461
Comment:
I'm using https://github.com/ericonr/purr-c , because it's a reasonably simple project of my own and I already had the code written.
Building an aarch64-musl static binary and using x86_64-musl's qemu, it all seems to work fine. The issue, instead, seems to be when using x86_64-musl's qemu with a binary built for aarch64-glibc, where I get "Temporary failure in name resolution". Using x86_64-glibc's qemu, all works fine.
Command line used, because, as warned by the linker, statically linking `getaddrinfo` requires dynamic modules at runtime: `QEMU_LD_PREFIX=masterdir-glibc/usr/aarch64-linux-gnu qemu-aarch64-static masterdir-glibc/purr-c/purr -d r https://google.com/`.
I have a gist for the 4 combinations of `qemu -strace`, `strace qemu` and glibc, musl hosts: https://gist.github.com/ericonr/95a41049b96e6256ab08a40bab311994
next prev parent reply other threads:[~2020-10-29 5:14 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
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 [this message]
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=20201029051359.3OvpFUUj0GdHmJSFIhPRqMWBKGIGunzSs-Qo6Mf197U@z \
--to=ericonr@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).