@kura @nichii I gave Gentoo a shot. I actually love it for its documentation that is possibly only 2nd to Arch's. I loved portage. It was very straightforward. Only reason I went back to Arch was the compile times on Gentoo. It took more than a day and a half and was still compiling Firefox... I'd probably use Gentoo if I could find a way to at least mitigate that issue.
@apaperez Yeah, that's the big reason why I prefer arch over gentoo. The compiling times are too long for me.
@apaperez @nichii get a decent cpu (never had that issue on a modern one). use compiler caches (drastically reduces recompile times). use appropriate gcc flags (more specialized flags, especially on gcc, is faster compile time). check your USE flags (the less you USE, the less to compile). check for distributed compiling (if you have multiple machines. examples are distcc and icecc/icecream).
@kura @nichii I had it running with a KDE Plasma DE. I have a somewhat generic quad core intel cpu with 8gb of ram on the machine I tried it with. I followed the wiki to set something to perform multiple jobs based on how many cores I had. I set that, but to no avail. I recently tried an install of Calculate Linux to see if it would create the file any differently. As soon as I have some time, Ill give it another shot. It does require lots of time and patience.
also, if you change your march or mtune flags (I suggest march over mtune. Read the 2 links there) you should recompile gcc twice.
You run a stage one gcc.
When u compile gcc first, it creates a stage 2 gcc (optimized gcc with generic code gen)
you compile a second time, you get stage 3 (optimized gcc with optimized code gen).
not sure if the ebuild does it on its own now. check the log output if it compiles twice.
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!