Randy Barlow <[EMAIL PROTECTED]> writes:
> [EMAIL PROTECTED] wrote:
>> I've pared down my system to a minimal state.
>>
>> emerge --depclean returns no actions needed, but I think it may have
>> gotten a litte too exuberant.
>>
>> revdep-rebuild wants to rebuild python but the emerge fails here:
>>
>>>>> Source unpacked.
>>>>>
>>>>> Compiling source in
>>>>> /var/tmp/portage/dev-lang/python-2.5.1-r4/work/Python-2.5.1 .
>> ..
>>
>> * econf failed
>>
>> [...]
>> * The ebuild environment file is located at
>> '/var/tmp/portage/dev-lang/python-2.5.1-
>> r4/temp/environment'.
>>
>> *
>>
>>
>> [...]
>
> What's in this "[...]"? The error message that matters the most is
> likely to be in there...
It didn't look like it.
I don't have it now since I've found I the switch to minimal has
caused my gcc to not be ready to compile binaries.
I'm in there now with live cd trying to fix things up.
I copied the livecd gcc binary on /mnt/gentoo/mybin.
I've chrooted into the problem OS after mounting the livecd proc
directory on it, and attempting to emerge gcc, after adding /mybin
first in the $PATH variable.
Here is that error message:
[...]
gcc-config error: Could not run/locate "gcc"
*** The command 'gcc -o conftest conftest.c' failed.
*** You must set the environment variable CC to a working compiler.
*
* ERROR: sys-devel/gcc-3.4.6-r2 failed.
* Call stack:
* ebuild.sh, line 46: Called src_compile
* environment, line 4540: Called toolchain_src_compile
* environment, line 5022: Called gcc_src_compile
* environment, line 2903: Called gcc_do_configure
* environment, line 2669: Called die
* The specific snippet of code:
* "${S}"/configure ${confgcc} $@ ${EXTRA_ECONF} || diefunc "$FUNCNAME"
"$LINENO" "$?" "failed to run configure";
* The die message:
* failed to run configure
*
--
[EMAIL PROTECTED] mailing list
