From: Peter Oberparleiter <oberpar@linux.vnet.ibm.com>
To: Rishikesh K Rajak <risrajak@linux.vnet.ibm.com>
Cc: ltp-list@lists.sourceforge.net,
Pramendra Singh <Pramendra.Singh@lntinfotech.com>
Subject: Re: [LTP] not able to generate HTML output
Date: Thu, 18 Feb 2010 20:42:19 +0100 [thread overview]
Message-ID: <4B7D981B.1070005@linux.vnet.ibm.com> (raw)
In-Reply-To: <20100218104715.GB21750@rishikesh.in.ibm.com>
If you're cross-compiling your kernel and want to run lcov on the build
machine, you need to specify the full path to the cross-compiler gcov
tool, otherwise lcov will attempt to use the gcov tool of the locally
installed gcc package.
Example:
lcov -c -d /path/to/files --gcov-tool /path/to/ppc_85xx-gcov -o x.info
Also note that lcov can do the copying of .gcda files for you if a perl
interpreter and the lcov file is available. On the test machine, run:
lcov -c --to-package package
Copy the package file to the build machine. On the build machine, run:
lcov -c --from-package package --gcov-tool ...
Regards,
Peter Oberparleiter
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2010-02-18 19:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-18 7:00 [LTP] not able to generate HTML output Pramendra Singh
2010-02-18 10:14 ` Rishikesh K Rajak
[not found] ` <EB1A7C66AD0C92419BFFC785A947865A09EAE448A4@BLRINMSMBX01.bglrodc.lntinfotech.com>
2010-02-18 10:47 ` Rishikesh K Rajak
2010-02-18 19:42 ` Peter Oberparleiter [this message]
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=4B7D981B.1070005@linux.vnet.ibm.com \
--to=oberpar@linux.vnet.ibm.com \
--cc=Pramendra.Singh@lntinfotech.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=risrajak@linux.vnet.ibm.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