Re: [gentoo-amd64] GCC 4 CFLAGS

[Peter Humphrey]

On Monday 25 September 2006 07:22, Peter Humphrey wrote:
> On Monday 25 September 2006 02:27, David Fellows wrote:
> > So verify again, emerge imagemagick with your fancy cc options. If you
> > get the error message again, then either the ebuild or autoconf is
> > selecting a 3.6 version of gcc to compile with, Presumably by setting
> > CTARGET.
>
> What I'm doing at the moment is to emerge -e world without -compile

Yet another typo. I meant -combine, of course. Sorry.

> or -ftree-pre. Kde-base/juk failed to compile, the loader complaining
> about an undefined reference. I'll look into that later; at present I
> still have 47 of the 709 packages to go [1] before I have a complete
> GCC-4.1.1 system. Then I'll see about adding those two flags back in.
>
> To remove any doubt, I did an rm -rf /var/log/portage and
> /var/tmp/portage before starting emerge -e world. That was last night;
> this morning I find that portage has removed all its
> /var/tmp/portage/*/work directories apart from those of failed packages,
> and of course the package it's currently working on. Is this new
> behaviour of portage? I don't think I've changed any make.conf FEATURES,
> but I've been used to finding vast wodges of disk space occupied by work
> directories (quote: FEATURES="ccache sandbox"). Also /var/log/portage is
> full of stuff too, which I must devise a way to keep under control.
>
> [1]  Down to 43 packages now; progress is slow now that it's got into the
> kde packages.

Now finished, and started on emerge -e world with the two CFLAGS reinstated. 
Watch this space...

-- 
Rgds
Peter
-- 
gentoo-amd64@g.o mailing list