public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: Thiago Jung Bauermann <bauerman@br.ibm.com>,
	       "gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: 7.2 branch, configure problem, --with-python
Date: Wed, 28 Jul 2010 16:15:00 -0000	[thread overview]
Message-ID: <m339v3oa55.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4C4F7A39.9030606@vmware.com> (Michael Snyder's message of "Tue,	27 Jul 2010 17:30:49 -0700")

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

I wonder why that changed.  Does your Python come with dynamic
libraries?  Did 7.1 choose those instead?  AFAIK we didn't intentionally
make any change to prefer static libraries -- I think that would be a
bad decision.

Michael> Isn't this problem showing up for anyone else?  It seems to me that
Michael> it will bite anybody who's using a binary release of these versions.

Jan reports that 7.2 builds ok on RHEL 5 against the system python.
At least those of us at Red Hat haven't hit this problem since we use
the system python, not the one you are using.

Tom

  reply	other threads:[~2010-07-28 16:15 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 [this message]
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
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=m339v3oa55.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=bauerman@br.ibm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).