From: FX Coudert <fxcoudert@gmail.com>
To: Jerry D <jvdelisle2@gmail.com>
Cc: fortran@gcc.gnu.org
Subject: Re: [PATCH] libgfortran: avoid duplicate libraries in spec
Date: Tue, 19 Dec 2023 22:10:48 +0100 [thread overview]
Message-ID: <782CA6E4-41B3-4B73-99B8-B62714FC5FE1@gmail.com> (raw)
In-Reply-To: <46639a0f-04d6-4136-a12d-c614a921f5a3@gmail.com>
Hi,
> I am getting side notes about people having these issues with gfortran 13. Is this something that should be backported.
I have already backported it in the latest Homebrew package (because we have many users complaining about it). I intend to backport but will wait for a conservative amount of time before doing so.
> Apparently it is causing some none gfortran compilations to break, but I do not know if this is the same issue.
Don’t think so. I can have a look if you give me a pointer.
FX
next prev parent reply other threads:[~2023-12-19 21:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 8:02 FX Coudert
2023-12-19 21:04 ` Jerry D
2023-12-19 21:10 ` FX Coudert [this message]
2023-12-19 21:12 ` Jerry D
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=782CA6E4-41B3-4B73-99B8-B62714FC5FE1@gmail.com \
--to=fxcoudert@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=jvdelisle2@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.
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).