SOLVED: Very Long Rust Emerge on Old Laptop

Message

robert1234 · Post by **robert1234** » Sun Feb 28, 2021 2:51 pm

Does it sound realistic that Rust would take over 2 days to compile on an old Intel core i3 processor? Or should I kill it and try to see if something is wrong?

mike155 · Post by **mike155** » Sun Feb 28, 2021 3:43 pm

Rust is a huge package and needs a lot of time to emerge. But 2 days is probably too long.

Don't stop emerge yet. Try to find out what's going on. Check for excessive swapping.

Post by **fedeliallalinea** » Sun Feb 28, 2021 3:45 pm

I agree with mike155, in my i7-6700HQ

Code: Select all

Tue Nov 17 20:08:44 2020 >>> dev-lang/rust-1.46.0
       merge time: 1 hour, 20 minutes and 8 seconds.

robert1234 · Post by **robert1234** » Sun Feb 28, 2021 5:46 pm

I'm actually still in the installation. I tried to chroot into the installation in a different tty, and the chroot command has been running for 30 minutes.

Anon-E-moose · Post by **Anon-E-moose** » Sun Feb 28, 2021 5:56 pm

some of the early i3's were slow and memory constrained (more likely what's happening)

What specs on the emerge machine, which i3, how much memory, have you set up a swap partition/file?

Irre · Post by **Irre** » Sun Feb 28, 2021 6:03 pm

Or: emerge rust-bin

mike155 · Post by **mike155** » Sun Feb 28, 2021 6:08 pm

robert1234 wrote:I tried to chroot into the installation in a different tty, and the chroot command has been running for 30 minutes.

That's a typical sign for excessive swapping.

You don't need to chroot. Start 'top' and look at the line with the swap values:

Code: Select all

MiB Swap:   1952.0 total,   1952.0 free,      0.0 used.   6912.7 avail Mem

Is the 'free' value close to zero and do the numbers change every few seconds?

Does your machine have a HDD LED? Is it constantly on? That's another sign for excessive swapping.

robert1234 · Post by **robert1234** » Mon Mar 01, 2021 1:03 am

For some reason I had set -j4 for my makeopts when I should have set -j2. I changed this and restarted the emerge. Now it seems like it is emerging properly. It is much more responsive to inputs, and other commands now run fine. I am hoping this fixed the problem. Perhaps I will know by morning...

edit: Rust has now completed emerging. Mission success.

Post by **NeddySeagoon** » Mon Mar 01, 2021 9:30 am

robert1234,

If MAKEOPTS="j4" is what you really want to use, its possible set overides oh anything in make.conf on a per packages basis.
That lets you use MAKEOPTS="j4" for everything except rust and other big packages.

eccerr0r · Post by **eccerr0r** » Tue Mar 02, 2021 8:11 am

Rust should not take more than 29 hours - or at least that's how long it takes on my *really* slow laptop ...

(Atom 1.6GHz, single core -- probably slowest general purpose SSE2 processor out there? Any other slower ones?)

BTW I had been trying to compile rust on my i5 laptop, and due to trying to build with a limited amount of RAM and tmpfs, it swapped heavily... and took a bit bite out of endurance on one of my SSDs...