public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "Clément Chigot" <chigot@adacore.com>
To: Luis Machado <luis.machado@arm.com>
Cc: Nick Clifton <nickc@redhat.com>,
	binutils@sourceware.org,
	 Torbjorn SVENSSON <torbjorn.svensson@foss.st.com>
Subject: Re: [PATCH] bfd: handle codepage when opening files on MinGW
Date: Fri, 12 Aug 2022 17:11:12 +0200	[thread overview]
Message-ID: <CAJ307EiOi+4qTZkUau2SSTMG+_rx52kgaspzqNbzY3JWbdFo6A@mail.gmail.com> (raw)
In-Reply-To: <2fe3fe60-4039-b9e8-4212-4d9f62e270cc@arm.com>

Hi Luis,

> 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();

Looking at the commit exposing this ___lc_codepage_func, it seems to have
been integrated only after 8.0.1 (cf
https://github.com/mirror/mingw-w64/commit/64cb5e8582d9004cfa4d90b189c80c6e1a35d7af)

I don't know if there is any define providing the version of MinGW (I
didn't find it).
Otherwise, I guess it'll have to be checked by the configure.

I won't have time to create a patch for that before next week (probably on
wednesday/thursday). Meanwhile, you should be able to recompile binutils
without this patch. As long as you don't have non-ASCII characters in your
filename, you should be fine.

But thanks for bringing that up !

Clément

  reply	other threads:[~2022-08-12 15:11 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
2022-08-12 15:11     ` Clément Chigot [this message]
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=CAJ307EiOi+4qTZkUau2SSTMG+_rx52kgaspzqNbzY3JWbdFo6A@mail.gmail.com \
    --to=chigot@adacore.com \
    --cc=binutils@sourceware.org \
    --cc=luis.machado@arm.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).