public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Kevin F. Quinn" <kevquinn@gentoo.org>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64]  Re: -fPIC - Toolchain broken?
Date: Mon, 23 Oct 2006 16:20:50 +0200	[thread overview]
Message-ID: <20061023162050.48b4e70f@c1358217.kevquinn.com> (raw)
In-Reply-To: <eh8o1g$cbe$3@sea.gmane.org>

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

On Thu, 19 Oct 2006 20:43:28 +0000 (UTC)
"Duncan" <1i5t5.duncan@cox.net> wrote:

> Simon Stelling <blubb@gentoo.org> posted 45379CDC.1010504@gentoo.org,
> excerpted below, on  Thu, 19 Oct 2006 17:42:20 +0200:
> 
> > If you want to add instead of replace, CFLAGS="${CFLAGS} -fadded"
> > will do the job. Removing is done with CFLAGS=" ${CFLAGS}" ;
> > CFLAGS=${CFLAGS//-fremoved}

FWIW I think Simon meant:

CFLAGS=" ${CFLAGS}" ; CFLAGS=${CFLAGS// -fremoved}

assuming that adding the space was done to catch flags that match part
of longer flags.

> > So you can do effectively anything, given you know the bash
> > tricks ;)
> 
> Hey, thanks!  The add was a no-brainer here, but I hadn't thought
> about the remove trick yet.  Very nice! =8^)

Watch also for flags that start with the same string; for example:

  CFLAGS=${CFLAGS// -finline-functions}

would end up with "-called-once" in CFLAGS, if
"-finline-functions-called-once" was set.

Another easy one is doing:

  CFLAGS=${CFLAGS// -g}

when CFLAGS has "-ggdb2" or similar set...

-- 
Kevin F. Quinn

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

  parent reply	other threads:[~2006-10-23 14:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-18 15:08 [gentoo-amd64] -fPIC - Toolchain broken? Sebastian Redl
2006-10-18 15:28 ` Hemmann, Volker Armin
2006-10-18 15:53 ` Simon Stelling
2006-10-18 16:08   ` Simon Stelling
2006-10-18 17:41   ` Sebastian Redl
2006-10-18 18:32     ` Simon Stelling
2006-10-18 21:21 ` [gentoo-amd64] " Duncan
2006-10-19  9:54   ` Sebastian Redl
2006-10-19 13:11     ` Conway S. Smith
2006-10-19 15:42       ` Simon Stelling
2006-10-19 20:43         ` Duncan
2006-10-20  9:10           ` Simon Stelling
2006-10-23 14:20           ` Kevin F. Quinn [this message]
2006-10-23 15:22             ` Duncan
2006-10-19 20:33     ` Duncan

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=20061023162050.48b4e70f@c1358217.kevquinn.com \
    --to=kevquinn@gentoo.org \
    --cc=gentoo-amd64@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