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 D033F3858422; Thu, 13 Jul 2023 09:34:00 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D033F3858422
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1689240840;
	bh=KMFtk3/zdWys/D2zOif7dgdkq8qV4N1VOO7VeMt8LpU=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=pGD3nY0XRjBhXtrUFmWgKCc5epaaq+9V7YvINi1lbxEfij9cqzYGyPVjMNfoPc9kI
	 iRzUWrjXYZVjp6UHkqP1Q+/WL9T85R6ZvMHS70H9fCPGFhmEn00b8V/lMdAt9VfZG/
	 7+HXacjyLlCm/LHQPkKXxKMP0sDb1ExzL28Zqf8o=
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: Thu, 13 Jul 2023 09:34:00 +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-bL5eKdm8o1@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 #2 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot U=
ni-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 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?

We do: @LIBM@ is handled that way.

>> * 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.

Agreed: for me modifying the spec was a quick hack to avoid half the
failures in the testsuite run.=