From: Alex Kost <alezost@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 27389@debbugs.gnu.org
Subject: [bug#27389] [PATCH] doc: Explain how to use the GCC toolchain.
Date: Fri, 16 Jun 2017 16:00:02 +0300 [thread overview]
Message-ID: <87vanwnl4d.fsf@gmail.com> (raw)
In-Reply-To: <20170616075635.19382-1-rekado@elephly.net> (Ricardo Wurmus's message of "Fri, 16 Jun 2017 09:56:35 +0200")
Ricardo Wurmus (2017-06-16 09:56 +0200) wrote:
> * 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}).
>
> +@subsection The GCC toolchain
> +
> +@cindex GCC
> +@cindex 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
> +wrapper.
> +
> +@cindex 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
^
Shouldn't there be a comma after "By default"? Although, I see the
absence/presence of commas in such cases is inconsistent in
"guix.texi" anyway :-(
> +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
> +@code{GUIX_LD_WRAPPER_ALLOW_IMPURITIES}.
Great explanation!
--
Alex
next prev parent reply other threads:[~2017-06-16 13:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-16 7:56 [bug#27389] [PATCH] doc: Explain how to use the GCC toolchain Ricardo Wurmus
2017-06-16 12:55 ` Ludovic Courtès
2017-06-16 16:48 ` bug#27389: " Ricardo Wurmus
2017-06-16 13:00 ` Alex Kost [this message]
2017-06-16 16:47 ` [bug#27389] " Ricardo Wurmus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vanwnl4d.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=27389@debbugs.gnu.org \
--cc=rekado@elephly.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.