From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id CBE95385E021; Thu, 14 Mar 2024 16:25:17 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org CBE95385E021 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1710433517; bh=nBHNO1HrtXQdac7e+hviEnpf9zfA4Uv6Q6Im/dVGxRo=; h=From:To:Subject:Date:In-Reply-To:References:From; b=mCl7PwZe0UITuNJepGUfHKP2PHWvZOcpwHvWNy30zhWJTZznFXCzAzssYiugVXsx7 DoUMvt3NpZ3gykeggiEBzXr36IdiSNW0X6xOVMi8KLuBIIdVcvj+qVuoAlwbg67pKV ACn03QG5BgCI2ZPa/rChuRqydf0dVsgcmC94N5Y0= From: "peter0x44 at disroot dot org" To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/110710] LTO linker on Windows creates an invalid Makefile Date: Thu, 14 Mar 2024 16:25:17 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: lto X-Bugzilla-Version: 12.2.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: peter0x44 at disroot dot org X-Bugzilla-Status: WAITING X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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=3D110710 --- Comment #10 from peter0x44 at disroot dot org --- > For a workaround, I would recommend busybox-w32. It's what w64devkit uses. > You can just put it on your PATH and see if it solves that issue. Just to be completely explicit, what I mean to do is: Download busybox.exe from here: https://frippery.org/busybox/ Rename it to "sh.exe", and place it on your PATH.=