| 1 |
On Monday 25 September 2006 02:27, David Fellows wrote: |
| 2 |
|
| 3 |
> So verify again, emerge imagemagick with your fancy cc options. If you |
| 4 |
> get the error message again, then either the ebuild or autoconf is |
| 5 |
> selecting a 3.6 version of gcc to compile with, Presumably by setting |
| 6 |
> CTARGET. |
| 7 |
|
| 8 |
What I'm doing at the moment is to emerge -e world without -compile |
| 9 |
or -ftree-pre. Kde-base/juk failed to compile, the loader complaining about |
| 10 |
an undefined reference. I'll look into that later; at present I still have |
| 11 |
47 of the 709 packages to go [1] before I have a complete GCC-4.1.1 system. |
| 12 |
Then I'll see about adding those two flags back in. |
| 13 |
|
| 14 |
To remove any doubt, I did an rm -rf /var/log/portage and /var/tmp/portage |
| 15 |
before starting emerge -e world. That was last night; this morning I find |
| 16 |
that portage has removed all its /var/tmp/portage/*/work directories apart |
| 17 |
from those of failed packages, and of course the package it's currently |
| 18 |
working on. Is this new behaviour of portage? I don't think I've changed |
| 19 |
any make.conf FEATURES, but I've been used to finding vast wodges of disk |
| 20 |
space occupied by work directories (quote: FEATURES="ccache sandbox"). |
| 21 |
Also /var/log/portage is full of stuff too, which I must devise a way to |
| 22 |
keep under control. |
| 23 |
|
| 24 |
[1] Down to 43 packages now; progress is slow now that it's got into the |
| 25 |
kde packages. |
| 26 |
|
| 27 |
-- |
| 28 |
Rgds |
| 29 |
Peter |
| 30 |
-- |
| 31 |
gentoo-amd64@g.o mailing list |
Archives