From: zimoun <zimon.toutoune@gmail.com>
To: bbb ee <blasforr@gmail.com>, 59278@debbugs.gnu.org
Subject: bug#59278: how gcc-toolchain can depends a package who doesn't exists?
Date: Tue, 15 Nov 2022 09:42:34 +0100 [thread overview]
Message-ID: <864jv0k3r9.fsf@gmail.com> (raw)
In-Reply-To: <CALNLCmUJOyvfjELjW-YcF+hDgwxPH1SoEcZm2hMOAtmt6vr36g@mail.gmail.com>
Hi,
On Tue, 15 Nov 2022 at 00:53, bbb ee <blasforr@gmail.com> wrote:
> in commit c81457, how gcc-toolchain can depends a package who doesn't
> exists?
The package exists, it is ’hidden’ – it means not accessible at the CLI
level. The ’inherit’ copies, so gcc-11 is also hidden, for instance.
--8<---------------cut here---------------start------------->8---
(define-public gcc-4.7
[...]
(hidden-package
(package
(name "gcc")
(version "4.7.4")
(define-public gcc-4.8
(package (inherit gcc-4.7)
(version "4.8.5")
[...]
(define-public gcc-11
(package
(inherit gcc-8)
(version "11.3.0")
--8<---------------cut here---------------end--------------->8---
The package ’gcc’ by itself is not barely useful because you also need
linker etc. Well, you usually need a complete toolchain, named
gcc-toolchain. ;-)
See manual: <https://guix.gnu.org/manual/devel/en/guix.html#The-GCC-toolchain>
So this is not a bug and I miss how what could be improved. Closing?
Cheers,
simon
next prev parent reply other threads:[~2022-11-15 14:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 23:53 bug#59278: how gcc-toolchain can depends a package who doesn't exists? bbb ee
2022-11-15 6:26 ` Julien Lepiller
2022-11-15 10:29 ` bbb ee
2022-11-15 8:42 ` zimoun [this message]
2022-11-15 21:42 ` bbb ee
2022-11-16 8:53 ` zimoun
2022-11-15 22:04 ` bbb ee
2022-11-15 10:30 ` bug#59278: bbb ee
2023-05-15 17:55 ` bug#59278: gcc@7 and higher are not hidden packages zimoun
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=864jv0k3r9.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=59278@debbugs.gnu.org \
--cc=blasforr@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).