Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: David Edelsohn <dje.gcc@gmail.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Andreas Schwab <schwab@suse.de>,
	"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: GDB Python extension on AIX
Date: Thu, 18 Aug 2016 13:00:00 -0000	[thread overview]
Message-ID: <CAGWvnykaNfekPhYo+YNtFFq7WE5inbrF376oma4+q86QJMqt6A@mail.gmail.com> (raw)
In-Reply-To: <20160818072133.GB3037@adacore.com>

On Thu, Aug 18, 2016 at 3:21 AM, Joel Brobecker <brobecker@adacore.com> wrote:
>> I think the ball is in GDB's court.
>>
>> If GDB is going to intervene in these macros for some systems and
>> configuratino, I request a method to disable this for AIX.
>
> Seems like a reasonable request to me, at least as a stop-gap measure.
> If there is a way to do things more correctly, perhaps we could look at
> that as a second step.
>
> Note that it is strange that I don't see the error you are seeing.
> But perhaps it has to do with the fact that we use a version of
> Python which we built and installed at a non-standard location?

Hi, Joel

Thanks for looking into this and for considering some sort of work-around.

I'm not sure what a "standard" location is on AIX.  I was using the
Bull Freeware installation of Python in /opt/freeware.

Was the Python installation found and recognized on your AIX system?
Until some of my more recent changes, GDB configure did not consider
the installation correct to try to build the GDB feature.

AIX, unfortunately, is very delicate and picky about header inclusion
order and feature macros.

Thanks, David


  reply	other threads:[~2016-08-18 13:00 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 [this message]
2016-08-19  5:49         ` Joel Brobecker
2016-08-19 15:36           ` David Edelsohn
2016-08-31 23:41             ` Joel Brobecker

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=CAGWvnykaNfekPhYo+YNtFFq7WE5inbrF376oma4+q86QJMqt6A@mail.gmail.com \
    --to=dje.gcc@gmail.com \
    --cc=brobecker@adacore.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