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 F1C973858409; Tue, 21 Nov 2023 09:43:44 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org F1C973858409
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1700559824;
	bh=TMgm2hRoup1EXSvaOxqnfdgdj33HTUOkrq0k+gDEMTw=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=lFfMVNwf3jUBXUXOB9GkzSSWxWk7wAxYDJn+CHom8ghiRcoq5W7wxHsgmyVAy2kE6
	 Xr9B7Jw+HMPK4aaLBJD0XKoSclyohenUQFeYAH/7eQu6ubiKggVFIlrMtAD2GSQQNj
	 wRe7vbetu+Zc5yID0eJGUC+wLliyf7PdW+Cs7HJI=
From: "costas.argyris at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/111170] [13/14 regression] Malformed manifest does not
 allow to run gcc on Windows XP (Accessing a corrupted shared library) since
 r13-6552-gd11e088210a551
Date: Tue, 21 Nov 2023 09:43:41 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 13.2.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: costas.argyris at gmail dot com
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-111170-4-mcbTJzgWTX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-111170-4@http.gcc.gnu.org/bugzilla/>
References: <bug-111170-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=3D111170

--- Comment #10 from Costas Argyris <costas.argyris at gmail dot com> ---
> I suspect there should be an `AC_ARG_ENABLE` in configure.ac?

It doesn't appear to be necessary to me.    It also wasn't part of the advi=
ce
of https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D108865#c44 as far as I can
tell.

>From the two examples given there, with_avrlibc is used just through its sh=
ell
variable without any corresponding AC_ARG_WITH (couldn't find any with git =
grep
avrlibc anyway).

It also worked in my builds which were picking up the new
--disable-win32-utf8-manifest option (or its absence), so it doesn't seem t=
o be
necessary to make any other changes.

Did you get any failures and suspect it's due to AC_ARG_ENABLE missing?=