public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit 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, 23 Nov 2023 00:49:20 +0000 [thread overview]
Message-ID: <bug-108865-4-c7RLruTXLC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108865-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108865
--- Comment #46 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jonathan Yong <jyong@gcc.gnu.org>:
https://gcc.gnu.org/g:4f1ebd54380e16927cd0085be939165870354eac
commit r14-5768-g4f1ebd54380e16927cd0085be939165870354eac
Author: Costas Argyris <costas.argyris@gmail.com>
Date: Mon Nov 20 17:58:16 2023 +0000
mingw: Exclude utf8 manifest [PR111170, PR108865]
Make the utf8 manifest optional (on by default and
explicitly off with --disable-win32-utf8-manifest)
in the mingw hosts.
Also eliminate duplication between the 32-bit and
64-bit mingw hosts by putting them both in the
same branch and special-case only the 64-bit long
long setting.
PR mingw/111170
PR mingw/108865
Signed-off-by: Costas Argyris <costas.argyris@gmail.com>
Signed-off-by: Jonathan Yong <10walls@gmail.com>
gcc/Changelog:
* configure.ac: Handle new --enable-win32-utf8-manifest
option.
* config.host: allow win32 utf8 manifest to be disabled
by user.
* configure: Regenerate.
next prev parent reply other threads:[~2023-11-23 0:49 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-20 21:11 [Bug driver/108865] New: " costas.argyris at gmail dot com
2023-02-20 21:23 ` [Bug driver/108865] " pinskia at gcc dot gnu.org
2023-02-20 21:39 ` costas.argyris at gmail dot com
2023-02-20 21:41 ` pinskia at gcc dot gnu.org
2023-02-25 14:15 ` costas.argyris at gmail dot com
2023-02-25 18:27 ` pinskia at gcc dot gnu.org
2023-02-28 21:01 ` costas.argyris at gmail dot com
2023-02-28 21:11 ` costas.argyris at gmail dot com
2023-02-28 21:14 ` pinskia at gcc dot gnu.org
2023-02-28 21:27 ` pinskia at gcc dot gnu.org
2023-02-28 22:07 ` costas.argyris at gmail dot com
2023-03-01 10:38 ` costas.argyris at gmail dot com
2023-03-01 17:08 ` costas.argyris at gmail dot com
2023-03-02 0:57 ` costas.argyris at gmail dot com
2023-03-02 1:11 ` pinskia at gcc dot gnu.org
2023-03-02 9:56 ` costas.argyris at gmail dot com
2023-03-02 23:50 ` pinskia at gcc dot gnu.org
2023-03-05 23:42 ` costas.argyris at gmail dot com
2023-03-05 23:50 ` pinskia at gcc dot gnu.org
2023-03-06 12:25 ` costas.argyris at gmail dot com
2023-03-09 15:00 ` cvs-commit at gcc dot gnu.org
2023-03-09 16:22 ` pinskia at gcc dot gnu.org
2023-03-22 10:00 ` lh_mouse at 126 dot com
2023-03-22 10:35 ` costas.argyris at gmail dot com
2023-03-22 15:37 ` lh_mouse at 126 dot com
2023-03-23 1:13 ` costas.argyris at gmail dot com
2023-03-23 4:48 ` lh_mouse at 126 dot com
2023-03-23 9:24 ` costas.argyris at gmail dot com
2023-03-23 9:53 ` costas.argyris at gmail dot com
2023-03-24 12:00 ` costas.argyris at gmail dot com
2023-03-24 13:33 ` rguenth at gcc dot gnu.org
2023-03-29 11:58 ` costas.argyris at gmail dot com
2023-03-29 12:01 ` costas.argyris at gmail dot com
2023-03-29 12:20 ` costas.argyris at gmail dot com
2023-11-15 0:05 ` peter0x44 at disroot dot org
2023-11-15 0:10 ` pinskia at gcc dot gnu.org
2023-11-15 0:13 ` pinskia at gcc dot gnu.org
2023-11-15 0:15 ` peter0x44 at disroot dot org
2023-11-15 1:31 ` lh_mouse at 126 dot com
2023-11-15 9:23 ` ebotcazou at gcc dot gnu.org
2023-11-15 13:16 ` costas.argyris at gmail dot com
2023-11-15 13:57 ` ebotcazou at gcc dot gnu.org
2023-11-16 13:41 ` costas.argyris at gmail dot com
2023-11-16 14:57 ` ebotcazou at gcc dot gnu.org
2023-11-18 2:41 ` aoliva at gcc dot gnu.org
2023-11-20 18:35 ` costas.argyris at gmail dot com
2023-11-23 0:49 ` cvs-commit at gcc dot gnu.org [this message]
2023-11-29 10:56 ` cvs-commit at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-108865-4-c7RLruTXLC@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).