Gentoo Archives: gentoo-amd64

From: Peter Humphrey <prh@××××××××××.uk>
To: gentoo-amd64@l.g.o
Subject: Re: [gentoo-amd64] Re: vectorization (was: gcc4 CFLAGS)
Date: Sun, 24 Sep 2006 11:53:44
Message-Id: 200609241147.22022.prh@gotadsl.co.uk
In Reply to: [gentoo-amd64] Re: vectorization (was: gcc4 CFLAGS) by Duncan <1i5t5.duncan@cox.net>
1 On Saturday 23 September 2006 23:50, Duncan wrote:
2
3 > I've not done a full emerge --emptytree world with -combine in my
4 > CFLAGS, so while I know it doesn't kill a majority of packages, it
5 > apparently does kill a few. Still, for the additional optimization it
6 > enables, I consider it worth it on the others.
7
8 Is there a way to specify CFLAGS on the command line in such a way as to
9 negate (unset) those that are set in /etc/make.conf? I have -combine
10 and -ftree-pre in make.conf, and while emerge -e world is running it fails
11 some packages by not recognising those two. When that happens I want to
12 emerge --resume --skipfirst so as not to lose my place in the world emerge,
13 and in another terminal emerge the ones that have failed.
14
15 I can think of an expensive way to obtain the same effect, namely to remove
16 the two offending flags from make.conf, run emerge -e world, replace the
17 flags and emerge -e world again, using --skipfirst every time that one
18 stops.
19
20 Or I could write a script that keeps resuming a failed emerge until it
21 finishes. Not sure how I'd go about that: how would the script distinguish
22 the end of the emerge from in interruption of it?
23
24 The last option would be to create a bug for each package that stops on
25 unrecognised flags, but I'd rather continue to be able to talk to
26 people :-(
27
28 Apologies if I seem to be thinking on my feet here.
29
30 --
31 Rgds
32 Peter
33 --
34 gentoo-amd64@g.o mailing list

Replies

Subject Author
Re: [gentoo-amd64] Re: vectorization (was: gcc4 CFLAGS) "Kevin F. Quinn" <kevquinn@g.o>
[gentoo-amd64] Re: vectorization (was: gcc4 CFLAGS) Duncan <1i5t5.duncan@×××.net>