From: nick clifton <nickc@redhat.com>
To: Pierre Muller <pierre.muller@ics-cnrs.unistra.fr>,
"'Pedro Alves'" <palves@redhat.com>,
"'asmwarrior'" <asmwarrior@gmail.com>
Cc: "'GDB Development'" <gdb@sourceware.org>,
"'Binutils Development'" <binutils@sourceware.org>
Subject: Re: [RFC] BFD MinGW/Cygwin build error in bfd/peiXXgen.c
Date: Wed, 18 Dec 2013 17:52:00 -0000 [thread overview]
Message-ID: <52B1E03E.9010002@redhat.com> (raw)
In-Reply-To: <002101cefbf1$7554b9a0$5ffe2ce0$@muller@ics-cnrs.unistra.fr>
Hi Pierre,
> bfd/ChangeLog entry:
>
> 2013-12-18 Pierre Muller <muller@sourceware.org>
>
> peXXigen.c (u16_mbtouc): Avoid unused function warning by exculding if
> __CYGWIN__ or __MINGW32__ macro is defined.
> (rsrc_cmp): Fix short Windows OS version. Also use this code
> for mingw32 systems.
> [__MINGW32__]: Alias wcsncasecmp function to Windows API wcsnicmp function.
Approved - please apply.
Cheers
Nick
next prev parent reply other threads:[~2013-12-18 17:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-18 9:54 GDB MinGW build error: implicit declaration of function 'wcsncasecmp' asmwarrior
2013-12-18 9:58 ` asmwarrior
2013-12-18 10:06 ` BFD " Pedro Alves
2013-12-18 12:50 ` asmwarrior
2013-12-18 15:47 ` Eli Zaretskii
2013-12-18 13:03 ` [RFC] BFD MinGW/Cygwin build error in bfd/peiXXgen.c Pierre Muller
2013-12-18 17:52 ` nick clifton [this message]
2013-12-19 11:45 ` [RFC-v2] " Pierre Muller
2013-12-19 12:41 ` nick clifton
2013-12-19 13:02 ` Mark Kettenis
2013-12-19 13:18 ` Pierre Muller
2013-12-19 15:13 ` nick clifton
[not found] ` <52b19d01.22cbc20a.69b0.ffffb29eSMTPIN_ADDED_BROKEN@mx.google.com>
2013-12-18 13:25 ` [RFC] " asmwarrior
[not found] ` <52b19d19.0850420a.7b6a.52dcSMTPIN_ADDED_BROKEN@mx.google.com>
2013-12-18 17:56 ` Pedro Alves
2013-12-19 11:15 ` nick clifton
2013-12-18 15:35 ` GDB MinGW build error: implicit declaration of function 'wcsncasecmp' Eli Zaretskii
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=52B1E03E.9010002@redhat.com \
--to=nickc@redhat.com \
--cc=asmwarrior@gmail.com \
--cc=binutils@sourceware.org \
--cc=gdb@sourceware.org \
--cc=palves@redhat.com \
--cc=pierre.muller@ics-cnrs.unistra.fr \
/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