unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Malte Gerdes <malte.f.gerdes@gmail.com>
To: noloader@gmail.com
Cc: 43303@debbugs.gnu.org
Subject: bug#43303: GCC package name
Date: Thu, 10 Sep 2020 08:18:43 +0200	[thread overview]
Message-ID: <CAMVpQiVF28N6FGmcwohiK_uY-4BoUs1iQJerUDJugO7GL+FsoA@mail.gmail.com> (raw)
In-Reply-To: <CAH8yC8kcLJJi-V6ekgzCANV+JjvvrhJbuDf4OR+85NZEueR7hg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1156 bytes --]

Hi,

the GCC package itself isn't to useful. I think you are looking for the
gcc-toolchain package which installs GCC, binutils and libc.

Malte

On Thu, 10 Sep 2020, 07:22 Jeffrey Walton, <noloader@gmail.com> wrote:

> Hi Everyone,
>
> It took me about 15 minutes to install GCC on Guix because Guix named
> the GCC package libgccjit.
>
> I understand Guix package manager is powerful. I think you should use
> an alias feature (or whatever it is called under Guix), and create and
> few aliases to help with administration:
>
>    gcc -> libgccjit
>    g++ -> libgccjit
>    gcc-c++ -> libgccjit
>
> These are the names developers expect for the compiler. They don't
> expect a name like libgccjit.
>
> With the aliases in place, a command like 'guix install gcc' works as
> expected.
>
> Without the aliases (and absent a sane package name), people have to
> lookup the documentation and read how to use the package manager for a
> simple task like installing the compiler. When 50 or 100 developers
> waste 15 minutes of their time, that's about 1 man-week wasted.
> There's no reason to waste man-weeks on simple tasks.
>
> Thanks in advance.
>
>
>
>

[-- Attachment #2: Type: text/html, Size: 1670 bytes --]

  reply	other threads:[~2020-09-10  6:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-10  5:20 bug#43303: GCC package name Jeffrey Walton
2020-09-10  6:18 ` Malte Gerdes [this message]
2020-09-10  8:34 ` zimoun
2020-09-10 10:33 ` Ludovic Courtès
2020-09-10 11:16   ` zimoun
2020-09-10 11:32     ` Ricardo Wurmus
2020-09-10 11:43       ` zimoun
2020-09-10 13:22         ` Ricardo Wurmus
2020-09-11 16:11     ` zimoun
2020-09-10 11:22   ` Jeffrey Walton

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=CAMVpQiVF28N6FGmcwohiK_uY-4BoUs1iQJerUDJugO7GL+FsoA@mail.gmail.com \
    --to=malte.f.gerdes@gmail.com \
    --cc=43303@debbugs.gnu.org \
    --cc=noloader@gmail.com \
    /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).