Browse Source

Notes

master
pjotrp 4 years ago
parent
commit
53423b7404
  1. 8
      DEVELOPERS.org
  2. 4
      GUIX-NO-ROOT.org
  3. 16
      INSTALL.org

8
DEVELOPERS.org

@ -23,6 +23,12 @@ GNU Guix has a number of things going for it:
GNU Guix you get the same environment, all the way down to glibc.
4. GNU Guix comes with great *tooling*. Because we are all developers!
Most importantly Guix provides *isolation*. That means that if you use
different combinations of dependencies you can rely on the system to
provide them. Examples are using different versions of
interpreters/compilers and different versions of libraries. Simply
create a profile for each combination.
* Installing GNU Guix
See the online documentation and [[INSTALL.org]].
@ -94,7 +100,7 @@ When you hit an error like
it means the Guix installed linker can not find its files. If are
creating Guix linked binaries you should set LIBRARY_PATH to the Guix
profile/lib. If are creating locally linked binaries, use the local
linker!
linker! Don't use the Guix ld.
ld is part of the Guix binutils package.

4
GUIX-NO-ROOT.org

@ -497,8 +497,8 @@ turned out to be a proot switch -r
** warn-about-old-distro
Guix versions won't run if they are old. Use a more recent version
of the daemon.
Guix versions won't run if they are old. Use a more recent version of
the daemon. It may also help to remove ~/.config/guix if it exists.
Also see this inside proot - probably because $HOME/.config is not
mounted. Happens when the client is run inside proot bash.

16
INSTALL.org

@ -34,10 +34,11 @@
- [[#install-gnu-guix-systemsoftware-distribution-sd][Install GNU Guix system/software distribution (SD)]]
- [[#trouble-shooting][Trouble shooting]]
- [[#failed-to-connect-to-daemon][Failed to connect to daemon]]
- [[#x509-certificate-error][X.509 certificate error]]
- [[#x509-certificate-error][X.509 certificate error]]
- [[#error-build-failed-substituter-substitute-died-unexpectedly][error: build failed: substituter `substitute' died unexpectedly]]
- [[#packagesscm-error][packages.scm error]]
- [[#error-while-loading-shared-libraries-libgslso23-cannot-open-shared-object-file-no-such-file-or-directory][error while loading shared libraries: libgsl.so.23: cannot open shared object file: No such file or directory]]
- [[#updating-guix-hell][updating Guix hell]]
* Introduction
@ -392,7 +393,7 @@ that ends up in $GUIX_LOCPATH/2.23/
and all should be well - at least for tools installed with Guix.
Not recommended: set the LOCPATH to that of your underlying
distribution - incompatibilities may exist.
distribution - incompatibilities may exist. See also the [[https://www.gnu.org/software/guix/manual/html_node/Application-Setup.html][Guix docs]].
* Fonts
@ -571,7 +572,7 @@ a clean shell
screen -S guix-build # I tend to build in screen
env -i /bin/bash --login --noprofile --norc
~/.guix-profile/bin/guix environment guix --ad-hoc help2man git strace \
pkg-config less vim binutils coreutils grep --no-grafts
pkg-config less vim binutils coreutils grep guile-git --no-grafts
bash # you may want this shell
#+end_src sh :lang bash
@ -895,7 +896,7 @@ If you get on a guix command
it means the daemon is not running.
** X.509 certificate error
** X.509 certificate error
When you get the X.509 certificate error it means that openssl can not find the certificates.
@ -939,3 +940,10 @@ good thing to try anyway.
** error while loading shared libraries: libgsl.so.23: cannot open shared object file: No such file or directory
You are probably not linking with ld-wrapper but are using a native /bin/ld
** updating Guix hell
When you get stuck with Guix it is possible to unpack the binary installation
tarball and copy the files in gnu/store into your own store. Now you can
run that guix from there
: /gnu/store/hash-guix-version/bin/guix package -i guix
Loading…
Cancel
Save