From: srimanta.panda@gmail.com (Srimanta Panda)
Subject: [ltt-dev] LTTng Build issue
Date: Tue, 14 Sep 2010 08:35:26 -0000 [thread overview]
Message-ID: <AANLkTik_BuUt6EtqKyMivMv1SjOiweGM_5uWi0LPy57H@mail.gmail.com> (raw)
Message-ID: <20100914083526.fmf-iGlOlNvt2DrDP7VeuKPRJImmqkqbPEv_9KsRUWI@z> (raw)
Hi,
I am quite new to this LLTng.
I am trying to build the Kernel 2.6.34 with the ltt patch .221 for ARM
platform. Its gives me link error related to the trace-clock
functionalities.
I tried to figured out and found that it is not able to compile the
trace-clock.c because of some flag HAVE_TRACE_CLOCK_GENERIC, which is
present in the KConfig of the init folder.
I tried to enable the flag in the "kernel.spec", but is not able to set it
because it is inside of menuconfig for CGROUPS. If I enable CGROUPS, it
tells me to disable some other flags which I have no idea it is correct to
do so.
I saw the previous patches for the kernel 2.6.33 and found that the
HAVE_TRACE_CLOCK and HAVE_TRACE_CLOCK_GENERIC is added in different
locations. It was not inside CGROUP menuconfig.
I wondering if the two flags have been added in the wrong place in the new
patch .221??
Can you please help me out if I am doing any thing wrong to set
the trace-clock?
--
Cheers,
Srimanta
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.casi.polymtl.ca/pipermail/lttng-dev/attachments/20100914/185b5256/attachment-0001.htm>
next reply other threads:[~2010-09-14 8:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-14 8:35 Srimanta Panda [this message]
2010-09-14 8:35 ` Srimanta Panda
2010-09-14 8:35 ` Srimanta Panda
2010-09-14 13:39 srimanta panda
2010-09-14 13:39 ` srimanta panda
2010-09-14 13:39 ` srimanta panda
2010-09-14 15:52 ` Mathieu Desnoyers
2010-09-14 16:04 ` Mathieu Desnoyers
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=AANLkTik_BuUt6EtqKyMivMv1SjOiweGM_5uWi0LPy57H@mail.gmail.com \
--to=srimanta.panda@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox