From: Romain Naour <romain.naour@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build failures, help requested!
Date: Thu, 17 Apr 2014 22:15:05 +0200 [thread overview]
Message-ID: <53503649.1020803@openwide.fr> (raw)
In-Reply-To: <20140417213939.35afc5ff@skate>
Hi,
>
>> arm | lttng-libust-2.4.0 | NOK | http://autobuild.buildroot.net/results/a88e2af7cd1ece12213da52c8dd687f8d6813299/
>
> Python problem, to be investigated by Samuel.
>
This problem is fixed in the 2.4.1 release:
https://bugs.lttng.org/projects/lttng-ust/repository/revisions/dcb6ba251f8c612133e4a3e064690d915f54a146
python (optional) dependency is missing in the package since it's needed for lttng-gen-tp and ptime tools.
Samuel, what do you think about updating lttng to 2.4.1 version ?
Best regards,
Romain Naour
next prev parent reply other threads:[~2014-04-17 20:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-17 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-04-16 Thomas Petazzoni
2014-04-17 7:46 ` Luca Ceresoli
2014-04-17 19:39 ` [Buildroot] Analysis of build failures, help requested! Thomas Petazzoni
2014-04-17 19:51 ` Max Filippov
2014-04-17 20:15 ` Romain Naour [this message]
2014-04-17 21:01 ` Luca Ceresoli
2014-04-17 21:58 ` Thomas Petazzoni
2014-04-18 7:39 ` Fatih Aşıcı
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=53503649.1020803@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