Re: Re: How is it possible ???

Ths fits in with my experiance - though I have only done a few ebuilds
manually when experimenting.  I think the main reason given is that bugs
from overzealous flags were very common in the early gentoo days so in
order to reduce the dev workload many just filter by default ( an
individual choice from what I can gather).  I believe their position is
that the gains from most optimisations are minimal (~10% over basic if
you are lucky) they do not think this is much of a real concern or loss
considering their gain.

Unfortunately I think this goes against the spirit of gentoo and
curtails those who really do need that 10%, or think they do.  This
should be a user choice, and the workload issue handled otherwise!

BillK

On Thu, 2005-01-06 at 21:57 -0800, Patrick Audley wrote:
> On Thursday 06 January 2005 04:46, William Kenworthy wrote:
> > Have a read of the ebuild - compiling gentoo with your own choice of
> > optimisations is is almost a myth!  There's been some interesting
> > threads about the predominance of flag filtering and how it often seems
> > to be used with little cause.
> 
> I have a hacked gcc-config profile that calls a perl script for all the gcc 
> executables that forces my cflags to be what I want and aside from ten 
> packages on my entire system I'm able to run without any problems.  That 
> includes X (though not glibc).  I think strip-compiler flags might be a good 
> idea for some systems but clearly on mine it's not necessary.
> 


--
[email protected] mailing list