public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Brian Harring <ferringb@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Add --hash-style=gnu to LDFLAGS
Date: Tue, 10 Aug 2010 01:45:48 -0700	[thread overview]
Message-ID: <20100810084548.GG30937@hrair> (raw)
In-Reply-To: <AANLkTi=GPSOpoX4H0fmP-fO=zWXaQ7-JXC0i+oT8CuzT@mail.gmail.com>

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

On Mon, Aug 09, 2010 at 07:05:11PM -0400, Mike Frysinger wrote:
> On Mon, Aug 9, 2010 at 7:03 PM, Markos Chandras wrote:
> > On Sat, Aug 07, 2010 at 10:16:24PM -0400, Mike Frysinger wrote:
> >> obviously you only mean linux x86/amd64 dev profiles.  i dont have a strong
> >> opinion on that small subset in either direction.
> >
> > So do you agree to make this linker option default to linux x86/amd64 dev/
> > profiles?
> 
> add them or dont add them, "i dont have a [...] opinion [...] in
> either direction".  if put to a vote, i'd abstain.

Possibly a stupid question, but any reason we've not looked at 
injecting something that has lower actual affect but can still be used 
for a canary?  I'm thinking of --build-id specifically...

~brian

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2010-08-10  8:48 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-07 16:32 [gentoo-dev] Add --hash-style=gnu to LDFLAGS Markos Chandras
2010-08-07 16:35 ` Tomáš Chvátal
2010-08-07 16:37 ` Alexis Ballier
2010-08-07 16:48   ` Markos Chandras
2010-08-07 18:59     ` Alexis Ballier
2010-08-07 22:08   ` Mike Frysinger
2010-08-07 17:18 ` [gentoo-dev] " Diego Elio “Flameeyes” Pettenò
2010-08-10 21:53   ` Markos Chandras
2010-08-10 22:31     ` Mike Frysinger
2010-08-11  9:11       ` Markos Chandras
2010-08-11 10:42         ` Thilo Bangert
2010-08-12  8:35       ` Christian Faulhammer
2010-08-13 15:11         ` Markos Chandras
2010-08-14  3:43           ` Ryan Hill
2010-08-14  3:50             ` Ryan Hill
2010-08-14  9:23               ` Markos Chandras
2010-08-14  4:14             ` Mike Frysinger
2010-08-14  6:41               ` Ryan Hill
2010-08-14  6:40                 ` Mike Frysinger
2010-08-14 12:08                   ` Markos Chandras
2010-08-14 17:58                     ` Mike Frysinger
2010-08-14 18:05                       ` Markos Chandras
2010-08-14 18:31                       ` Samuli Suominen
2010-08-14 18:34                         ` Mike Frysinger
2010-08-14 19:46                       ` Markos Chandras
2010-08-15  7:31                         ` Christian Faulhammer
2010-08-07 21:32 ` Mike Frysinger
2010-08-08  0:11   ` Markos Chandras
2010-08-08  0:15     ` Alec Warner
2010-08-08  0:21       ` Markos Chandras
2010-08-08  7:57         ` Petteri Räty
2010-08-08  8:37           ` Ryan Hill
2010-08-08  0:22       ` Diego Elio Pettenò
2010-08-08  0:19     ` Diego Elio Pettenò
2010-08-08 11:12       ` Markos Chandras
2010-08-08  2:16     ` Mike Frysinger
2010-08-08 11:14       ` Markos Chandras
2010-08-09 23:03       ` Markos Chandras
2010-08-09 23:05         ` Mike Frysinger
2010-08-10  8:45           ` Brian Harring [this message]
2010-08-10 18:40             ` Francesco R
2010-08-10 20:09               ` Mike Frysinger
2010-08-10 20:16             ` Mike Frysinger

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=20100810084548.GG30937@hrair \
    --to=ferringb@gmail.com \
    --cc=gentoo-dev@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