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 F2D32385E010; Fri,  8 Mar 2024 17:42:33 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org F2D32385E010
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1709919753;
	bh=/oYvlZzaoeJP2GhrNXSLnhei8sGHDCGcWJM+AsH+Xvo=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=EDXvgX4jrwUAfBKelPsUPCr9/QVhNas9SNBM3NR+cnMtvtI59y20XMx3S1JLf24NP
	 D99M3XG2eWhnz0fomKiJYDSt+Ao3c6qWB2Af5NyNQ08fmWx2kaX9+XrB4P6HRC8mLC
	 Yz0DWy9va6snJxi9SzyMoyu85SaZK4T2+uB5c9PM=
From: "kyle.shores44 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/110644] Error in gfc_format_decoder
Date: Fri, 08 Mar 2024 17:42:33 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 13.1.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kyle.shores44 at gmail dot com
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: <bug-110644-4-dicl5KnrRy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-110644-4@http.gcc.gnu.org/bugzilla/>
References: <bug-110644-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=3D110644

--- Comment #18 from Kyle Shores <kyle.shores44 at gmail dot com> ---
(In reply to Steve Kargl from comment #16)
> On Fri, Mar 08, 2024 at 04:44:52PM +0000, kyle.shores44 at gmail dot com
> wrote:
> > I have not made a smaller example, but we have since removed json-fortr=
an as a
> > dependency for tuv-x.
> >=20
> > So it should be easier to view the failure in tuv-x. I have not made th=
e time
> > to try to reduce the code to an example, but maybe this could help.
> >=20
> > Following this instructions should show an error
> >=20
> > git clone https://github.com/NCAR/tuv-x
> > cd tuv-x
> > mkdir build && cd build
> > FC=3Dg++-13 cmake ..
> > make
> >=20
>=20
> FC=3Dg++-13?
>=20
> Should that be gfortran13?
>=20
> I get
>=20
> % env FC=3D/usr/home/sgk/work/x/bin/g++ cmake ..
> -- The Fortran compiler identification is GNU 14.0.1
> -- The CXX compiler identification is GNU 14.0.1
> -- The C compiler identification is GNU 14.0.1
> -- Detecting Fortran compiler ABI info
> -- Detecting Fortran compiler ABI info - failed
> -- Check for working Fortran compiler: /usr/home/sgk/work/x/bin/g++
> -- Check for working Fortran compiler: /usr/home/sgk/work/x/bin/g++ - bro=
ken
> CMake Error at
> /usr/local/share/cmake/Modules/CMakeTestFortranCompiler.cmake:59 (message=
):
>   The Fortran compiler
>=20
>     "/usr/home/sgk/work/x/bin/g++"

ya, sorry about that. I'm more used to typing g++ than gfortran, muscle mem=
ory
kicked in=