From: Tobias Geerinckx-Rice <me@tobias.gr>
To: 35551@debbugs.gnu.org
Cc: Bruno Haible <bruno@clisp.org>, 35551-done@debbugs.gnu.org
Subject: bug#35551: package gcc does not depend on binutils and glibc
Date: Sat, 04 May 2019 02:20:02 +0200 [thread overview]
Message-ID: <8736lvf4ul.fsf@nckx> (raw)
In-Reply-To: <87imurunjv.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 421 bytes --]
Bruno,
Welcome!
Nicolas Goaziou wrote:
> You are really looking for `gcc-toolchain' package. See section
> 2.6.6 in
> the manual.
Yup! :-)
‘Toolchain’ exactly describes what you're looking for, so I'm
going to go ahead and close this bug.
(Speaking as a user, I'd be annoyed to the point of switching if
my distro installed ‘binutils’ when asked for ‘gcc’.)
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2019-05-04 0:21 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-03 22:57 bug#35551: package gcc does not depend on binutils and glibc Bruno Haible
2019-05-03 23:27 ` Nicolas Goaziou
2019-05-04 0:20 ` Tobias Geerinckx-Rice [this message]
2019-05-04 1:34 ` Bruno Haible
2019-05-07 16:23 ` Tobias Geerinckx-Rice
2019-05-07 17:26 ` Bruno Haible
2019-05-07 16:04 ` Ludovic Courtès
2019-05-09 21:21 ` Ricardo Wurmus
2019-05-09 21:57 ` Bruno Haible
2019-05-10 6:18 ` Ricardo Wurmus
2019-05-10 8:07 ` Ludovic Courtès
2019-05-10 9:38 ` bug#35551: guix search Bruno Haible
2019-05-10 10:17 ` Ludovic Courtès
2019-05-10 10:22 ` Bruno Haible
2019-05-10 15:17 ` Ludovic Courtès
2019-05-10 14:21 ` Bruno Haible
2019-05-10 21:15 ` Ludovic Courtès
2019-05-10 22:04 ` Mark H Weaver
2019-05-10 22:38 ` Bruno Haible
2019-05-10 23:41 ` Tobias Geerinckx-Rice
2019-05-11 18:38 ` Mark H Weaver
2019-05-11 18:18 ` Mark H Weaver
2019-05-13 7:57 ` Ludovic Courtès
2019-05-13 15:39 ` znavko
2019-05-10 15:43 ` znavko
2019-05-10 21:22 ` Bruno Haible
2019-05-10 10:18 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8736lvf4ul.fsf@nckx \
--to=me@tobias.gr \
--cc=35551-done@debbugs.gnu.org \
--cc=35551@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 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.