From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <palves@redhat.com>
Cc: jan.kratochvil@redhat.com, brobecker@adacore.com,
gdb@sourceware.org, siddhesh@redhat.com
Subject: Re: Old OSes compatibility [Re: 64-bit (>4GB) inferior data types rules; TYPE_LENGTH: unsigned -> ULONGEST]
Date: Mon, 01 Oct 2012 19:14:00 -0000 [thread overview]
Message-ID: <837graattd.fsf@gnu.org> (raw)
In-Reply-To: <5069DA6F.6070806@redhat.com>
> Date: Mon, 01 Oct 2012 19:01:19 +0100
> From: Pedro Alves <palves@redhat.com>
> CC: jan.kratochvil@redhat.com, brobecker@adacore.com, gdb@sourceware.org,
> siddhesh@redhat.com
>
> In the old mingw sources copy I have here (2009), I see under
> mingwex/stdio/ a printf.c file, which provides the __mingw_printf replacement.
> The format conversion engine is in pformat.c, and it does implement '%z'
> (look for "case 'z':").
>
> See <http://sourceforge.net/project/shownotes.php?release_id=24832>
> for how to enable the replacements. E.g., #define _GNU_SOURCE
> or __USE_MINGW_ANSI_STDIO to 1 should be enough (it defines printf to
> __mingw_printf).
In that case, perhaps GDB should use __USE_MINGW_ANSI_STDIO by default
when building for MinGW.
> I tried looking for the current sources, but the mingw.org frontpage has a news
> item mentioning that the sources have moved to git, without giving a pointer to
> where the repository is... Then, after wasting some minutes trying to find
> a pointer (and failing; in the end google found it)
> I found that http://sourceforge.net/projects/mingw/develop points
> at "git clone git://mingw.git.sourceforge.net/gitroot/mingw/mingw",
> but cloning that yields an empty repo. WTH? Is the project actively
> trying to hide itself in some dark internet corner?
I have quite recent sources here, and the feature is there. Thanks.
next prev parent reply other threads:[~2012-10-01 19:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-28 17:32 64-bit (>4GB) inferior data types rules; TYPE_LENGTH: unsigned -> ULONGEST Jan Kratochvil
2012-09-28 20:23 ` Sergio Durigan Junior
2012-09-29 6:08 ` Jan Kratochvil
2012-09-29 16:58 ` Jan Kratochvil
2012-09-30 16:56 ` Joel Brobecker
2012-10-01 16:48 ` Old OSes compatibility [Re: 64-bit (>4GB) inferior data types rules; TYPE_LENGTH: unsigned -> ULONGEST] Jan Kratochvil
2012-10-01 17:18 ` Pedro Alves
2012-10-01 17:38 ` Eli Zaretskii
2012-10-01 18:01 ` Pedro Alves
2012-10-01 19:14 ` Eli Zaretskii [this message]
2012-10-01 17:32 ` Eli Zaretskii
2012-10-01 17:55 ` Jan Kratochvil
2012-10-01 17:57 ` Joel Brobecker
2012-10-01 18:08 ` Jan Kratochvil
2012-10-01 18:13 ` Joel Brobecker
2012-10-01 18:29 ` Jan Kratochvil
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=837graattd.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=palves@redhat.com \
--cc=siddhesh@redhat.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).