public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Luis Machado <luis.machado@arm.com>
To: "Torbjörn SVENSSON" <torbjorn.svensson@foss.st.com>,
	binutils@sourceware.org
Subject: Re: [PATCH] bfd: Define func prototype for old mingw
Date: Mon, 15 Aug 2022 11:01:06 +0100	[thread overview]
Message-ID: <503a5a7b-4e94-105f-5242-5364b6d49701@arm.com> (raw)
In-Reply-To: <20220815084902.3630298-1-torbjorn.svensson@foss.st.com>

Just some nits...
On 8/15/22 09:49, Torbjörn SVENSSON wrote:
> In commit 68e80d96a84282d547f3b3c1234c99009521630c, the usage of
> ___lc_codepage_func was introduced to determine the current encoding.
> Prior to version 9.0 of MinGW-w64, the function prototype for
> ___lc_codepage_func was missing and caused
> error: implicit declaration of function ‘___lc_codepage_func’
> when building.  This changeset adds a conditonal definition of
> ___lc_codepage_func to allow a sucessful build with MinGW-w64.

sucessful -> successful
> 
> Signed-off-by: Torbjörn SVENSSON <torbjorn.svensson@foss.st.com>
> ---
>   bfd/bfdio.c | 5 +++++
>   1 file changed, 5 insertions(+)
> 
> diff --git a/bfd/bfdio.c b/bfd/bfdio.c
> index a7c7d5bd363..59f79203b88 100644
> --- a/bfd/bfdio.c
> +++ b/bfd/bfdio.c
> @@ -29,6 +29,11 @@
>   #if defined (_WIN32)
>   #include <windows.h>
>   #include <locale.h>
> +
> +#if defined(__MINGW64_VERSION_MAJOR) && __MINGW64_VERSION_MAJOR < 9
> +/* This prototype was added to locale.h in version 9.0 of MinaGW-w64.  */

MinaGW-w64 -> MinGW-w64
> +_CRTIMP unsigned int __cdecl ___lc_codepage_func(void);

I don't see any occurrences of CRTIMP in binutils-gdb. Should we not use that?

> +#endif
>   #endif
>   
>   #ifndef S_IXUSR


  reply	other threads:[~2022-08-15 10:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-15  8:49 Torbjörn SVENSSON
2022-08-15 10:01 ` Luis Machado [this message]
2022-08-15 10:19   ` Torbjorn SVENSSON
2022-08-16 14:18 ` Nick Clifton
2022-08-16 17:09   ` 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=503a5a7b-4e94-105f-5242-5364b6d49701@arm.com \
    --to=luis.machado@arm.com \
    --cc=binutils@sourceware.org \
    --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).