From: "Duncan" <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64] Re: -fPIC - Toolchain broken?
Date: Mon, 23 Oct 2006 15:22:04 +0000 (UTC) [thread overview]
Message-ID: <ehimms$3p9$1@sea.gmane.org> (raw)
In-Reply-To: 20061023162050.48b4e70f@c1358217.kevquinn.com
"Kevin F. Quinn" <kevquinn@gentoo.org> posted
20061023162050.48b4e70f@c1358217.kevquinn.com, excerpted below, on Mon,
23 Oct 2006 16:20:50 +0200:
> 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.
What about adding a space at each end, then testing for a space at each
end of the removed,, but then you have to be sure and add one space back
in so as not to concatenate two flags into one with the removal, so...
CFLAGS=" ${CFLAGS} " ; CFLAGS=${CFLAGS// -fremoved/ /}
If I'm not mistaken, that should eliminate the partial flag matches you
mentioned without causing other issues.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2006-10-23 15:27 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
2006-10-23 15:22 ` Duncan [this message]
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='ehimms$3p9$1@sea.gmane.org' \
--to=1i5t5.duncan@cox.net \
--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