Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: 7.2 branch, configure problem, --with-python
Date: Thu, 29 Jul 2010 15:28:00 -0000	[thread overview]
Message-ID: <20100729152827.GZ13267@adacore.com> (raw)
In-Reply-To: <4C50B58A.5080408@vmware.com>

> Hmmm, what if you try configure --with-python=/usr?
> That will approximate what I'm doing (only with me it's a
> non-standard install location).

I just rebuilt python-2.7 with --enable-shared and installed it at
a non-standard location.  And then configured GDB as follow:

    % CFLAGS='-g' ~/act/gdb-public/configure --with-python=/t.a/brobecke/python-2.7-shared

And I still see GDB being linked against the python DSO:

    % ldd gdb/gdb
    libpython2.7.so.1.0 => /t.a/brobecke/python-2.7-shared/lib/libpython2.7.so.1.0 (0x00007f5effa5f000)

For this to work, I did need my python-config.py patch, because
the compilation command was missing a -L/path/to/python/dso, without
which the configure check for libpython2.7 would fail.

In order to understand what is going on, you will probably have to
dig into your config.log file and see what the configure script is
doing. I'm starting to think that your python install might be screwed
or non-standard?

-- 
Joel


  reply	other threads:[~2010-07-29 15:28 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-26 23:45 Michael Snyder
2010-07-27 15:30 ` Thiago Jung Bauermann
2010-07-27 17:17   ` Michael Snyder
2010-07-27 17:25     ` Jan Kratochvil
2010-07-28  0:30   ` Michael Snyder
2010-07-28 16:15     ` Tom Tromey
2010-07-28 16:56       ` Michael Snyder
2010-07-28 17:20       ` Joel Brobecker
2010-07-28 17:27         ` Michael Snyder
2010-07-28 17:37           ` Joel Brobecker
2010-07-28 17:59             ` Michael Snyder
2010-07-28 18:08               ` Joel Brobecker
2010-07-28 18:10                 ` Michael Snyder
2010-07-28 18:15                   ` Michael Snyder
2010-07-28 19:59                     ` Michael Snyder
2010-07-28 21:32                       ` Joel Brobecker
2010-07-28 18:19                   ` Joel Brobecker
2010-07-28 18:23                     ` Michael Snyder
2010-07-28 18:27                       ` Joel Brobecker
2010-07-28 19:58                         ` Michael Snyder
2010-07-28 20:02                           ` Michael Snyder
2010-07-28 20:07                             ` Michael Snyder
2010-07-28 20:21                               ` Michael Snyder
2010-07-28 21:36                                 ` Joel Brobecker
2010-07-28 22:56                                   ` Michael Snyder
2010-07-29 15:28                                     ` Joel Brobecker [this message]
2010-07-29 17:37                                       ` Michael Snyder
2010-07-29 17:52                                         ` Michael Snyder
2010-07-29 18:41                                           ` Joel Brobecker
2010-07-29 18:49                                             ` Michael Snyder
2010-07-29 19:05                                               ` Joel Brobecker
2010-07-29 19:31                                                 ` Michael Snyder
2010-07-29 21:32                                                   ` Joel Brobecker
2010-07-29 21:45                                                     ` Michael Snyder

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=20100729152827.GZ13267@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@vmware.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