summary refs log tree commit diff
path: root/gnu/services/vnc.scm
diff options
context:
space:
mode:
authorLudovic Courtès <ludo@gnu.org>2023-11-26 22:58:27 +0100
committerLudovic Courtès <ludo@gnu.org>2023-11-26 23:34:47 +0100
commitc936853a646fbb2b55e20a8374b9f93b8838f5a3 (patch)
treef84938b79e00a07c4b12f4bf3d21b211200ba8e6 /gnu/services/vnc.scm
parent176440c056fdde6da98b11720989b1ed060ec97c (diff)
downloadguix-c936853a646fbb2b55e20a8374b9f93b8838f5a3.tar.gz
gnu: commencement: Make ‘glibc-final’ immune to ‘%current-target-system’.
Previously, the value memoized for ‘glibc-final’ was influenced by that
of ‘%current-target-system’ since it is used as a default argument to
‘libc-for-target’.  Thus, due to the order in which modules were loaded
versus the time at which ‘%current-target-system’ was set, it was
possible to end up with ‘glibc-final’ set to the “wrong” libc, for
instance when doing:

  guix build -f guix.scm --target=i586-pc-gnu

from another project such as the Shepherd.

This is similar to the problem fixed in
625a847d2a554168bec6e294888d9d1f8ab03d08.

* gnu/packages/commencement.scm (glibc-final-with-bootstrap-bash)
(glibc-final): Explicitly pass (%current-system) as the first argument
to ‘libc-for-target’ so that the value of ‘%current-target-system’ at
that time has no influence.

Change-Id: I2f05898b8f9d1f99d4c75108441c7ad38728225f
Diffstat (limited to 'gnu/services/vnc.scm')
0 files changed, 0 insertions, 0 deletions