views:

57

answers:

1

I've been compiling it in a virtual machine for over 8 hours now and it still hasn't finished.

The terminal is still printing things so I know it's still compiling.

The host system is a 2.10Ghz Intel Core2Duo with 4GB RAM and the guest is Linux on a PowerPC virtual machine (QEMU) one with 1GB RAM.

I know the dynamic instruction translation can slow things down a bit but even so, Glibc shouldn't take longer than 3 hours or so?

Is there something wrong or should I just continue to let do it's thing overnight?

+1  A: 

For comparison, the last time Ubuntu compiled eglibc for a 64-bit machines, it took about 1.75 hours for amd64, and about 2.5 hours for both i386 and powerpc

I think it's just that dynamic translation is that slow, especially dynamic translation to a different architecture.

Evan Broder
From the same link, I looked up the compile times for uClibc and they were way shorter.Would using uClibc be a better option in this instance?
Tangrs