public inbox for gentoo-hardened@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Kevin F. Quinn (Gentoo)" <kevquinn@gentoo.org>
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] Problems compiling xen - please help...
Date: Thu, 2 Feb 2006 22:41:19 +0100	[thread overview]
Message-ID: <20060202224119.740937f8@c1358217.kevquinn.com> (raw)
In-Reply-To: <1138912533.12457.14.camel@localhost>

[-- Attachment #1: Type: text/plain, Size: 1451 bytes --]

On Thu, 02 Feb 2006 15:35:33 -0500
Ned Ludd <solar@gentoo.org> 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 <solar@gentoo.org> 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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2006-02-02 21:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-02 15:03 [gentoo-hardened] Problems compiling xen - please help Ed W
2006-02-02 15:48 ` Ned Ludd
2006-02-02 15:53   ` Ed W
2006-02-02 17:02     ` Ed W
2006-02-04 10:16     ` Peter S. Mazinger
2006-02-02 17:34 ` Kevin F. Quinn (Gentoo)
2006-02-02 17:52   ` Ed W
2006-02-02 17:59     ` Ed W
2006-02-02 18:18       ` Ned Ludd
2006-02-02 19:35         ` Kevin F. Quinn (Gentoo)
2006-02-02 20:35           ` Ned Ludd
2006-02-02 21:41             ` Kevin F. Quinn (Gentoo) [this message]
2006-02-04 10:12 ` Peter S. Mazinger

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=20060202224119.740937f8@c1358217.kevquinn.com \
    --to=kevquinn@gentoo.org \
    --cc=gentoo-hardened@lists.gentoo.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox