From: Romain Naour <romain.naour@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/1] trace-cmd: use pkg-config instead of python-config
Date: Mon, 28 Oct 2013 00:16:45 +0100 [thread overview]
Message-ID: <526D9EDD.3070104@openwide.fr> (raw)
In-Reply-To: <871u37uezx.fsf@dell.be.48ers.dk>
Le 27/10/2013 12:31, Peter Korsgaard a ?crit :
>>>>>> "Romain" == Romain Naour <romain.naour@openwide.fr> writes:
> > trace-cmd use python-config to find out which headers
> > and libraries should be used to link against the Python libraries.
> > By default, python-config returns paths that are inappropriate for
> > cross-compilation.
>
> > This patch replaces python-config with pkg-config as a workaround.
>
> > Add PYTHON_VERS to build trace-cmd with python2 or python3
>
> > Fixes:
> > http://autobuild.buildroot.net/results/980/980875810528ac1dee34b8c268d9b3c40b2e35ec/
>
> Committed, thanks. Did you send the patch upstream? If not, please try
> to do so?
>
Hi,
Not yet, but it would be better to fix python-config directly instead of
replacing it.
The RFC about the new pkg-python infrastructure is interesting.
If I understand correctly it may also fixes this issue without replacing
python-config.
I will still send this patch upstream.
We have a new issue with trace-cmd if ptrace support is not available...
A new patch is coming for review :)
Best regards,
Romain
next prev parent reply other threads:[~2013-10-27 23:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-20 21:36 [Buildroot] [PATCH v3 1/1] trace-cmd: use pkg-config instead of python-config Romain Naour
2013-10-27 11:31 ` Peter Korsgaard
2013-10-27 23:16 ` Romain Naour [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-10-20 21:30 Romain Naour
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=526D9EDD.3070104@openwide.fr \
--to=romain.naour@openwide.fr \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.