5377 – portage ccache usage

Bug 5377 - portage ccache usage

Summary: portage ccache usage

Status:	RESOLVED FIXED

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Unclassified (show other bugs)
Hardware:	All Linux

Importance:	Low minor (vote)
Assignee:	Daniel Robbins (RETIRED)

URL:	http://forums.gentoo.org/viewtopic.ph...
Whiteboard:
Keywords:

Duplicates (1):	5376 (view as bug list)
Depends on:
Blocks:

Reported:	2002-07-22 03:05 UTC by Marc
Modified:	2011-10-30 22:21 UTC (History)
CC List:	1 user (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

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

Description Marc 2002-07-22 03:05:20 UTC

Hi,     
    
I think there's a bug within portage that makes usage of ccache with portage  
difficult. It's about these lines in /usr/lib/portage/bin/ebuild.sh (ll. 125)  
:   
  
#We can enable compiler cache support   
export PATH="/usr/bin/ccache:${PATH}"   
if [ ! -z "${CCACHE_DIR}" ]   
then   
CCACHE_DIR=/root/.ccache   
fi   
addread ${CCACHE_DIR}   
addwrite ${CCACHE_DIR}   
  
Should the  "if[ ! -z ..." statement mean "if[ -z ... " to ensure that if  
there's no ccache path set, then set a default. Cause when you install ccache,  
no CCACHE_DIR will be set, which leads to the impossibility to specify an own  
path as well as leaving CCACHE_DIR unset.

Comment 1 Marc 2002-07-22 03:07:45 UTC

*** Bug 5376 has been marked as a duplicate of this bug. ***

Comment 2 Daniel Robbins (RETIRED) gentoo-dev

2002-07-22 09:45:16 UTC

 yep, this has been fixed in my working version.  Will be fixed in 2.0.16