From: ludo@gnu.org (Ludovic Courtès)
To: Federico Beffa <beffa@ieee.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: build -K environment-variables
Date: Sun, 05 Jun 2016 14:52:48 +0200 [thread overview]
Message-ID: <87eg8bsspr.fsf@gnu.org> (raw)
In-Reply-To: <CAKrPhPOB+iF3zHcgZ-=nEsTBOT2PUvEOdr=Eb7X_VTYXAvQ+og@mail.gmail.com> (Federico Beffa's message of "Sat, 4 Jun 2016 21:58:45 +0200")
Federico Beffa <beffa@ieee.org> skribis:
> On Sat, Jun 4, 2016 at 9:46 PM, Thompson, David
> <dthompson2@worcester.edu> wrote:
>> On Sat, Jun 4, 2016 at 12:23 PM, Federico Beffa <beffa@ieee.org> wrote:
>>> Hi,
>>>
>>> the content of the 'environment-variables' file left after a failed
>>> build do look odd...
>>>
>>> $ pwd
>>> /tmp/guix-build-chez-sockets-0.0-1.f90e817.drv-2
>>> $ cat environment-variables | grep "drv-0"
>>> export NIX_BUILD_TOP="/tmp/guix-build-chez-sockets-0.0-1.f90e817.drv-0"
>>> export PWD="/tmp/guix-build-chez-sockets-0.0-1.f90e817.drv-0/source"
>>> export TEMP="/tmp/guix-build-chez-sockets-0.0-1.f90e817.drv-0"
>>> export TEMPDIR="/tmp/guix-build-chez-sockets-0.0-1.f90e817.drv-0"
>>> export TMP="/tmp/guix-build-chez-sockets-0.0-1.f90e817.drv-0"
>>> export TMPDIR="/tmp/guix-build-chez-sockets-0.0-1.f90e817.drv-0"
>>
>> What is odd about them?
>
> That the files are placed into /tmp/....drv-2, but the variables point
> to /tmp/...drv-0.
Ah ha! That’s because of/thanks to the deterministic build directory
names now used by the daemon (commit
cb9601029ea164b86bdf997f7160d494c15d344b).
https://www.gnu.org/software/guix/manual/html_node/Build-Environment-Setup.html
(Scroll down.)
HTH,
Ludo’.
prev parent reply other threads:[~2016-06-05 12:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-04 16:23 build -K environment-variables Federico Beffa
2016-06-04 19:46 ` Thompson, David
2016-06-04 19:58 ` Federico Beffa
2016-06-05 12:52 ` Ludovic Courtès [this message]
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=87eg8bsspr.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=beffa@ieee.org \
--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 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.