From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 21E7E3858D32; Fri, 13 Jan 2023 10:28:48 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 21E7E3858D32 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1673605728; bh=+XKcPdwJb3KI8XyaUqilCAXbziIo64SiDc8j3f3yKQE=; h=From:To:Subject:Date:In-Reply-To:References:From; b=MaywYRnKOcPGzMQLLL0h52i+y4hqrbgQvp6mp+8aX0+Co0Mc2D4ftIJg7OHneIgZT n7AKYDUQEL85/gUTxk6WKK7yMyEuZ6hVtYfotDJYg/AZ6o/CrJcf0QXt1rNQtKHKX4 kLDDy3KsN267ezBKdoDDEW5ODuIMd532XLJaioj0= From: "gnu.org at billz dot fastmail.fm" To: gcc-bugs@gcc.gnu.org Subject: [Bug driver/108350] Windows: invoking gcc via symlink does not work Date: Fri, 13 Jan 2023 10:28:47 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: driver X-Bugzilla-Version: 12.2.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: gnu.org at billz dot fastmail.fm 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: --- 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=3D108350 --- Comment #14 from Bill Zissimopoulos = --- (In reply to niXman from comment #13) > I figured out the building problem. >=20 > it seems to work as it should for symlink, but it doesn't work for hardli= nk. This is good news. Unless I misunderstand what you mean I think working for symlink, but not working for hardlink is expected behavior. There is no way to resolve a hardlink to a "real" path, all hardlinked paths are "real".=