public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: "François-Xavier Coudert" <fxcoudert@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r12-10151] libgfortran: avoid duplicate libraries in spec Date: Sun, 11 Feb 2024 13:48:33 +0000 (GMT) [thread overview] Message-ID: <20240211134833.378873858D20@sourceware.org> (raw) https://gcc.gnu.org/g:56071adae867e63248816f5879339eec27785383 commit r12-10151-g56071adae867e63248816f5879339eec27785383 Author: Francois-Xavier Coudert <fxcoudert@gcc.gnu.org> Date: Sun Feb 11 14:47:54 2024 +0100 libgfortran: avoid duplicate libraries in spec The linking of libgcc is already present in %(liborig), so the current situation duplicates libraries. This was not an issue until macOS's new linker started giving warnings for such cases. libgfortran/ChangeLog: PR libfortran/110651 * libgfortran.spec.in: Remove duplicate libraries. Diff: --- libgfortran/libgfortran.spec.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libgfortran/libgfortran.spec.in b/libgfortran/libgfortran.spec.in index 367d485c230c..058ee5775bf2 100644 --- a/libgfortran/libgfortran.spec.in +++ b/libgfortran/libgfortran.spec.in @@ -5,4 +5,4 @@ # %rename lib liborig -*lib: @LIBQUADSPEC@ @LIBM@ %(libgcc) %(liborig) +*lib: @LIBQUADSPEC@ @LIBM@ %(liborig)
reply other threads:[~2024-02-11 13:48 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240211134833.378873858D20@sourceware.org \ --to=fxcoudert@gcc.gnu.org \ --cc=gcc-cvs@gcc.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: linkBe 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).