From: sheetalchawla2608@gmail.com (Sheetal Chawla)
Subject: [lttng-dev] Difficulty in viewing kerne traces
Date: Fri, 25 Sep 2015 15:08:36 +0530 [thread overview]
Message-ID: <CAAYE7VVeRWOe7Sn2gGBKgNpcD_3ng++Ookfn75LXGnyxJdWeEQ@mail.gmail.com> (raw)
SIr/Madam,
We are working on a project that involves kernel traces. So we are using
LTTng as a tool. We are not able to view the kernel traces using babeltrace
as we are getting the following errors while doing ./configure for
babeltrace
*checking for uuid_generate in -luuid... nochecking for uuid_create in
-lc... noconfigure: error: Cannot find libuuid uuid_generate nor libc
uuid_create. Use LDFLAGS=-Ldir to specify their location.*
Kindly help us with the difficulty.
Your reply will be of great value to us.
Thanking You
Regards,
Sheetal Chawla
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lttng.org/pipermail/lttng-dev/attachments/20150925/188d4e3d/attachment.html>
next reply other threads:[~2015-09-25 9:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-25 9:38 Sheetal Chawla [this message]
2015-09-25 19:55 ` Jonathan Rajotte Julien
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=CAAYE7VVeRWOe7Sn2gGBKgNpcD_3ng++Ookfn75LXGnyxJdWeEQ@mail.gmail.com \
--to=sheetalchawla2608@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