Github messages for voidlinux
 help / color / mirror / Atom feed
From: duncancmt-alt <duncancmt-alt@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: proot segfault on aarch64-musl
Date: Sun, 27 Sep 2020 01:08:29 +0200	[thread overview]
Message-ID: <20200926230829.AkTGncu_eQa-DkfV987CrCSnntwAzp5igafi3K933sw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24918@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 852 bytes --]

New comment by duncancmt-alt on void-packages repository

https://github.com/void-linux/void-packages/issues/24918#issuecomment-699559084

Comment:
I ended up "solving" this problem by using a variation on the program [detailed on this page](https://blog.w1r3.net/2017/09/23/live-switching-void-linux-from-glibc-to-musl.html) to overlay the glibc `/usr` on top of the rest of the filesystem so that glibc programs work appropriately. I'm a little wary of suid binaries, but this one seems simple enough? I'm not sure if that actually should close this issue, though, because the underlying problem still exists.

(Yes, this isn't @duncancmt , but I'm locked out of that account until I fix the issue I talked about in #25125 and get back into my semi-broken main system. Or until I salvage what data I can from that system and move on with my life.)

  parent reply	other threads:[~2020-09-26 23:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-15  0:58 [ISSUE] " duncancmt
2020-09-19  3:50 ` fosslinux
2020-09-19 14:15 ` duncancmt
2020-09-19 14:47 ` Duncaen
2020-09-26 23:06 ` duncancmt-alt
2020-09-26 23:08 ` duncancmt-alt [this message]
2020-10-12  1:03 ` duncancmt
2020-10-12  1:03 ` [ISSUE] [CLOSED] " duncancmt

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=20200926230829.AkTGncu_eQa-DkfV987CrCSnntwAzp5igafi3K933sw@z \
    --to=duncancmt-alt@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).