public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Doug Evans <dje@google.com>,
	Meador Inge <meadori@codesourcery.com>,
	       gdb@sourceware.org
Subject: Re: Using Py_SetPythonHome
Date: Wed, 03 Oct 2012 15:14:00 -0000	[thread overview]
Message-ID: <20121003151415.GA23095@host2.jankratochvil.net> (raw)
In-Reply-To: <20121003151244.GA22734@host2.jankratochvil.net>

On Wed, 03 Oct 2012 17:12:44 +0200, Jan Kratochvil wrote:
> On Tue, 02 Oct 2012 15:08:54 +0200, Joel Brobecker wrote:
> > Going back to the actual subject of this discussion, would it cause
> > a problem to call Py_SetPythonHome in your situation where everything
> > is static and installed at the default location?
> 
> Yes, it is a problem because 99.9% of other Python-using packages behave
> differently.

That is I do not mind anymore as it just fits the current GDB relocation
feature already in place.  I am just against this GDB relocation feature.
But that is also off-topic here, this mail thread discusses only the
Py_SetPythonHome part.


Thanks,
Jan

  reply	other threads:[~2012-10-03 15:14 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-12 23:23 Meador Inge
2012-09-17 17:07 ` Joel Brobecker
2012-09-17 17:46   ` Jan Kratochvil
2012-09-18 19:38     ` Doug Evans
2012-09-19  8:04       ` Jan Kratochvil
2012-09-21 15:37         ` Joel Brobecker
2012-09-21 15:44           ` Jan Kratochvil
2012-09-21 15:58             ` Joel Brobecker
2012-09-21 17:28               ` Jan Kratochvil
2012-10-02 13:09                 ` Joel Brobecker
2012-10-03 15:13                   ` Jan Kratochvil
2012-10-03 15:14                     ` Jan Kratochvil [this message]
2012-10-03 15:39                     ` Joel Brobecker
2012-10-03 17:44                       ` Eli Zaretskii
2012-10-03 17:54                       ` Jan Kratochvil
2012-10-03 17:57                         ` Paul_Koning
2012-10-03 18:35                           ` Eli Zaretskii
2012-10-03 18:43                             ` Jan Kratochvil
2012-10-03 18:52                               ` Eli Zaretskii
2012-10-03 19:03                                 ` Jan Kratochvil
2012-10-03 19:10                                   ` Eli Zaretskii
2012-10-03 19:54                               ` Paul_Koning
2012-10-03 20:04                                 ` Jan Kratochvil
2012-10-03 20:11                               ` Alfred M. Szmidt
2012-10-03 18:40                         ` Eli Zaretskii
2012-10-03 19:26                         ` Terekhov, Mikhail
2012-10-04  7:33                         ` John Gilmore
2012-10-11  8:42                           ` Jan Kratochvil
2012-10-11 14:54                             ` Doug Evans
2012-09-21 15:55   ` Meador Inge
2012-09-21 16:01     ` Jan Kratochvil
2012-09-21 16:36       ` Doug Evans

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=20121003151415.GA23095@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=dje@google.com \
    --cc=gdb@sourceware.org \
    --cc=meadori@codesourcery.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).