SEO

Hi,

I just got Gentoo running on a somewhat antiquated PC (it's only an AMD
K6-2, IIRC).

I have been trying to 'emerge -u world' or 'emerge -u system', and the
first line listed (if I add the -p) is gcc. But, it always gives me an
error after a few hours of trying to emerge gcc.

I figured it might help if I emerged gcc alone (I don't really know why
it would...), so I tried 'emerge -p gcc', and noticed that it was going to
emerge glibc first, instead of after gcc ("emerge -up world" and "emerge
-up system" both list gcc first, then glibc). I also tried 'emerge -p
glibc' and noticed, oddly, that it would try to emerge gcc first. (That
alone doesn't make sense to me. 'emerge -up world', 'emerge -up system',
and 'emerge -up glibc' all list gcc as the first package to emerge, but
'emerge -up gcc' lists glibc as the first to emerge...)

So I tried 'emerge -u gcc' thinking maybe if I updated glibc first. But I
got an error after about 5 hours of compiling that:

| gcc gb18030.c -c -std=gnu99 -O2 -Wall -Winline -Wstrict-prototypes
| -Wwrite-strings -freorder-blocks -mcpu=i486 -pipe -fPIC
| -I../include -I.
| -I/var/tmp/portage/glibc-2.3.2-r3/work/glibc-2.3.2/buildhere/iconvdata
| -I.. -I../libio
| -I/var/tmp/portage/glibc-2.3.2-r3/work/glibc-2.3.2/buildhere
| -I../sysdeps/i386/elf -I../linuxthreads/sysdeps/unix/sysv/linux/i386
| -I../linuxthreads/sysdeps/unix/sysv/linux
| -I../linuxthreads/sysdeps/pthread -I../sysdeps/pthread
| -I../linuxthreads/sysdeps/unix/sysv -I../linuxthreads/sysdeps/unix
| -I../linuxthreads/sysdeps/i386 -I../sysdeps/unix/sysv/linux/i386
| -I../sysdeps/unix/sysv/linux -I../sysdeps/gnu -I../sysdeps/unix/common
| -I../sysdeps/unix/mman -I../sysdeps/unix/inet
| -I../sysdeps/unix/sysv/i386
| -I../sysdeps/unix/sysv -I../sysdeps/unix/i386 -I../sysdeps/unix
| -I../sysdeps/posix -I../sysdeps/i386/i486 -I../sysdeps/i386/fpu
| -I../sysdeps/i386 -I../sysdeps/wordsize-32 -I../sysdeps/ieee754/ldbl-96
| -I../sysdeps/ieee754/dbl-64 -I../sysdeps/ieee754/flt-32
| -I../sysdeps/ieee754 -I../sysdeps/generic/elf -I../sysdeps/generic
| -nostdinc -isystem /usr/lib/gcc-lib/i486-pc-linux-gnu/3.2.3/include
| -isystem /usr/include -D_LIBC_REENTRANT -include
| ../include/libc-symbols.h -DPIC -DSHARED -DNOT_IN_libc -o
| /var/tmp/portage/glibc-2.3.2-r3/work/glibc-2.3.2/buildhere/iconvdata/gb18030.os
| make[1]: *** [iconvdata/others] Terminated make[1]: Leaving directory
| `/var/tmp/portage/glibc-2.3.2-r3/work/glibc-2.3.2' make: *** [all]
| Error 2
|
| !!! ERROR: sys-libs/glibc-2.3.2-r3 failed.
| !!! Function src_compile, Line 442, Exitcode 2
| !!! (no error message)

Is this a comprehensible error?

I assume I've done something wrong, but don't know where to start.

Can anyone please point me in the right direction to get this resolved, so
I can update my world?

--
Lenroc

Lenroc wrote:


> I have been trying to 'emerge -u world' or 'emerge -u system', and the
> first line listed (if I add the -p) is gcc. But, it always gives me an
> error after a few hours of trying to emerge gcc.

The first question is whether it always fails at the same place with the
same error or whether it fails at any given spot.

In the first case, there's probably s/th wrong with our installation and
we'll have to look more closely at the error. In the second case, your
hardware is not up to running at 100% for extended periods of time. Typical
culprits would be faulty RAM or an overheating CPU (but it could also be
your harddrive, hd controller, ...).

HTH,

Anno.

On Thu, 15 Jan 2004 08:26:23 +0100, Anno v. Heimburg wrote:

> The first question is whether it always fails at the same place with the
> same error or whether it fails at any given spot.

Ah... ok. I have the logs from a number of attempts, and will try to make
some sort of sense out of them to try to figure this one out

> In the first case, there's probably s/th wrong with our installation and
> we'll have to look more closely at the error. In the second case, your
> hardware is not up to running at 100% for extended periods of time. Typical
> culprits would be faulty RAM or an overheating CPU (but it could also be
> your harddrive, hd controller, ...).

This is very possible. I actually found the computer 'in' the trash
(actually on the ground, near the trash, where people in my apartment
complex put things that may be useful to someone else...), so I've no way
to vouch for how good the computer is

I may need to look into compiling on my primary machine.

Thanks for the help!

--
Lenroc