This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: Using Py_SetPythonHome
- From: Joel Brobecker <brobecker at adacore dot com>
- To: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- Cc: Doug Evans <dje at google dot com>, Meador Inge <meadori at codesourcery dot com>, gdb at sourceware dot org
- Date: Tue, 2 Oct 2012 06:08:54 -0700
- Subject: Re: Using Py_SetPythonHome
- References: <50511945.2070400@codesourcery.com> <20120917170657.GB5716@adacore.com> <20120917174611.GA27891@host2.jankratochvil.net> <CADPb22R4cTRqHyRi6asd6muJooPFPaCaRi2DDuqEtA+ew9jrRQ@mail.gmail.com> <20120919080410.GA12296@host2.jankratochvil.net> <20120921153645.GD5439@adacore.com> <20120921154345.GA30615@host2.jankratochvil.net> <20120921155758.GE5439@adacore.com> <20120921172735.GA4341@host2.jankratochvil.net>
> I have discovered now that default build of GCC really uses something like
> relocate_gdb_directory for its own components (like cc1), it does not use
> constant compiled-in path like normal applications do. This justifies
> relocate_gdb_directory for the default build of GDB, it was not clear to me.
> This also means GCC is violating standard system packaging practices.
I am starting to see where you are coming from. GCC has had this feature
longer than GDB, IIRC. And to me, this is not violating "standard system
packagainng practices" (please point me to a document that would claim
to explain what the standard practices are), but providing a very
important feature, which, if not standard, definitely should be (IMO).
If I have built a tool somewhere with a given prefix, and then I want
to install a copy somewhere else, it would be a real pain in the neck
to have to rebuild it.
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?
--
Joel