1hr+ for a general update* (following the guide. Pre-kernel)
On a more serious note, gentoo is fun… On competent hardware. This is a 4 core Celeron N2940 with 4gb of RAM.
*emerge --ask --verbose --update --deep --changed-use @world is too long to type…
Roughly 8 hours ago, that means you might just now be struggling with a nw manager to get a LAN IP assigned, or worse, a wifi network logged in.
Do you have a gui yet?
I’ve tried Gentoo with a fork (Sabayon Linux). It was all good and fun until I’ve hit huge build times, especially by kernel updates.
If you like living on the cutting edge version of packages, then just use Arch or any derived distro
Legend says it’s still compiling.
pretty spot on with the ‘competent hardware’ part. i’ve read some people automate those on their sleep just to offset the build times.
there’s single letter argument versions on emerge, i think. the long ones are for the learning experience.
@MidsizedSedan using gentoo on thinkpad does not always mean building packages locally
Weather update. 2hr20min. Terminal output hasnt updated since I posted. Close to giving up for the night. (If it STILL hasnt moved in the morning, ill just start again then)
You might have run out of memory. Linking in particular can require lots of RAM, and if you run out, the entire machine will freeze.
It really seems you hit the fun
As a guix user with custom package permutations, I feel your pain.
Gentoo? With 4GB of RAM? That sounds like a challenge!
When trying to run gentoo, if you’re emerging with fewer than a few dozen cores (either in a single machine with something like a threadripper, or in a cluster with
distcc), then I highly recommend using the binary versions of certain packages. This can be done either with-binversions of packages, or something like the Gentoo Binary Host Project.Packages that particularly benifit from using binary versions would primarily web browser or web browser adjacent packages such as Firefox, Chrome, QTWebEngine, but really any particularly large compile that doesn’t benifit from compiling locally (eg: not that many use flags, not likely to use any additional CPU features you might have such as avx512). In fact, bin versions of Web browsers often will perform much better than locally compiled versions since they are compiled with additional optimisations that either make the compile time even longer (O3 and LTO), or require additional manual steps (such as PGO where the unoptomised browser is compiled and ran through real-world workloads with a profiler attached to identify code hotpaths so the compiler can optimise more efficiently during a second complete compile run).
All I have emerged was vim (because nano hurts my muscle memory) and fastfetch (because style points). That took 20 minutes+, but I just hoped its because i didnt select closer mirrors then.
Oh yeah. OpenRC, Desktop profile, multilib, so whatever packages included in there.
If i remember, use flags were : -kde, -gnome, -systemd, wifi… Not TOO crazy
If you’re doing an @world emerge, then you’ll be recompiling all installed packages with updates, including dependencies.
One of the heavier packages that’s included in almost every desktop profile as a dependency somewhere is
dev-qt/qtcore(full list of packages in the standard desktop profile here, though each package listed here will have its own dependencies which may have their own dependencies, etc. So it is not an exhaustive list), qtcore also appears to be what was compiling when the photo in your post was taken so is likely the primary cause of that specific long build time.
ThinkPad? Without clit mouse? Am I supposed to use my own nipple, or god forbid, the TrackPad?
Maybe its just because i dont have a Desktop Environment yet, but my nipple isnt working :(
Nipple support is included in the genital engorgement flatpak
Have you ever played arcade? Do you sometimes wonder which part of your body controls the movement?
ARE YOU NOT ENTERTAINED?
Shoulda stuck with Linux Mint 22.1 Cinnamon edition.
Wtf, it made your TrackPoint disappear.
Gentoo is fantastic for learning. It forced me to get intimate with internals I had no exposure to before. And I learned a lot of little tricks from it that accelerated my career. Or at least made it easier.
I’d try to find something a bit more beefy if you plan on compiling almost everything. And once you get it where you like it, take a backup or system image you can restore to. Because when it breaks, it’ll be a lot less painful to start over.
