From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 9479C3858409; Fri, 21 Jul 2023 11:39:39 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9479C3858409
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1689939579;
	bh=z9iuYlDVg6y9XuWuKdWn33neO88DVFlXhlYkFkhbBtg=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=vBwfAWZjsz2CaILxc7hW0xRuZj7h1sgxndxEHaxf3vbxYNQ5OMg5u3K6dEj7MSPMb
	 YyrcHqsShyLYpESvs1kaSfez0CQW/ScX63Uphnv/tgvESgxgfrZSZRWNMprRYJR0dN
	 z82klxE4oqBAc7cLUnDCTCdkS6qFOECS3WLu6vPE=
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/110651] libgfortran.spec links twice with libgcc
 spec
Date: Fri, 21 Jul 2023 11:39:39 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libfortran
X-Bugzilla-Version: 14.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ro at CeBiTec dot Uni-Bielefeld.DE
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 14.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-110651-4-AbmUrmrhCA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-110651-4@http.gcc.gnu.org/bugzilla/>
References: <bug-110651-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D110651

--- Comment #3 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot U=
ni-Bielefeld.DE> ---
> --- Comment #2 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot
> Uni-Bielefeld.DE> ---
>> --- Comment #1 from Iain Sandoe <iains at gcc dot gnu.org> ---
>> (In reply to Rainer Orth from comment #0)
>>> When bootstrapping current trunk on macOS 14.0 beta 3 with Xcode 15 bet=
a 4,
>>> every single fortran link test FAILs like
>>
>>> * Get rid of %(libgcc) in libgfortran.spec.in.
>>>=20
>>> * Include it conditionally depending on a configure test.
>>
>> Hmm .. I thought we already had configure tests to customise the spec for
>> Darwin?
>> FX?
>
> We do: @LIBM@ is handled that way.

FWIW, I've now removed the %(libgcc) from libgfortran.spec.in locally:
on all of *-*-solaris2.11, x86_64-pc-unix-gnu, and
x86_64-apple-darwin23.0.0 there were no regressions.

It seems ever more important to understand why it was introduced in the
first place, before even considering adding it conditionally.=