public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "Kevin F. Quinn" <kevquinn@gentoo.org>
To: Olivier Galibert <galibert@pobox.com>
Cc: binutils@sourceware.org, toolchain@gentoo.org
Subject: Re: Adding -z nonow to complement -z now
Date: Mon, 12 Jun 2006 19:56:00 -0000	[thread overview]
Message-ID: <20060612212204.399d77cc@c1358217.kevquinn.com> (raw)
In-Reply-To: <20060612184810.GA63035@dspnet.fr.eu.org>

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

On Mon, 12 Jun 2006 20:48:10 +0200
Olivier Galibert <galibert@pobox.com> wrote:

> On Mon, Jun 12, 2006 at 08:00:03PM +0200, Kevin F. Quinn wrote:
> > Although some might consider it pointless, it would be very useful
> > to us (Gentoo Hardened project).  We flip the default when building
> > with gcc to set -z now by default.  Our current method of undoing
> > this (which we need to do very occasionally) is via an extra option
> > handled in a gcc specs file; the downside here is that libtool in
> > particular filters our option because it doesn't recognise it.
> > With this, we can pass '-Wl,-z,nonow' in LDFLAGS and libtool pays
> > attention.
> 
> Why don't you fix libtool?

The essential problem for us is that ld doesn't provide a switch-off
option to go with the switch-on option.  There are other downsides that
go with this.  I prefer to tackle that essential issue, especially as
it's trivial to do.

Is there a good reason why this shouldn't be added to ld?

-- 
Kevin F. Quinn

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

  reply	other threads:[~2006-06-12 19:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-12 18:49 Kevin F. Quinn
2006-06-12 18:54 ` Olivier Galibert
2006-06-12 19:56   ` Kevin F. Quinn [this message]
2006-06-13  1:59 ` Alan Modra
2006-06-13 17:27   ` Ulrich Drepper
2006-06-13 18:10     ` Kevin F. Quinn
2006-06-14  0:41     ` Kevin F. Quinn
2006-06-14  6:07       ` Alan Modra

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=20060612212204.399d77cc@c1358217.kevquinn.com \
    --to=kevquinn@gentoo.org \
    --cc=binutils@sourceware.org \
    --cc=galibert@pobox.com \
    --cc=toolchain@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).