Volker Armin Hemmann wrote:
> On Montag 06 Juli 2009, Jarry wrote:
>
>> Hi,
>> I just tried to update gcc (actually, it is just recompiling with
>> new nptl flag), but it failed with this messages:
>> __________
>>
>> >>> Failed to emerge sys-devel/gcc-4.3.2-r3, Log file:
>> >>>
>> >>> '/var/tmp/portage/sys-devel/gcc-4.3.2-r3/temp/build.log'
>>
>> * Messages for package sys-devel/gcc-4.3.2-r3:
>>
>> *
>> * ERROR: sys-devel/gcc-4.3.2-r3 failed.
>> * Call stack:
>> * ebuild.sh, line 49: Called src_compile
>> * environment, line 4870: Called toolchain_src_compile
>> * environment, line 5396: Called gcc_src_compile
>> * environment, line 3094: Called gcc_do_make
>> * environment, line 2884: Called die
>> * The specific snippet of code:
>> * emake LDFLAGS="${LDFLAGS}" STAGE1_CFLAGS="${STAGE1_CFLAGS}"
>> LIBPATH="${
>> LIBPATH}" BOOT_CFLAGS="${BOOT_CFLAGS}"
>> ${GCC_MAKE_TARGET} || die "emake failed with ${GCC_MAKE_TARGET}";
>> * The die message:
>> * emake failed with bootstrap-lean
>> *
>> * If you need support, post the topmost build error, and the call
>> stack if relevant.
>> * A complete build log is located at
>> '/var/tmp/portage/sys-devel/gcc-4.3.2-r3/temp/build.log'.
>> * The ebuild environment file is located at
>> '/var/tmp/portage/sys-devel/gcc-4.3.2-r3/temp/environment'.
>> __________
>>
>> What does it mean, and how can I fix it???
>>
>> Jarry
>>
>
> that means that you forgot to copy the important part. You just copied the
> pretty useless vanilla portage error. Not the real error some lines above
> that
> one.
>
>
>
And based on a little searching, you may want to post emerge --info as
well. There appears to be a version of kernel that doesn't like this
gcc version. Note the word "appears".
Dale
:-) :-)
