From: Luis Machado <luis.machado@arm.com>
To: "Clément Chigot" <chigot@adacore.com>,
"Nick Clifton" <nickc@redhat.com>,
binutils@sourceware.org
Cc: Torbjorn SVENSSON <torbjorn.svensson@foss.st.com>
Subject: Re: [PATCH] bfd: handle codepage when opening files on MinGW
Date: Fri, 12 Aug 2022 15:45:32 +0100 [thread overview]
Message-ID: <2fe3fe60-4039-b9e8-4212-4d9f62e270cc@arm.com> (raw)
In-Reply-To: <CAJ307Egz7v6m9aK6MadKgfSnhmQ0WiDH2AfAp3wcRUJrUjHFYw@mail.gmail.com>
Hi Clément,
On 6/28/22 08:47, Clément Chigot via Binutils wrote:
> On Tue, Jun 28, 2022 at 9:27 AM Clément Chigot <chigot@adacore.com> wrote:
>>
>> Hi Nick,
>>
>> A few days ago, I've tried to open
>> https://sourceware.org/bugzilla/show_bug.cgi?id=25713
>> again because the new handling of Windows filename is triggering
>> issues for GNAT under MinGW.
>>
>> We've made the following changes attached. We aren't sure this
>> is the best solution, but it seems to work fine and it's what MinGW is
>> using internally.
>> If you find such a patch ok, I guess it would be logical to merge it
>> for 2.39.
>
> Oops, I've pushed a patch which was a bit old and doesn't apply anymore...
> This version is better.
>
> Sorry for the noise..
>
> Thanks
> Clément
It's been reported to me that this is causing some issues building binutils with mingw.
In fact, trying to build master binutils-gdb with Ubuntu 22.04's mingw-w64 8.0 or Ubuntu 20.04's mingw-w64 7.0.0 runs
into the following:
bfd/bfdio.c: In function ‘_bfd_real_fopen’:
bfd/bfdio.c:125:28: error: implicit declaration of function ‘___lc_codepage_func’ [-Werror=implicit-function-declaration]
125 | const unsigned int cp = ___lc_codepage_func();
next prev parent reply other threads:[~2022-08-12 14:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 7:27 Clément Chigot
2022-06-28 7:47 ` Clément Chigot
2022-06-28 14:52 ` Nick Clifton
2022-08-12 14:45 ` Luis Machado [this message]
2022-08-12 15:11 ` Clément Chigot
2022-08-12 15:13 ` Luis Machado
2022-08-15 11:07 ` Nick Clifton
2022-08-15 11:38 ` Torbjorn SVENSSON
2022-08-16 12:15 ` Luis Machado
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=2fe3fe60-4039-b9e8-4212-4d9f62e270cc@arm.com \
--to=luis.machado@arm.com \
--cc=binutils@sourceware.org \
--cc=chigot@adacore.com \
--cc=nickc@redhat.com \
--cc=torbjorn.svensson@foss.st.com \
/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).