all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "christoph vogelsberg" <chrissvberg@gmx.de>
To: help-guix@gnu.org
Subject: General Question: Execution of binaries not built for GuixSD
Date: Wed, 22 Jun 2016 01:21:25 +0200	[thread overview]
Message-ID: <trinity-580e3ce2-7852-4cdd-89f4-89a895356f40-1466551285945@3capp-gmx-bs45> (raw)

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:

* 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?

so long
cvog (Christoph Vogelsberg)

             reply	other threads:[~2016-06-21 23:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-21 23:21 christoph vogelsberg [this message]
2016-06-22 10:50 ` General Question: Execution of binaries not built for GuixSD 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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=trinity-580e3ce2-7852-4cdd-89f4-89a895356f40-1466551285945@3capp-gmx-bs45 \
    --to=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. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.