McQ

The output from this command gives you the subarch for your cpu.
gcc -march=native -Q --help=target | grep march Find the output of -march=  that matches in the right column printed in red here:
http://www.funtoo.org/Subarches#amd64
Click the link to download optimized stage at the beginning of the line where you  find the matching march.
For example if "-march=  amdfam10"
Download http://www.funtoo.org/Amd64-k10
 
 
 
Reference:
http://www.funtoo.org/Install#Installing_the_Stage_3_tarball
http://www.funtoo.org/Subarches

emerge -av =app-admin/ego-1.1.3-r5
ego sync
emerge -avuDN @world

In order to get the eix-sync functionality i've created the following alias
alias eixsync="ego sync && eix-sync -u" When we pass -u to eix-sync it does all its work without the "emerge --sync" part so it syncs through ego and then it updates eix databases and run eix-diff
 
Hope this can help someone  :)

Build microcode cpio with iucode_tool and load as initrd, If there is a problem disable in the grub menu prior to boot.

and from my own experience, i have never used stable builds anywhere and there was no really major problems (like disastrous ones), maybe 2-3 only in last 10 years. so, a key is - when you know what to do with stable or unstable - you could expect things to work. if you don't know what to do, likely you'll trap into troubles regardless stable or unstable used. Sometimes updates can be frustrating, i agree. And for newcomers, of course, it's hard as they mostly driven by existing documentation, web, irc -which can be really wrong. The "stable" is what is controlled by matter of letter, in ebuilds, i can put "amd64" instead "~amd64" and it will be considered stable by package manager, which is of course far from real definition of stable. For example, back into not so old case (about 4 monthes), xorg-server-1.19 stabilized by gentoo, due to multiple security vulnerabilities in xorg itself and in it's core parts. xorg-1.19, in turn, found to be very unstable in certain conditions, so the security fixes diminished by the fact you have no working xorg. Those security fixes can be easily, and they are in Funtoo, backported into good known 1.17 version. of course, if 1.19 were ok for the one, he could choose using 1.19. Just trying to describe that stabilization and stable by means of packages, is a volatile term.

Forum search returns no results:https://bugs.funtoo.org/browse/FL-2718

Arch is "near to *too".
But by default you've precompiled packages.
With *too Portage will compilete your ebuilds (packages)
 
I know that is possible to use aur or yaourt (time ago) to compile from sources.
 
I think that about source-based distributions, *too then the "Portage" is the more genial & eclectic.
 
@McQ have you ever used the subarch "native_64" ?
 
For me ... simply the best cause can be differencies. I make an example about core2 processors:
core2 I generation uses up to SSSE3 SIMD; but if you have a 2nd generation ("Penryn") core2 cpu you will have also the SSE4.1
 
Then i think that only the "native" can optimize perfectly.
 
Another example: i've a core i7 4771 (Haswell) but there are differencies from a 4770K (unlocked) and 4771 (locked but 3 instructions more for Vt technology)
 
to see the flags passed ... open a terminal then digit:
echo 'int main(){return 0;}' > test.c && gcc -v -Q -march=native -O2 test.c -o test && rm test.c test Then open a 2nd terminal and try 
echo 'int main(){return 0;}' > test.c && gcc -v -Q -march=westmere -O2 test.c -o test && rm test.c test Compares the 2 terminals and take a look if there are differencies or not.
 
I use this method
 
I wish not to have bored you :)