Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Kevin Pouget <kevin.pouget@gmail.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sourceware.org
Subject: Re: Fwd: GDB/Python conflicts between HEAD and Fedora
Date: Thu, 25 Oct 2012 07:41:00 -0000	[thread overview]
Message-ID: <CAPftXUJ0Rk5Zxs5daD7JmKZBgHv72AyW1VjO=xPs-POWD0RxrQ@mail.gmail.com> (raw)
In-Reply-To: <20121024151731.GN3571@adacore.com>

On Wed, Oct 24, 2012 at 5:17 PM, Joel Brobecker <brobecker@adacore.com> wrote:
>> > warning: Could not load the Python gdb module from `/usr/share/gdb/python'.
>> >
>> > warning: Limited Python support is available from the _gdb module.
>
> This is the important clue.  You need to install the GDB you built
> in order for it to work properly. This was a recent change to the way
> the gdb module is constructed, to make it more pythonic.
>
> I am guessing that you configured GDB with the default --prefix,
> and so it's finding the system ones from an older version of GDB.
> If you're not going to install it in a system area, I'd configure
> with a different prefix.

Hello,

thanks for your answer, `make install` did solve the problem :)

> I am guessing that you configured GDB with the default --prefix,
> and so it's finding the system ones from an older version of GDB.

just for the record, I think that you're not right on this point:
> cd $BUILD_DIR
> $SRC_DIR/configure --prefix=$INST_DIR
> make
> gdb/gdb # from $BUILD_DIR, this don't work yet
> make install
> gdb/gdb # from $BUILD_DIR, this work now
> $INST_DIR/bin/gdb # obviously works correctly


Thanks,

Kevin


      reply	other threads:[~2012-10-25  7:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAPftXUKL9Qst0057rU9SVwiUp=otsVO_Y3h1KGNP+NVBYGVJ0w@mail.gmail.com>
2012-10-24 15:05 ` Kevin Pouget
2012-10-24 15:17   ` Joel Brobecker
2012-10-25  7:41     ` Kevin Pouget [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='CAPftXUJ0Rk5Zxs5daD7JmKZBgHv72AyW1VjO=xPs-POWD0RxrQ@mail.gmail.com' \
    --to=kevin.pouget@gmail.com \
    --cc=brobecker@adacore.com \
    --cc=gdb@sourceware.org \
    /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