On Wednesday 15 March 2017 at 11:54:19 +, Mike Crowe wrote:
> On Monday 13 March 2017 at 13:51:46 +, Mike Crowe wrote:
> > On Monday 13 March 2017 at 13:33:27 +, Burton, Ross wrote:
> > > On 11 March 2017 at 16:54, Mike Crowe wrote:
> > >
> > > > ccache apparently does this so that pa
On Monday 13 March 2017 at 13:51:46 +, Mike Crowe wrote:
> On Monday 13 March 2017 at 13:33:27 +, Burton, Ross wrote:
> > On 11 March 2017 at 16:54, Mike Crowe wrote:
> >
> > > ccache apparently does this so that paths in the debug information will
> > > always be correct. In an OE world
On Monday 13 March 2017 at 13:33:27 +, Burton, Ross wrote:
> On 11 March 2017 at 16:54, Mike Crowe wrote:
>
> > ccache apparently does this so that paths in the debug information will
> > always be correct. In an OE world these paths may already be missing or
> > incorrect due to rm_work or t
On 11 March 2017 at 16:54, Mike Crowe wrote:
> ccache apparently does this so that paths in the debug information will
> always be correct. In an OE world these paths may already be missing or
> incorrect due to rm_work or the use of a shared sstate cache, so it doesn't
> seem as if we're losing
As of ccache-3.3, ccache will always include the current directory
in the hash when the compiler is configured to output debug
information. The current directory will change every time ${PV}
changes, which will invalidate the cache.
ccache apparently does this so that paths in the debug informatio
