public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] python-config.py --ldflags should return relocated path to libpython
Date: Thu, 05 Aug 2010 18:25:00 -0000	[thread overview]
Message-ID: <m3bp9gx6ge.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20100728172339.GL13267@adacore.com> (Joel Brobecker's message of	"Wed, 28 Jul 2010 10:23:39 -0700")

>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:

Joel> There are currently 2 issues, I think, with python-config --ldflags:
Joel> 1. When python is configured with --enable-shared:
Joel> -L<prefix>/lib is missing.  This is a problem if python was
Joel> installed in a non-standard location.
[...]


Joel> No comment either on the Python side or on the gdb-patches side.

Joel> I think it's too late for 7.2, but I would like to apply this patch
Joel> on the HEAD. Any objections? If we ever create a 7.2.1, and this patch
Joel> was shown to not cause any problem, then perhaps I'll consider it for
Joel> backporting on the 7.2 branch - if approved by the GMs.

It sounds reasonable to me.
I don't know enough about all the Python configuration and install
options to fully understand the patch, but it also seemed ok.

Tom

  reply	other threads:[~2010-08-05 18:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-08 22:25 Joel Brobecker
2010-07-08 23:04 ` Joel Brobecker
2010-07-28 17:23 ` Joel Brobecker
2010-08-05 18:25   ` Tom Tromey [this message]
2010-08-05 18:54 ` Jan Kratochvil
2010-08-11 19:08   ` Joel Brobecker
2010-08-11 19:10     ` Jan Kratochvil
2010-08-11 19:39       ` Joel Brobecker
2010-08-11 19:48         ` Jan Kratochvil
2010-08-16 14:50     ` 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=m3bp9gx6ge.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).