From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 3161B3858282; Tue, 19 Dec 2023 08:17:23 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 3161B3858282 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1702973843; bh=SykKpqyLpOvEBFzcy+LGHFtm1ozpHzOOh696fXvFBes=; h=From:To:Subject:Date:In-Reply-To:References:From; b=udVeIkpH2isg91SBcroyaR66FePzl7127LrJgLBG3QQrmodOWk2f2+N8Lub87t/kf pnRQ6dIMeiXg10VhUIlBEMrxwDh3GqGykdvxV3rWUXOFTl6ccbK5K4XuveVyrR+r76 W4Eq4M0qKXPhjp5xR2qGhCuZfZE02BVglwxS3vP0= From: "fxcoudert at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/110651] libgfortran.spec links twice with libgcc spec Date: Tue, 19 Dec 2023 08:17:22 +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: patch X-Bugzilla-Severity: normal X-Bugzilla-Who: fxcoudert at gcc dot gnu.org X-Bugzilla-Status: NEW 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: keywords bug_status cf_reconfirmed_on bug_file_loc everconfirmed Message-ID: In-Reply-To: References: 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: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D110651 Francois-Xavier Coudert changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |patch Status|UNCONFIRMED |NEW Last reconfirmed| |2023-12-19 URL| |https://gcc.gnu.org/piperma | |il/gcc-patches/2023-Decembe | |r/640943.html Ever confirmed|0 |1 --- Comment #4 from Francois-Xavier Coudert = --- I introduced the original behaviour and I'm not sure I remember why. I've propose to remove the duplication, because I cannot see a single case where= it could be useful. Patch posted at https://gcc.gnu.org/pipermail/gcc-patches/2023-December/640943.html=