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 0B2663858D34; Thu,  2 May 2024 07:03:26 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0B2663858D34
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1714633407;
	bh=RRQJwquFLLn2VHmMCrKs51wWLfp/OU2YNbm4pl5GvVw=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=kVEn2LVw/xnVC1KMwRUXY5Qs7xU5X9ooaqaYeRsGgBPg9oyNBAci7uShCn9FZxv7/
	 ld5gHqfiulqZTtkmLsCHMR2sc3+zujs1AD2Yx2n12ANG92/rXFKIQeY1KVP+GpnZFO
	 wKDQ/pFnZf73Qluul022Td2j+T/V+FEyxLVdC1GU=
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/114895] Build failure with !HAVE_WORKING_STAT
Date: Thu, 02 May 2024 07:03:26 +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: rguenth at gcc dot gnu.org
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: <bug-114895-4-38enaNLsl8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-114895-4@http.gcc.gnu.org/bugzilla/>
References: <bug-114895-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=3D114895

--- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> ---
So besides maybe no way to reproduce the failure the source still has the i=
ssue
described.=