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

[Ludovic Courtès]

Ricardo Wurmus <address@hidden> skribis:

> * doc/guix.texi (Application Setup): Add subsection "The GCC toolchain".

[...]

> +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

s/library/Library/

> +debugging symbols in the 'debug' output), Binutils, and a linker

s/'debug'/@code{debug}/

> +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

s/Guix store/store/

> +ensure purity.  This can be annoying when using the toolchain to link

s/purity/``purity''/

I’m nitpicking but I think it’s great to add this section.  Thank you!

Ludo’.