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 CD2DC3858D3C; Thu,  2 May 2024 07:16:19 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org CD2DC3858D3C
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1714634179;
	bh=0aXzBvsRSXBEVRMBqhnZjo7kftdEHyfMeX70PA3srUg=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=R+/3HAwposUCADw8+NxBQbgkUV6CgD9E1chHha4QWkrIP3Ch7/KEw7X6/Y2NHZ8Lb
	 kVjfVGESWX4ILWaeRxNTa5UfggJIV1jH+9eT7V0ZrbwGzdcuwxLeCc28AN+cCYykc+
	 PFQq97CTGfOnMewWsu2fdPhEpBw3uhdL/JuARd5k=
From: "sjames 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:16:19 +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: sjames 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-UmrO8PYRvT@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 #8 from Sam James <sjames at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #7)
> So besides maybe no way to reproduce the failure the source still has the
> issue
> described.

Sorry, not following -- jakub's attached one has #define _FILE_OFFSET_BITS =
64,
so we should be fine?=