From: zimoun <zimon.toutoune@gmail.com>
To: Bruno Haible <bruno@clisp.org>
Cc: 41038@debbugs.gnu.org
Subject: bug#41038: gcc creates binaries that don't find their shared libraries
Date: Mon, 4 May 2020 11:06:35 +0200 [thread overview]
Message-ID: <CAJ3okZ21BJTdJ2DxMOZuxssSDJ0FaC=2PYO7+94zFH9jY+JZsA@mail.gmail.com> (raw)
In-Reply-To: <2050118.Ql0zV9tn6O@omega>
Dear Ludo and Bruno,
On Mon, 4 May 2020 at 01:10, Bruno Haible <bruno@clisp.org> wrote:
> The question "What packages do I need to do normal C development?" should
> really be documented.
>
> How about a doc section - at the beginning of the chapter
> https://guix.gnu.org/manual/en/html_node/Development.html - that says:
>
> Packages needed for C development
> =================================
>
> For C development, you will typically need the packages
> make gcc-toolchain gdb
>
> Do NOT install glibc and binutils explicitly, as they would shadow
> the 'ld' wrapper that is necessary for proper operation of GCC.
Does it make sense to provide example/sample of manifests for
developing in the main languages?
And add advices in the manual? For example:
guix package -m /etc/guix/minimal-opinionated-tools-for-C.scm
guix package -m /etc/guix/minimal-opinionated-tools-for-Python.scm
Well, I do not know what the correct location for such "examples"
files. Folder /etc/? Other?
And with a better name than "minimal-opinionated-tools-for-".
WDYT?
All the best,
simon
next prev parent reply other threads:[~2020-05-04 9:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-02 23:55 bug#41038: gcc creates binaries that don't find their shared libraries Bruno Haible
2020-05-03 21:07 ` Ludovic Courtès
2020-05-03 23:09 ` Bruno Haible
2020-05-04 8:50 ` zimoun
2020-05-04 9:06 ` zimoun [this message]
2020-05-04 9:30 ` Ludovic Courtès
2020-05-04 9:59 ` zimoun
2020-05-04 19:52 ` Ludovic Courtès
2020-05-06 17:42 ` bug#41038: [PATCH] doc: Reword "The GCC toolchain" zimoun
2020-05-15 16:59 ` zimoun
2020-05-15 19:42 ` Nicolas Goaziou
2020-05-16 14:57 ` zimoun
2020-05-16 15:19 ` Ludovic Courtès
2020-05-03 22:12 ` bug#41038: gcc creates binaries that don't find their shared libraries Danny Milosavljevic
2020-05-05 9:30 ` Ludovic Courtès
2020-05-05 11:17 ` Bruno Haible
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJ3okZ21BJTdJ2DxMOZuxssSDJ0FaC=2PYO7+94zFH9jY+JZsA@mail.gmail.com' \
--to=zimon.toutoune@gmail.com \
--cc=41038@debbugs.gnu.org \
--cc=bruno@clisp.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).