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: [patch] use python-config if available


Am 20.12.2012 16:59, schrieb Joel Brobecker:
>>> This patch does use the python-config, which comes shipped with the python
>>> interpreter, and falls back to the internal copy of python-config.py.
>>> AC_CHECK_TOOL is used to find a possible python-config for the host.
>>>
>>> Tested with 7.5 with a native and a cross build.
> 
> Can you tell us what problem you are trying to solve?

cross building in a multiarch environment, where the host libraries are
installed, and a <host>-python-config is shipped as part of the system python.
This <host>-python-config is a backport of http://bugs.python.org/issue16235
(not yet applied upstream).

> Your patch would most certainly break the build in my case, as
> I rely on some local changes made to our copy of python-config.py,
> which I cannot contribute because they break some setups different
> than ours.

so what is your recommendation? configure.ac reads:

dnl /path/to/python/executable -
dnl        Run python-config.py with this version of python to fetch the
dnl        compilation parameters.
dnl        NOTE: This needn't be the real python executable.
dnl        In a cross-compilation scenario (build != host), this could be
dnl        a shell script that provides what python-config.py provides for
dnl        --ldflags, --includes, --exec-prefix.

do I really have to provide a shell script, which shifts the first parameter,
and then calls the real python-config?

  Matthias


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