Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: David Edelsohn <dje.gcc@gmail.com>
Cc: Andreas Schwab <schwab@suse.de>,
	"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: GDB Python extension on AIX
Date: Wed, 31 Aug 2016 23:41:00 -0000	[thread overview]
Message-ID: <20160831234105.GG4538@adacore.com> (raw)
In-Reply-To: <CAGWvny=hQZD+dEo3HCisM7m7A5ajoa1ne_pGEXQ424YU0cO1sQ@mail.gmail.com>

> Would the appended patch be an acceptable approach?

Sorry for the late reply (holidays and traveling). That would
seem reasonable to me, but patches in the python/ subdir have
traditionally been Tom and Doug's territory.

My suggestion is to modify your comment about AIX to include
the issue you've been describing in this email chain, to make it
easier to remember why the workaround should not be applied on
AIX, and then resubmit on gdb-patches, with Doug Evans in Cc:.

> gdb/
> * python/python-internal.h: Don't redefine _POSIX_C_SOURCE and
> _XOPEN_SOURCE on AIX.
> 
> diff --git a/gdb/python/python-internal.h b/gdb/python/python-internal.h
> index 8545c7b..6378ccc 100644
> --- a/gdb/python/python-internal.h
> +++ b/gdb/python/python-internal.h
> @@ -72,8 +72,12 @@
>     To work around this, undef _POSIX_C_SOURCE before we include Python.h.
> 
>     Same problem with _XOPEN_SOURCE.  */
> +
> +/* A kludge to avoid overriding on AIX.  */
> +#ifndef _AIX
>  #undef _POSIX_C_SOURCE
>  #undef _XOPEN_SOURCE
> +#endif
> 
>  /* On sparc-solaris, /usr/include/sys/feature_tests.h defines
>     _FILE_OFFSET_BITS, which pyconfig.h also defines.  Same work

-- 
Joel


      reply	other threads:[~2016-08-31 23:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-11  1:56 David Edelsohn
     [not found] ` <mvmk2fnsr0a.fsf@hawking.suse.de>
2016-08-11 13:56   ` David Edelsohn
2016-08-18  7:21     ` Joel Brobecker
2016-08-18 13:00       ` David Edelsohn
2016-08-19  5:49         ` Joel Brobecker
2016-08-19 15:36           ` David Edelsohn
2016-08-31 23:41             ` Joel Brobecker [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=20160831234105.GG4538@adacore.com \
    --to=brobecker@adacore.com \
    --cc=dje.gcc@gmail.com \
    --cc=gdb@sourceware.org \
    --cc=schwab@suse.de \
    /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