unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Gary Johnson <lambdatronic@disroot.org>
To: help-guix@gnu.org
Subject: What happened to gfortran-toolchain?
Date: Thu, 06 Jan 2022 11:39:13 -0500	[thread overview]
Message-ID: <87lezsq0dj.fsf@disroot.org> (raw)

Hi Guix,

I finally got around to running `guix pull` and `guix package -u` on my
system now that the holidays are over, and I got a notification that
the gfortran-toolchain package had been removed. Sure enough, running
`guix package -s gfortran-toolchain` and even `guix package -s gfortran`
return no results at all.

After a bit of digging, I managed to track down the gfortran-toolchain
package definition to gnu/packages/commencement.scm, where it looks
perfectly normal to me.

```
(define-public gfortran-toolchain
  (package (inherit (make-gcc-toolchain gfortran))
    (synopsis "Complete GCC tool chain for Fortran development")
    (description "This package provides a complete GCC tool chain for
Fortran development to be installed in user profiles.  This includes
gfortran, as well as libc (headers and binaries, plus debugging symbols
in the @code{debug} output), and binutils.")))
```

However, when I follow its reference to the
gfortran package over to gnu/packages/gcc.scm, I see this: 

```
(define-public gfortran
  (hidden-package
   (custom-gcc gcc
               "gfortran" '("fortran")
               %generic-search-paths)))
```

Could this hidden-package form be the culprit here? Was hiding gfortran
an intentional change to Guix System, or was this an accident? If the
former, what is the current recommended approach for Fortran programming
on Guix?

Thanks,
  Gary

-- 
GPG Key ID: 7BC158ED
Use `gpg --search-keys lambdatronic' to find me
Protect yourself from surveillance: https://emailselfdefense.fsf.org
=======================================================================
()  ascii ribbon campaign - against html e-mail
/\  www.asciiribbon.org   - against proprietary attachments

Why is HTML email a security nightmare? See https://useplaintext.email/

Please avoid sending me MS-Office attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html


             reply	other threads:[~2022-01-06 16:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-06 16:39 Gary Johnson [this message]
2022-01-06 17:43 ` What happened to gfortran-toolchain? Remco
2022-01-10 16:14   ` Gary Johnson

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=87lezsq0dj.fsf@disroot.org \
    --to=lambdatronic@disroot.org \
    --cc=help-guix@gnu.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.
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).