From: Andreas Schwab <schwab@linux-m68k.org>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix PR gdb/19250: ptrace prototype is not detected properly in C++ mode
Date: Sat, 16 Apr 2016 06:47:00 -0000 [thread overview]
Message-ID: <m2shym2gox.fsf@linux-m68k.org> (raw)
In-Reply-To: <1460765786-12190-1-git-send-email-palves@redhat.com> (Pedro Alves's message of "Sat, 16 Apr 2016 01:16:26 +0100")
Wouldn't it be easier to split the configure check in two parts, one
running in C mode that does the detection of the argument and return
types, and a second part running in C++ mode that probes the need for
the enum?
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2016-04-16 6:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-16 0:16 Pedro Alves
2016-04-16 6:47 ` Andreas Schwab [this message]
[not found] ` <5714FD3D.5010706@redhat.com>
2016-04-18 16:48 ` [PATCH v2] " Pedro Alves
2016-04-18 14:15 ` [PATCH] " Simon Marchi
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=m2shym2gox.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=gdb-patches@sourceware.org \
--cc=palves@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