From: Darren Hart <dvhart@linux.intel.com>
To: Saul Wold <sgw@linux.intel.com>
Cc: poky@yoctoproject.org
Subject: Re: [PATCH 1/1] packagegroup-core-tools-profile: replace 'legacy' lttng with lttng 2.0
Date: Mon, 15 Oct 2012 16:53:30 -0700 [thread overview]
Message-ID: <507CA1FA.4060105@linux.intel.com> (raw)
In-Reply-To: <507CA199.2000509@linux.intel.com>
On 10/15/2012 04:51 PM, Saul Wold wrote:
> On 10/12/2012 12:53 PM, tom.zanussi@intel.com wrote:
>> From: Tom Zanussi <tom.zanussi@intel.com>
>>
>> packagegroup-core-tools-profile currently pulls in the 'legacy' lttng
>> packages, which are useless without legacy lttng support in the kernel.
>>
>> This makes packagegroup-core-tools-profile pull in the lttng 2.0
>> packages instead, which don't need any kernel modifications to work.
>>
>> Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
>> ---
>> .../packagegroups/packagegroup-core-tools-profile.bb | 9 +++++----
>> 1 file changed, 5 insertions(+), 4 deletions(-)
>>
>> diff --git a/meta/recipes-core/packagegroups/packagegroup-core-tools-profile.bb b/meta/recipes-core/packagegroups/packagegroup-core-tools-profile.bb
>> index 1035036..bf6e16e 100644
>> --- a/meta/recipes-core/packagegroups/packagegroup-core-tools-profile.bb
>> +++ b/meta/recipes-core/packagegroups/packagegroup-core-tools-profile.bb
>> @@ -5,7 +5,7 @@
>> SUMMARY = "Profiling tools"
>> LICENSE = "MIT"
>>
>> -PR = "r1"
>> +PR = "r2"
>>
>> inherit packagegroup
>>
>> @@ -29,8 +29,9 @@ PROFILETOOLS = "\
>> oprofileui-server \
>> powertop \
>> latencytop \
>> - lttng-control \
>> - lttng-viewer"
>> + lttng-tools \
>> + lttng-modules \
>> + babeltrace"
>>
> Not sure this will work since babeltrace is not buildable for mips machines.
I guess that means we just need a BABELTRACE and BABELTRACE_mips
definition? Or perhaps a set for LTTNG similar to those below for LTTNGUST ?
--
Darren
>
> Sau!
>
>> # systemtap needs elfutils which is not fully buildable on uclibc
>> # hence we exclude it from uclibc based builds
>> @@ -44,7 +45,7 @@ SYSTEMTAP_mips = ""
>> # which means we can not use syscall() to call it. So we ignore
>> # it for x86_64/uclibc
>>
>> -LTTNGUST = "lttng-ust"
>> +LTTNGUST = "lttng2-ust"
>> LTTNGUST_libc-uclibc = ""
>> LTTNGUST_mips = ""
>>
>>
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel
next prev parent reply other threads:[~2012-10-15 23:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-12 19:52 [PATCH 0/1] lttng-2.0 fixes tom.zanussi
2012-10-12 19:53 ` [PATCH 0/1] replace lttng with lttng-2.0 in core-tools-profile tom.zanussi
2012-10-12 19:52 ` [PATCH 1/1] lttng-modules: update SRCREV and remove is_compat_task patch tom.zanussi
2012-10-12 20:12 ` Bruce Ashfield
2012-10-12 19:53 ` [PATCH 1/1] packagegroup-core-tools-profile: replace 'legacy' lttng with lttng 2.0 tom.zanussi
2012-10-12 20:11 ` Bruce Ashfield
2012-10-12 20:11 ` Bruce Ashfield
2012-10-15 23:51 ` Saul Wold
2012-10-15 23:53 ` Darren Hart [this message]
2012-10-16 2:33 ` Tom Zanussi
2012-10-12 20:13 ` [PATCH 0/1] lttng-2.0 fixes Bruce Ashfield
-- strict thread matches above, loose matches on Subject: below --
2012-10-16 4:59 [PATCH 0/1] replace lttng with lttng-2.0 in core-tools-profile, v2 tom.zanussi
2012-10-16 4:59 ` [PATCH 1/1] packagegroup-core-tools-profile: replace 'legacy' lttng with lttng 2.0 tom.zanussi
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=507CA1FA.4060105@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=poky@yoctoproject.org \
--cc=sgw@linux.intel.com \
/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.