GNU bug report logs - #53002
guix can't find gfortran-toolchain or gdc-toolchain

Previous Next

Full log

Message #13 received at 53002-done <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Liliana Marie Prikler <liliana.prikler <at> gmail.com>
Cc: 53002-done <at> debbugs.gnu.org, Jesse Gibbons <jgibbons2357 <at> gmail.com>
Subject: Re: bug#53002: guix can't find gfortran-toolchain or gdc-toolchain
Date: Tue, 11 Jan 2022 11:08:36 +0100

Hello,

Liliana Marie Prikler <liliana.prikler <at> 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’.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.