From: JonY <jon_y@users.sourceforge.net>
To: Gcc Patch List <gcc-patches@gcc.gnu.org>
Cc: Kai Tietz <ktietz70@googlemail.com>
Subject: Re: [Patch] Remove _GLIBCXX_HAVE_BROKEN_VSWPRINTF from mingw32-w64/os_defines.h
Date: Mon, 29 Oct 2012 13:06:00 -0000 [thread overview]
Message-ID: <508E7F1A.5070206@users.sourceforge.net> (raw)
In-Reply-To: <508DB835.1070001@users.sourceforge.net>
[-- Attachment #1: Type: text/plain, Size: 1139 bytes --]
Fix the mail subject line.
On 10/29/2012 06:56, JonY wrote:
> Hi,
>
> Workaround now exists for trunk mingw-w64 headers.
> Kai approved over IRC, so anybody with commit rights please push.
>
> ChangeLog
> 2012-10-29 Jonathan Yong <jon_y@users.sourceforge.net>
>
> * config/os/mingw32-w64/os_defines.h: Remove _GLIBCXX_HAVE_BROKEN_VSWPRINTF
> as no longer required.
>
>
>
> Index: libstdc++-v3/config/os/mingw32-w64/os_defines.h
> ===================================================================
> --- libstdc++-v3/config/os/mingw32-w64/os_defines.h (revision 192802)
> +++ libstdc++-v3/config/os/mingw32-w64/os_defines.h (working copy)
> @@ -63,8 +63,9 @@
> // See libstdc++/20806.
> #define _GLIBCXX_HAVE_DOS_BASED_FILESYSTEM 1
>
> -// See libstdc++/37522.
> -#define _GLIBCXX_HAVE_BROKEN_VSWPRINTF 1
> +// See libstdc++/37522. mingw-w64 stdio redirect for C++
> +// #define _GLIBCXX_HAVE_BROKEN_VSWPRINTF 1
> +// Workaround added for mingw-w64 trunk headers r5437
>
> // See libstdc++/43738
> // On native windows targets there is no ioctl function. And the existing
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 196 bytes --]
next prev parent reply other threads:[~2012-10-29 13:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-29 0:08 [Patch] Remove _GLIBCXX_HAVE_BROKEN_VSWPRINTF from JonY
2012-10-29 13:06 ` JonY [this message]
2012-10-30 10:34 ` [Patch] Remove _GLIBCXX_HAVE_BROKEN_VSWPRINTF from mingw32-w64/os_defines.h JonY
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=508E7F1A.5070206@users.sourceforge.net \
--to=jon_y@users.sourceforge.net \
--cc=gcc-patches@gcc.gnu.org \
--cc=ktietz70@googlemail.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).