From: Romain Naour <romain.naour@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2014-04-18
Date: Sat, 19 Apr 2014 12:45:36 +0200 [thread overview]
Message-ID: <535253D0.1060207@openwide.fr> (raw)
In-Reply-To: <20140419123252.6147c733@skate>
Hi Thomas,
Le 19/04/2014 12:32, Thomas Petazzoni a ?crit :
> Dear Romain Naour,
>
> On Sat, 19 Apr 2014 10:43:36 +0200, Romain Naour wrote:
>
>>> checking host system alignment requirements... checking for a Python interpreter with version >= 2.7... none
>>> configure: error: no suitable Python interpreter found
>>> make: *** [/home/test/test/1/output/build/lttng-libust-2.4.0/.stamp_configured] Error 1
>>>
>>> I think Romain Naour said the new version of lttng-libust was fixing
>>> this. Romain, could you send a patch to bump lttng-libust?
>>
>> Yes, but I think it would be better to keep all lttng tools in sync.
>> lttng-tools 2.4.1
>> lttng-modules 2.4.1
>> lttng-ust 2.4.1
>> and bump liburcu to 0.8.4 while we are at it.
>
> Sure. I'm waiting for your patches :-)
>
> Thomas
>
They are already in the patchwork :)
http://patchwork.ozlabs.org/patch/340473/
http://patchwork.ozlabs.org/patch/340477/
http://patchwork.ozlabs.org/patch/340474/
http://patchwork.ozlabs.org/patch/340475/
http://patchwork.ozlabs.org/patch/340476/
Romain
next prev parent reply other threads:[~2014-04-19 10:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-19 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-04-18 Thomas Petazzoni
2014-04-19 7:08 ` [Buildroot] Analysis of build " Thomas Petazzoni
2014-04-19 8:43 ` Romain Naour
2014-04-19 10:32 ` Thomas Petazzoni
2014-04-19 10:45 ` Romain Naour [this message]
2014-04-20 3:51 ` Baruch Siach
2014-04-20 5:23 ` Baruch Siach
2014-04-20 8:15 ` Thomas Petazzoni
2014-04-26 19:29 ` Bernd Kuhls
2014-04-26 19:52 ` Bernd Kuhls
2014-04-26 20:27 ` Frank Bergmann
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=535253D0.1060207@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox