From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org, ktietz70@googlemail.com
Subject: Re: [RFA/gdb-7.2] Enable leading-mingw64-underscores by default.
Date: Thu, 08 Jul 2010 16:50:00 -0000 [thread overview]
Message-ID: <83k4p57wdc.fsf@gnu.org> (raw)
In-Reply-To: <20100708154904.GN2595@adacore.com>
> Date: Thu, 8 Jul 2010 08:49:04 -0700
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: gdb-patches@sourceware.org, ktietz70@googlemail.com
>
> > If the former, I think it is a very bad idea to have the ABI fixed at
> > build time, because most users of MinGW do not build their own GDB.
> > At the time when 2 incompatible ABIs coexist, it is very important to
> > have GDB that could adapt to either.
>
> The problem is that I do not know whether we can make it work or not.
Well, we should at least have the symptoms of the wrong ABI spelled
out in PROBLEMS.
prev parent reply other threads:[~2010-07-08 16:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-07 19:21 Joel Brobecker
2010-07-08 6:20 ` Eli Zaretskii
2010-07-08 15:49 ` Joel Brobecker
2010-07-08 16:50 ` Eli Zaretskii [this message]
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=83k4p57wdc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.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).