This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: 7.2 branch, configure problem, --with-python

From: Michael Snyder <msnyder at vmware dot com>
To: Tom Tromey <tromey at redhat dot com>
Cc: Thiago Jung Bauermann <bauerman at br dot ibm dot com>, "gdb-patches at sourceware dot org" <gdb-patches at sourceware dot org>
Date: Wed, 28 Jul 2010 09:56:08 -0700
Subject: Re: 7.2 branch, configure problem, --with-python
References: <4C4E1E0F.80309@vmware.com> <1280244591.2661.104.camel@hactar> <4C4F7A39.9030606@vmware.com> <m339v3oa55.fsf@fleche.redhat.com>

Tom Tromey wrote:

Michael> So this problem shows up because we've switched to static linking
Michael> (at least for configure).

I wonder why that changed.

Me too.

Does your Python come with dynamic libraries?

Yep.

Did 7.1 choose those instead?

Yep.

AFAIK we didn't intentionally make any change to prefer static libraries --

That's odd, because it seems like a non-trivial change was required.

> I think that would be a bad decision.

Me too.

Both 7.1 and 7.2 use "ac_fn_c_try_link", which is locally defined in configure. In configure.ac, it appears to be AC_TRY_LIBPYTHON.

References:
- 7.2 branch, configure problem, --with-python
  - From: Michael Snyder
- Re: 7.2 branch, configure problem, --with-python
  - From: Thiago Jung Bauermann
- Re: 7.2 branch, configure problem, --with-python
  - From: Michael Snyder
- Re: 7.2 branch, configure problem, --with-python
  - From: Tom Tromey

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]