+5
-5
doc/using/configuration.chapter.md
+5
-5
doc/using/configuration.chapter.md
···- For allowing the build of a broken package once, you can use an environment variable for a single invocation of the nix tools:···- For allowing the build of an unsupported package once, you can use an environment variable for a single invocation of the nix tools:···- To temporarily allow all unfree packages, you can use an environment variable for a single invocation of the nix tools:···- To temporarily allow all insecure packages, you can use an environment variable for a single invocation of the nix tools:···For this to work fully, you must also have this script sourced when you are logged in. Try adding something like this to your `~/.profile` file:
···- For allowing the build of a broken package once, you can use an environment variable for a single invocation of the nix tools:···- For allowing the build of an unsupported package once, you can use an environment variable for a single invocation of the nix tools:···- To temporarily allow all unfree packages, you can use an environment variable for a single invocation of the nix tools:···- To temporarily allow all insecure packages, you can use an environment variable for a single invocation of the nix tools:···For this to work fully, you must also have this script sourced when you are logged in. Try adding something like this to your `~/.profile` file:
+1
-1
doc/using/overlays.chapter.md
+1
-1
doc/using/overlays.chapter.md
···This overlay uses Intel's MKL library for both BLAS and LAPACK interfaces. Note that the same can be accomplished at runtime using `LD_LIBRARY_PATH` of `libblas.so.3` and `liblapack.so.3`. For instance:
···This overlay uses Intel's MKL library for both BLAS and LAPACK interfaces. Note that the same can be accomplished at runtime using `LD_LIBRARY_PATH` of `libblas.so.3` and `liblapack.so.3`. For instance: