Bug 171074 - Unable to get .gcno files when compile with -ftest-coverage and -fprofile-arcs options
Summary: Unable to get .gcno files when compile with -ftest-coverage and -fprofile-arc...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: ccache
Version: 4
Hardware: All
OS: Linux
medium
low
Target Milestone: ---
Assignee: Ville Skyttä
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-10-17 22:14 UTC by Carlos Martín
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2007-01-01 21:53:02 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Carlos Martín 2005-10-17 22:14:42 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; es-ES; rv:1.7.12) Gecko/20050922 Fedora/1.0.7-1.1.fc4 Firefox/1.0.7

Description of problem:

When C source files are compiled with ccache and coverage flags enabled, (-ftest-coverage and -fprofile-arcs), .gcno files are generated, but in ~/.ccache. Those also should move to build directories as .o files does.

There are 2 options, IMHO to solve this kind of problem;

1: Disable ccache: Unfortunately, ccache package installs a ccache.sh file in /etc/profile.d wich force to use it. So it could be posible to clear this file from ccache package.

2: Implement funtionality to move .gcno files to builddir.

Option 2 is an enhacement, so I thought that fastest option to solve this issue is op 1.

Version-Release number of selected component (if applicable):
ccache-2.4-3

How reproducible:
Always

Steps to Reproduce:
1. Install ccache-2.4-3.
2. compile elfutils-115 (from rawhide) witn --enable-gcov 
3. run /tests/coverage.sh
  

Additional info:

Comment 1 Ville Skyttä 2006-02-17 22:38:22 UTC
Doesn't setting CCACHE_DISABLE in the environment satisfy your option 1?  See
the ccache man page for more info.

Comment 3 Ville Skyttä 2007-01-01 21:53:02 UTC
It's been some time, so I'm assuming comment 1 was a sufficient solution.  Feel
free to reopen if not.


Note You need to log in before you can comment on or make changes to this bug.