From: "Thompson, David" <dthompson2@worcester.edu>
To: christoph vogelsberg <chrissvberg@gmx.de>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: General Question: Execution of binaries not built for GuixSD
Date: Wed, 22 Jun 2016 08:44:27 -0400 [thread overview]
Message-ID: <CAJ=RwfY7ib3qskG-tZpqOGqM4zfE+Ao0XWc2P-WY3ndWs6yWNg@mail.gmail.com> (raw)
In-Reply-To: <trinity-580e3ce2-7852-4cdd-89f4-89a895356f40-1466551285945@3capp-gmx-bs45>
On Tue, Jun 21, 2016 at 7:21 PM, christoph vogelsberg
<chrissvberg@gmx.de> wrote:
> Hello
>
> I have a fresh installation of GuixSD and I'm keen of learning more. I struggle with a concept and don't know how to circumvent best:
>
> Binaries built for ordinary Linux's (as, in my case, Firefox Developer Edition) expect libraries on certain standard pathes which doesn't exist on GuixSD. I found three possibilities that might work:
To be clear, an "ordinary" GNU/Linux system is one which uses the
Filesystem Hierarchy Standard, which GuixSD deliberately does not
conform to.
> * use fakechroot to make my user profile a pseudo root (disadvantage: I have no experience, it seams there is no package for that)
> * create symbolic links (disadvantage: new builts get a new path with a hash value and must be re-linked properly)
> * install a minimal Linux and use Guix instead of GuixSD (disadvantage: this would the point where I had capitulated)
>
> My question: is there an already elabored way, documentation and so on, for this specific problem?
The solution is to build the software from source to produce a binary
that is compatible with GuixSD. Guix has a GNU Icecat package that
may provide a good base for this.
HTH,
- Dave
next prev parent reply other threads:[~2016-06-22 12:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 23:21 General Question: Execution of binaries not built for GuixSD christoph vogelsberg
2016-06-22 10:50 ` Florian Paul Schmidt
2016-06-22 13:27 ` Florian Paul Schmidt
2016-06-22 13:53 ` Thompson, David
2016-06-22 14:06 ` ng0
2016-06-22 14:12 ` Florian Paul Schmidt
2016-06-22 12:44 ` Thompson, David [this message]
2016-06-24 18:19 ` General Question: What if Binary Building breaks? christoph vogelsberg
2016-06-24 18:55 ` ng0
2016-06-25 17:36 ` Leo Famulari
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='CAJ=RwfY7ib3qskG-tZpqOGqM4zfE+Ao0XWc2P-WY3ndWs6yWNg@mail.gmail.com' \
--to=dthompson2@worcester.edu \
--cc=chrissvberg@gmx.de \
--cc=help-guix@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).