From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 1DC673858C2D; Mon, 29 Jan 2024 23:44:28 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 1DC673858C2D DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1706571868; bh=ePUKaDm71UQwUdHdqJwoHPq/IYYB/BzPNRUCuz/aQbo=; h=From:To:Subject:Date:In-Reply-To:References:From; b=FNNKsKn+p0/lL0+WONlV/jnjR4IZjYMCpEnQp5j+Mq6fevRXwt/rM44IEe9yfH0uq fyPLd3KUCEq0SGMG2TMgOHITDNlWdMYvxNqqSLDcJA5lmZJrmEAJ/xwk6wbxwz2YgI TYw7jrQV6kbKquAN61NKiiFvkWXzenqhutF+av4s= From: "lennoxhoe at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/97813] std::filesystem::equivalent returning incorrect results on MinGW due to symlinks Date: Mon, 29 Jan 2024 23:44:27 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 10.2.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: lennoxhoe at gmail dot com 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: --- 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=3D97813 --- Comment #5 from Lennox Ho --- Thanks for the insight. I think the only potential blocker would be CreateSymbolicLinkW requires at least Vista/WinSer2008. I'm not able to figure out MinGW (or at least mingw-w64)'s OS requirements. I might look into contributing a patch to enable Windows symlink support sometime in the future. In the meantime, I have a patch for std::filesytem::hard_link_count for Windows. https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D113663 Thanks=