From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] apitrace: bump to version 7.0
Date: Mon, 24 Aug 2015 16:42:06 +0100 [thread overview]
Message-ID: <55DB3B4E.3060109@imgtec.com> (raw)
In-Reply-To: <87h9nozp9e.fsf@dell.be.48ers.dk>
Dear Peter Korsgaard,
On 08/24/2015 04:21 PM, Peter Korsgaard wrote:
>>>>>> "Vicente" == Vicente Olivert Riera <Vincent.Riera@imgtec.com> writes:
>
> > Our current apitrace version can't detect the host-python version
> > correctly, so if both host-python and host-python3 where installed, it
> > will take the last one and it will fail with an "invalid syntax" error.
> > The latest apitrace version has this problem solved and it detects the
> > host-python version correctly.
>
> > Fixes:
>
> > http://autobuild.buildroot.net/results/22a/22a73b4ba0adcc874ecc153917ae6edcfd4d37af/
>
> > Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
>
> So then perhaps we shouldn't force people to build host-python if they
> already have host-python3 built?
>
> E.G. something like:
>
> APITRACE_DEPENDENCIES = xlib_libX11 $(if $(BR2_PACKAGE_PYTHON3),host-python3,host-python)
>
> But that can be added later - Committed, thanks.
>
No, no. I think you misunderstood me, or perhaps I didn't explain myself
very well.
What the new version of apitrace does is using python2 even if you have
python3 installed. The old one was using python3 although both python2
and python3 were installed. It was just choosing the wrong python. Does
it make sense now?
Regards,
Vincent.
next prev parent reply other threads:[~2015-08-24 15:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-24 8:54 [Buildroot] [PATCH] apitrace: bump to version 7.0 Vicente Olivert Riera
2015-08-24 15:21 ` Peter Korsgaard
2015-08-24 15:42 ` Vicente Olivert Riera [this message]
2015-08-24 15:55 ` Peter Korsgaard
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=55DB3B4E.3060109@imgtec.com \
--to=vincent.riera@imgtec.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox