From: ludo@gnu.org (Ludovic Courtès)
To: Alexander Vorobiev <alexander.vorobiev@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Daemon update
Date: Fri, 22 May 2015 15:45:18 +0200 [thread overview]
Message-ID: <877fs0k9ox.fsf@gnu.org> (raw)
In-Reply-To: <CAGOCFPUhZVpB6ZKR4gEejzHeePV5bSWAZONqpam65aeSOD=M0Q@mail.gmail.com> (Alexander Vorobiev's message of "Thu, 21 May 2015 20:47:48 -0500")
Alexander Vorobiev <alexander.vorobiev@gmail.com> skribis:
> Doesn't binary distribution have hardcoded /gnu/* paths?
Yes it does.
> I can't use those unfortunately. We have a standard configuration of
> RHEL 6.5 installed on hundreds of servers and any modifications of the
> root directory (and all other "standard" directories) layout are out
> of question.
OK. Note that using a store other than /gnu/store prevents you from
using substitutes from hydra.gnu.org (just mentioning it if that is of
interest to you.)
> Would it be too hard to add an environment variable(s) pointing to a
> Guix's store and cache directories so that the binary build of the
> daemon doesn't depend on the hardcoded values? Thanks, Alex
There are two issues here:
1. File names hard-coded in the RUNPATH and other places of the
‘guix-daemon’ binary of the tarball.
2. The store directory that ‘guix-daemon’ targets.
#2 can actually be changed at run-time via the (purposefully
undocumented) ‘NIX_STORE_DIR’ environment variable (see ‘test-env.in’ in
the source tree.)
#1 means that if you want to run the ‘guix-daemon’ binary from the
binary tarball, you’ll have to somehow satisfy its requirements. You
might be able to unpack the tarball in an arbitrary directory, and then
define ‘LD_LIBRARY_PATH’ so that ‘guix-daemon’ finds all the .so files
that it needs and are provided by the binary tarball (libstdc++.so,
libgcrypt.so, libsqlite3.so, libc.so, etc.)
Once ‘guix-daemon’ is running, you could run ‘guix environment guix’,
and from there you could build Guix from source.
But that is really hacky, and perhaps not particularly easier than
building a newer GCC on your machine.
Alternately, you could build a suitable binary tarball on another
machine: just install and configure Guix with the options that you need,
and run ‘make guix-binary.x86_64-linux.tar.xz’.
WDYT?
Ludo’.
next prev parent reply other threads:[~2015-05-22 13:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 14:15 Daemon update Ludovic Courtès
2015-05-21 3:03 ` Alex Vorobiev
2015-05-21 7:24 ` Taylan Ulrich Bayırlı/Kammer
2015-05-21 8:24 ` Ludovic Courtès
2015-05-22 1:47 ` Alexander Vorobiev
2015-05-22 8:35 ` Taylan Ulrich Bayırlı/Kammer
2015-05-22 13:45 ` Ludovic Courtès [this message]
2015-05-27 3:27 ` Alexander Vorobiev
2015-05-27 15:18 ` Ludovic Courtès
2015-05-27 20:10 ` Alexander Vorobiev
2015-05-27 20:51 ` Ludovic Courtès
2015-05-28 17:56 ` Alexander Vorobiev
2015-05-29 20:57 ` Ludovic Courtès
2015-05-29 22:34 ` Alexander Vorobiev
2015-05-31 19:14 ` Ludovic Courtès
2015-06-01 16:50 ` Alexander Vorobiev
2015-06-01 19:58 ` Ludovic Courtès
2015-06-01 20:23 ` Alexander Vorobiev
2015-06-02 5:26 ` Alexander Vorobiev
2015-06-03 8:24 ` Ludovic Courtès
2015-06-03 16:04 ` Alexander Vorobiev
-- strict thread matches above, loose matches on Subject: below --
2015-05-12 7:58 Ludovic Courtès
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=877fs0k9ox.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=alexander.vorobiev@gmail.com \
--cc=guix-devel@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 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).