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 D7959385735A; Thu, 13 Jul 2023 09:30:25 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D7959385735A
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1689240625;
	bh=LDlqy8qcuu5j/oW6b5kD9wl+pRfbZuyqv6ToJih5Sp4=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=DE0tJCpJ3+0ulXZRXKxm55Qi8teQI0izcgy0V0wseH7ugzAj3hH664zJTVEbqb7UZ
	 9akJt2RAP45ReVcywG1+wmqbzF47yIC/E1AqFvDuAVjH4kEPiEBfTKBgwaLQ+zPaEd
	 c7K+O1XtB6iZMKDBzlfT9+Y6EzM+l7xmPTYwW8Bo=
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/110651] libgfortran.spec links twice with libgcc
 spec
Date: Thu, 13 Jul 2023 09:30:25 +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: iains at gcc dot gnu.org
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-mU9ZyXwrXN@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 #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 beta =
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?

> * Disable ld warnings with -w in the spec, probably using some
> @TARGET_LDFLAGS@.
>=20
> * Disable ld warnings globally in the Darwin driver code.  That may be
>   undisable since it would disable possibly benign warnings, too.

I think we need to fix the specs not work around with disabled warnings.=