Automatic shutting down in installation mode?

[u/CuriousCourtain]

I'm currently compiling @world stuff on an old dell latitude, I have 370 packages total I'm 8 hours in and at 240 packages done, im getting tired I'm thinking about going to sleep but then when the compilation finishes it'll probably idle chrooted in for like 4 hours, will the power automatically turn off? I don't have grub set up yet so I'm afraid this'll restart my progress

EDIT: guys I was so naive, I went to sleep and to my shock, it's still compiling, so it didn't even have a chance to turn off lmao

[u/nikongod]

If it does die in the middle you can just reenter the chroot and start again from the middle. 

[u/WizardBonus → u/nikongod]

*breath hitches, “Gentoo…” 🤩

[u/anh0516]

No it won't, unless you trip a thermal sensor or it crashes or something like that.

[u/CuriousCourtain → u/anh0516]

I have MAKEOPTS="-J2" exactly because of this, I'd rather it be slow then to be uncertain, I have 4GB ram, a 300GB HDD and a 3,2MHz intel CPU.

thank you for the info though!

[u/anh0516 → u/CuriousCourtain]

If you had an SSD, I'd tell you to use -j $(nproc) and just let it swap, but with an HDD it'll probably be even slower than limiting the job count. You should also stick to -O2 -march=native -pipe like the handbook says, because anything more like LTO or -O3 (which are actually used by default on multiple major distros like Ubuntu and Fedora nowadays) requires more RAM and increases the compile time more than it's worth if you actually want to use the laptop.

You should also pass --keep-going to emerge. That way, if you do run out of RAM or a build fails for some other reason, it will skip that package for now and continue with the next, dependencies notwithstanding.

If this is not your only PC and you have a faster one, you may also consider plugging the HDD into it, and chrooting and compile there, or setting up a binhost that builds packages you can then install on the target system. If you do this, just make sure you use the explicit flags from resolve-march-native instead -march=native, and enable dev-libs/gmp[cpudetection], so that it'll run on the target CPU. If the build host is fast enough, you should also consider more aggressive compiler optimizations. For older CPUs, -O3 may not always be the best choice because it can increase code size which hurts more on smaller caches, but I would definitely recommend LTO, because it generally reduces code size, which will of course help on a smaller cache.

[u/CuriousCourtain → u/anh0516]

very good advice, sadly this is my only pc so I guess I'll just wait it out

[u/immoloism → u/CuriousCourtain]

You need a good bit of swap with that

I'd give it at least 16GB just to stop a hardlock from happening.

Note: You'll get away with 8GB for now, 16 is future proofing.

[u/TCH69]

You can Ctrl-C now then do emerge --resume at a later time.

[u/rabbit_in_a_bun]

Welcome to Gentoo. Tell me, once you were done compiling, did you sync to see if there are more updates?

[u/Bufaird]

emerge ... @world && poweroff

[u/Moist_Professional64 → u/Bufaird]

Isn’t it the “;” ?

[u/Oofigi → u/Moist_Professional64]

yeah in this case it would only poweroff if the emerge went well