Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Khoo Yit Phang <khooyp@cs.umd.edu>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Khoo Yit Phang <khooyp@cs.umd.edu>,
	Andreas Schwab <schwab@linux-m68k.org>,
	Hui Zhu <teawater@gmail.com>,
	gdb-patches@sourceware.org, David Malcolm <dmalcolm@redhat.com>
Subject: Re: [patch] Re: Disable -lmcheck when Python has threads (Re: [BUG] gdb crash when "python import gtk")
Date: Thu, 06 Sep 2012 19:31:00 -0000	[thread overview]
Message-ID: <D4729972-75D5-4CA7-8350-6EAFCF573A1E@cs.umd.edu> (raw)
In-Reply-To: <20120902153634.GA4703@host2.jankratochvil.net>

Hi,

On Sep 2, 2012, at 11:36 AM, Jan Kratochvil wrote:

> On Fri, 31 Aug 2012 20:40:49 +0200, Khoo Yit Phang wrote:
>> On Aug 31, 2012, at 1:56 PM, Jan Kratochvil wrote:
>>> But '-a' and '-o' are already used in configure.ac.  '(' and ')' are not but
>>> that should be the same category, also POSIX documents '(' and ')'.
>> 
>> I've posted patches for both styles, I'll check in whichever is preferable.
> 
> While Andreas is formally right I do not think it matters with current
> gdb/configure.ac, please check in the more readable -a/-o/(/) variant.
> 
> If one finds an incompatible build platform one needs to fix all the other
> cases already anyway.

I've checked in the -a/-o variant of this patch.

Thanks!

Yit
September 6, 2012


  reply	other threads:[~2012-09-06 19:31 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CANFwon0wEXd+40H85veHyRTg+itYyL2jjgsCMYByxk5K0MTLHA@mail.gmail.com>
     [not found] ` <20120719073959.GA10044@host2.jankratochvil.net>
     [not found]   ` <A681786A-58A1-41E6-8410-8EBD8330E6BE@cs.umd.edu>
2012-08-30 16:43     ` Jan Kratochvil
2012-08-30 18:05       ` Khoo Yit Phang
2012-08-30 18:21         ` Jan Kratochvil
2012-08-30 18:58           ` Khoo Yit Phang
2012-08-30 19:05             ` Jan Kratochvil
2012-08-30 19:28               ` Khoo Yit Phang
2012-08-31  1:32                 ` Khoo Yit Phang
2012-08-31  8:14                   ` Jan Kratochvil
2012-08-31 15:30                     ` Khoo Yit Phang
2012-08-31 15:41                       ` Andreas Schwab
2012-08-31 16:08                         ` Khoo Yit Phang
2012-08-31 17:02                           ` Andreas Schwab
2012-08-31 18:03                             ` Khoo Yit Phang
2012-08-31 18:23                           ` Jan Kratochvil
2012-08-31 18:41                             ` Khoo Yit Phang
2012-09-02 15:37                               ` Jan Kratochvil
2012-09-06 19:31                                 ` Khoo Yit Phang [this message]
2012-08-30 18:22         ` Sergio Durigan Junior
2012-08-30 18:45           ` Khoo Yit Phang

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=D4729972-75D5-4CA7-8350-6EAFCF573A1E@cs.umd.edu \
    --to=khooyp@cs.umd.edu \
    --cc=dmalcolm@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=schwab@linux-m68k.org \
    --cc=teawater@gmail.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