[Top][All Lists]

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

[debbugs-tracker] bug#27389: closed ([PATCH] doc: Explain how to use the

From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#27389: closed ([PATCH] doc: Explain how to use the GCC toolchain.)
Date: Fri, 16 Jun 2017 16:49:02 +0000

Your message dated Fri, 16 Jun 2017 18:48:39 +0200
with message-id <address@hidden>
and subject line Re: [bug#27389] [PATCH] doc: Explain how to use the GCC 
has caused the debbugs.gnu.org bug report #27389,
regarding [PATCH] doc: Explain how to use the GCC toolchain.
to be marked as done.

(If you believe you have received this mail in error, please contact

27389: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=27389
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: [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 *********************************************************************

--- End Message ---
--- Begin Message --- Subject: Re: [bug#27389] [PATCH] doc: Explain how to use the GCC toolchain. Date: Fri, 16 Jun 2017 18:48:39 +0200 User-agent: mu4e 0.9.18; emacs 25.2.1
Ludovic Courtès <address@hidden> writes:

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

Thanks for the suggestions.  I’ve pushed the patch as 2f0c4b828 after
making the requested changes.

  GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC

--- End Message ---

reply via email to

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