unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: 53002-done@debbugs.gnu.org, Jesse Gibbons <jgibbons2357@gmail.com>
Subject: bug#53002: guix can't find gfortran-toolchain or gdc-toolchain
Date: Tue, 11 Jan 2022 11:08:36 +0100	[thread overview]
Message-ID: <87a6g2y47v.fsf@gnu.org> (raw)
In-Reply-To: <bf48216f254ff7f8d76dcecf255bf31b730618ed.camel@gmail.com> (Liliana Marie Prikler's message of "Tue, 04 Jan 2022 21:16:10 +0100")

Hello,

Liliana Marie Prikler <liliana.prikler@gmail.com> skribis:

> Am Dienstag, dem 04.01.2022 um 00:47 -0700 schrieb Jesse Gibbons:
>> Strange bug, guix can't find gfortran-toolchain even though it is a 
>> package defined publicly in one of the files it presumably searches.
>> 
>> `which guix` outputs the expected
>> "$HOME/.config/guix/current/bin/guix", 
>> so it probably isn't a problem with my guix home.
>> 
>> `guix package -A gfortran` returns nothing.
>> 
>> `guix package -A gcc-toolchain` shows several different versions of 
>> gcc-toolchain in gnu/packages/commencement.scm
>> 
>> `guix edit gcc-toolchain` opens the source where guix presumably
>> found the gcc-toolchain package definition. Within that file, 
>> gfortran-toolchain is defined publicly.
>> 
>> This is also the case for gdc-toolchain.
> Checking gfortran-toolchain inside the Guix REPL, its properties
> contain (hidden? . #t), which probably also applies to gdc-toolchain.

Indeed, that’s a regression introduced with ‘--tune’.

Fixed a couple of days ago in af1b5de6d8a54439ef3f7e1f5fe9a8e7d109972d.

Thanks,
Ludo’.




      reply	other threads:[~2022-01-11 10:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-04  7:47 bug#53002: guix can't find gfortran-toolchain or gdc-toolchain Jesse Gibbons
2022-01-04 20:16 ` Liliana Marie Prikler
2022-01-11 10:08   ` Ludovic Courtès [this message]

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=87a6g2y47v.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=53002-done@debbugs.gnu.org \
    --cc=jgibbons2357@gmail.com \
    --cc=liliana.prikler@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).