public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/110651] New: libgfortran.spec links twice with libgcc spec
Date: Thu, 13 Jul 2023 09:22:03 +0000 [thread overview]
Message-ID: <bug-110651-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110651
Bug ID: 110651
Summary: libgfortran.spec links twice with libgcc spec
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libfortran
Assignee: unassigned at gcc dot gnu.org
Reporter: ro at gcc dot gnu.org
CC: burnus at gcc dot gnu.org, fxcoudert at gcc dot gnu.org,
iains at gcc dot gnu.org
Target Milestone: ---
Host: x86_64-apple-darwin23.0.0
Target: x86_64-apple-darwin23.0.0
Build: x86_64-apple-darwin23.0.0
When bootstrapping current trunk on macOS 14.0 beta 3 with Xcode 15 beta 4,
every single fortran link test FAILs like
FAIL: gfortran.dg/c-interop/allocatable-dummy.f90 -O0 (test for excess
errors)
Excess errors:
ld: warning: ignoring duplicate library '-lemutls_w'
ld: warning: ignoring duplicate library '-lgcc'
The link line ends in
-lgfortran -lemutls_w -lgcc -lquadmath -lemutls_w -lgcc -lSystem
-no_compact_unwind -idsym -dsym
I could trace this to libgfortran.spec, which has
%rename lib liborig
*lib: %{static-libquadmath:libquadmath.a%s;:-lquadmath} %(libgcc) %(liborig)
The libgcc spec is included twice, once explicitly here and another time in
%(liborig). I have no idea why this is done this way: this already was in
the original patch that introduced libgfortran.spec.in:
commit 1ec601bf9fb0fbc39b3a6cb90450500f857adae8
Author: Francois-Xavier Coudert <fxcoudert@gcc.gnu.org>
Date: Tue Nov 16 21:23:19 2010 +0000
re PR fortran/32049 (Support on x86_64 also kind=16)
I see quite a number of possible solutions:
* Get rid of %(libgcc) in libgfortran.spec.in.
* Include it conditionally depending on a configure test.
* Disable ld warnings with -w in the spec, probably using some
@TARGET_LDFLAGS@.
* Disable ld warnings globally in the Darwin driver code. That may be
undisable since it would disable possibly benign warnings, too.
next reply other threads:[~2023-07-13 9:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 9:22 ro at gcc dot gnu.org [this message]
2023-07-13 9:22 ` [Bug libfortran/110651] " ro at gcc dot gnu.org
2023-07-13 9:30 ` iains at gcc dot gnu.org
2023-07-13 9:34 ` ro at CeBiTec dot Uni-Bielefeld.DE
2023-07-21 11:39 ` ro at CeBiTec dot Uni-Bielefeld.DE
2023-12-19 8:17 ` fxcoudert at gcc dot gnu.org
2024-02-10 15:48 ` iains at gcc dot gnu.org
2024-02-11 13:53 ` fxcoudert at gcc dot gnu.org
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=bug-110651-4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).