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 r11-11234] libgfortran: avoid duplicate libraries in spec
Date: Sun, 11 Feb 2024 13:52:59 +0000 (GMT)	[thread overview]
Message-ID: <20240211135259.69A6F3858D20@sourceware.org> (raw)

https://gcc.gnu.org/g:407100bffa8c66e92fd4f6bfd2a083995b9dab93

commit r11-11234-g407100bffa8c66e92fd4f6bfd2a083995b9dab93
Author: Francois-Xavier Coudert <fxcoudert@gcc.gnu.org>
Date:   Sun Feb 11 14:51:39 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 95aa3f842a30..0ea15950514c 100644
--- a/libgfortran/libgfortran.spec.in
+++ b/libgfortran/libgfortran.spec.in
@@ -5,4 +5,4 @@
 #
 
 %rename lib liborig
-*lib: @LIBQUADSPEC@ -lm %(libgcc) %(liborig)
+*lib: @LIBQUADSPEC@ -lm %(liborig)

                 reply	other threads:[~2024-02-11 13:52 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=20240211135259.69A6F3858D20@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: 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).