From: Jonathan Frederickson <jonathan@terracrypt.net>
To: Mark H Weaver <mhw@netris.org>
Cc: 35591@debbugs.gnu.org
Subject: bug#35591: Segfault on flatpak remote-add
Date: Sun, 05 May 2019 18:47:57 -0400 [thread overview]
Message-ID: <2493358.OLn4tNdJs0@terrabase> (raw)
In-Reply-To: <87muk0sf4e.fsf@netris.org>
[-- Attachment #1: Type: text/plain, Size: 1879 bytes --]
On Sunday, May 5, 2019 6:36:06 PM EDT Mark H Weaver wrote:
> My knowledge of Flatpak is weak, but in general, foreign pre-compiled
> binaries will not work on Guix unless they are statically linked.
> Traditional dynamically-linked executables expect to find a dynamic
> linker and system shared libraries in /lib or /lib64, which do not exist
> on a Guix system. It is also fairly common for foreign binaries to
> depend on standard files and programs in /usr, /bin, and /sbin, none of
> which are present on a Guix system except for /bin/sh.
I believe Flatpak applications are statically linked. (Or rather, individual
applications may be dynamically linked, but they are eventually combined with
a full OS image similarly to how Docker works.)
> I'm sorry I don't have a better answer for you, but Guix was not
> designed to run foreign pre-compiled binaries. If that's important to
> you, it might be that Guix is not a good fit for you.
It's not the most important thing to me; it may end up being one more reason
for me to start attempting to package things for Guix! But it would still be
nice to be able to run the same tooling that e.g. some Gnome developers are
using to publish their apps across distros. (And the fact that Flatpak is
packaged for Guix seems to imply that it should be possible to use it here.)
> However, if your goal is to run Guix-compiled programs in a sandbox,
> that's something we are certainly very interested in, and we could use
> help. We have "guix container" as a building block, and I know that
> some Guix users have experimented with running e.g. GNU IceCat within a
> container. I don't know the current status of those efforts. Hopefully
> someone more knowledgable in this area will chime in.
While this isn't my immediate goal, this is also something that I'm interested
in, if someone else knows more about this!
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-05-05 23:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-05 20:05 bug#35591: Segfault on flatpak remote-add Jonathan Frederickson
2019-05-05 22:36 ` Mark H Weaver
2019-05-05 22:47 ` Jonathan Frederickson [this message]
2019-10-31 10:50 ` Ben Sturmfels
2020-05-11 20:23 ` Ricardo Wurmus
2020-05-11 21:38 ` Ricardo Wurmus
2020-05-14 5:26 ` Ricardo Wurmus
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2493358.OLn4tNdJs0@terrabase \
--to=jonathan@terracrypt.net \
--cc=35591@debbugs.gnu.org \
--cc=mhw@netris.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).