From: Pedro Alves <palves@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
gdb@sourceware.org,
Siddhesh Poyarekar <siddhesh@redhat.com>,
Eli Zaretskii <eliz@gnu.org>
Subject: Re: Old OSes compatibility [Re: 64-bit (>4GB) inferior data types rules; TYPE_LENGTH: unsigned -> ULONGEST]
Date: Mon, 01 Oct 2012 17:18:00 -0000 [thread overview]
Message-ID: <5069D06D.5070101@redhat.com> (raw)
In-Reply-To: <20121001164833.GA20592@host2.jankratochvil.net>
On 10/01/2012 05:48 PM, Jan Kratochvil wrote:
> Therefore I believe "%z" is OK, it would be nice to check it with several
> major non-GNU systems whether gnulib vasprintf should be already included.
Older mingw versions would be a host I recall whose libc didn't
use to support %z until a couple years ago. I believe Eli (like many, due to
some technical limitations of gcc 4.x) for example stills uses a mingw with a
3.x gcc. Not sure whether people are combining newer mingw runtime releases with
the 3.x based compilers.
--
Pedro Alves
next prev parent reply other threads:[~2012-10-01 17:18 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 [this message]
2012-10-01 17:38 ` Eli Zaretskii
2012-10-01 18:01 ` Pedro Alves
2012-10-01 19:14 ` Eli Zaretskii
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=5069D06D.5070101@redhat.com \
--to=palves@redhat.com \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@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).