All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Oberparleiter <oberpar@linux.vnet.ibm.com>
To: subrata@linux.vnet.ibm.com
Cc: ltp-list <ltp-list@lists.sf.net>,
	ltp-coverage <ltp-coverage@lists.sourceforge.net>
Subject: Re: [LTP] LTP fails to build for Application Code Coverage
Date: Fri, 30 Oct 2009 15:25:38 +0100	[thread overview]
Message-ID: <4AEAF762.3050205@linux.vnet.ibm.com> (raw)
In-Reply-To: <1256909081.13702.14.camel@subratamodak.linux.ibm.com>

Hi Subrata,

Subrata Modak wrote:
> # make CFLAGS=\ -fprofile-arcs\ -ftest-coverage\ -Wall
[...]
> gcc   ltp-pan.o zoolib.o splitstr.o -lm  -o ltp-pan
> ltp-pan.o: In function `run_child':
> ltp-pan.c:(.text+0x6d54): undefined reference to `__gcov_fork'

we already solved this issue via ST but I'll still post the result here 
for reference: to prevent this particular error, you'll need to also 
provide the additional linker option -coverage.

As not all ltp Makefile work well when specifying CFLAGS and LDFLAGS on 
the make command line, you'll need to specify those during the configure 
step, i.e.

./configure CFLAGS="-fprofile-arcs -ftest-coverage" LDFLAGS="-coverage"
make


Regards,
   Peter


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  reply	other threads:[~2009-10-30 17:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-30 13:24 [LTP] LTP fails to build for Application Code Coverage Subrata Modak
2009-10-30 14:25 ` Peter Oberparleiter [this message]
2009-10-30 19:01   ` Garrett Cooper

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=4AEAF762.3050205@linux.vnet.ibm.com \
    --to=oberpar@linux.vnet.ibm.com \
    --cc=ltp-coverage@lists.sourceforge.net \
    --cc=ltp-list@lists.sf.net \
    --cc=subrata@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 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.