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 8ABF73858C42; Thu, 16 Nov 2023 14:57:14 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8ABF73858C42
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1700146634;
	bh=z5C5i8SKWIAkZ9YWpv/iv11hPFbNnhR75EIkXiM4/nA=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=a3UwLePt/HINCSYp2elfp3eGcbLQPp7rhMYSjegcyqfSPInJOwzXkbVrP5Psr5Swk
	 9+lP0d3/2r8HXqnKygHiGjT2EpC4l83gCNzd91+ApGQsuvaFzhelLm1CSDHv/XKFYI
	 n+ysHxuCwZ1k46S7FIippuM61B1Ts0dBdZHrSWFk=
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/108865] gcc on Windows fails with Unicode path to source
 file
Date: Thu, 16 Nov 2023 14:57:13 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: driver
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 13.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-108865-4-ALyc64mEzj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-108865-4@http.gcc.gnu.org/bugzilla/>
References: <bug-108865-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=3D108865

--- Comment #43 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> Looks like what is being requested here is a windows-host-specific
> configuration option similar to the existing --disable-win32-registry, li=
ke
> for example --disable-win32-utf8-manifest with its corresponding
> --enable-win32-utf8-manifest (default).

Yes, this sounds like a good idea.

> Then the question is what can be done in configure.ac to raise some sort =
of
> flag that can be picked up from gcc/config.host, which is where the utf8
> resource objects get added.    According to its own doc, config.host is
> invoked by configure, so it should be possible to pass a simple flag from
> configure to config.host.    Perhaps setting a shell variable that can be
> checked inside config.host, like ${ENABLE_WIN32_UTF8_MANIFEST}, and pull =
in
> the utf-8 files only if that is true.

Yes, see the list of variables documented at the beginning of config.host f=
or
examples.=