From: Matthias Klose <doko@ubuntu.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] use python-config if available
Date: Thu, 20 Dec 2012 16:13:00 -0000 [thread overview]
Message-ID: <50D3391A.4000506@ubuntu.com> (raw)
In-Reply-To: <20121220155906.GB5370@adacore.com>
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
next prev parent reply other threads:[~2012-12-20 16:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-20 15:41 Matthias Klose
2012-12-20 15:43 ` Matthias Klose
2012-12-20 15:53 ` Pierre Muller
2012-12-20 15:59 ` Joel Brobecker
2012-12-20 16:13 ` Matthias Klose [this message]
2012-12-21 7:57 ` Joel Brobecker
2012-12-21 17:31 ` Doug Evans
2012-12-21 17:51 ` Joel Brobecker
2012-12-22 19:33 ` 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=50D3391A.4000506@ubuntu.com \
--to=doko@ubuntu.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/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