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 16A4A3857C58; Thu, 30 Dec 2021 19:05:00 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 16A4A3857C58
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/103866] AM_PROG_LIBTOOL not compatible with
 GCC_NO_EXECUTABLES
Date: Thu, 30 Dec 2021 19:05:00 +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: 12.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
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: <bug-103866-4-9ifAX8pnij@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-103866-4@http.gcc.gnu.org/bugzilla/>
References: <bug-103866-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
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Dec 2021 19:05:00 -0000

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D103866

--- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Nicolas Noble from comment #6)
> While a bit tangential from the narrow topic of this bug, it may be
> noteworthy that I just tried using the --with-newlib kludge here, and
> compilation still fails, with something new:
>=20
> checking for the value of EOF... configure: error: computing EOF failed



Yes, I have a simple patch for that.


>=20
> Checking the logs, this fails because it can't find stdio.h. Meaning the
> --with-newlib kludge isn't an actually valid method towards actual bare
> metal, and needs something a bit more fleshed out?


Yes, and even with that fixed, more checks for $is_hosted are needed for
stdint.h types. I have a patch for that too, but I'm not happy with it yet.

The same problems with stdio.h are listed in the other bug, but the fixes
suggested there are completely wrong, and the abuse is completely unaccepta=
ble.=