[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug#27389] [PATCH] doc: Explain how to use the GCC toolchain.

From: Ricardo Wurmus
Subject: [bug#27389] [PATCH] doc: Explain how to use the GCC toolchain.
Date: Fri, 16 Jun 2017 09:56:35 +0200

* doc/guix.texi (Application Setup): Add subsection "The GCC toolchain".
 doc/guix.texi | 24 ++++++++++++++++++++++++
 1 file changed, 24 insertions(+)

diff --git a/doc/guix.texi b/doc/guix.texi
index 97fa1b786..b9912a440 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -1441,6 +1441,30 @@ some reason, you want to avoid auto-loading Emacs 
packages installed
 with Guix, you can do so by running Emacs with @code{--no-site-file}
 option (@pxref{Init File,,, emacs, The GNU Emacs Manual}).
address@hidden The GCC toolchain
address@hidden GCC
address@hidden ld-wrapper
+Guix offers individual compiler packages such as @code{gcc} but if you
+are in need of a complete toolchain for compiling and linking source
+code what you really want is the @code{gcc-toolchain} package.  This
+package provides a complete GCC toolchain for C/C++ development,
+including GCC itself, the GNU C library (headers and binaries, plus
+debugging symbols in the 'debug' output), Binutils, and a linker
address@hidden attempt to use impure library, error message
+The wrapper's purpose is to inspect the @code{-L} and @code{-l} switches
+passed to the linker, add corresponding @code{-rpath} arguments, and
+invoke the actual linker with this new set of arguments.  By default the
+linker wrapper refuses to link to libraries outside the Guix store to
+ensure purity.  This can be annoying when using the toolchain to link
+with local libraries.  To allow references to libraries outside the
+store you need to define the environment variable
 @c TODO What else?
 @c *********************************************************************

reply via email to

[Prev in Thread] Current Thread [Next in Thread]