On Thu, 02 Feb 2006 15:35:33 -0500 Ned Ludd <[EMAIL PROTECTED]> wrote:
> On Thu, 2006-02-02 at 20:35 +0100, Kevin F. Quinn (Gentoo) wrote: > > On Thu, 02 Feb 2006 13:18:46 -0500 > > Ned Ludd <[EMAIL PROTECTED]> wrote: > > > > > On Thu, 2006-02-02 at 17:59 +0000, Ed W wrote: > > > > Heads up then that when switching compiler to the non-hardened > > > > one it makes sense to blow away the ccache of disable it's use. > > > > > > That probably makes sense for any time a gcc-config switch > > > happens. You should probably file a bug about that for the > > > maintainer of gcc-config. > > > > ccache doesn't take account of anything other than the built-in > > specs files and stuff specified via --specs - we could just patch > > ccache to pay attention to GCC_SPECS as well. I'll take a look. > > Ok cool but keep in mind. > > USE=-hardened emerge gcc > gcc-config 1 > echo $GCC_SPECS > > USE=hardened emerge gcc > gcc-config 1 > echo $GCC_SPECS > > Both times it shall be "" with the same version of gcc. The hash does include the size & mtime of the compiler driver - although that'll be the wrapper in most cases, I guess, which may not be good enough. bug #121336 btw actually I think hashing the files in GCC_SPECS won't work, as ccache doesn't see GCC_SPECS because it's set by the compiler wrapper. I think it may be enough to hash in the output of '<compiler> -v'... -- Kevin F. Quinn
signature.asc
Description: PGP signature
