Search the Community
Showing results for tags 'build'.
Found 3 results
I'll answer first so you get an idea. I play around with Funtoo on this desktop. I'm dual-booting until I become comfortable enough with it. Hopefully I'll become a Linux whiz sometime in the future. I also play around with programming, just python for now. The build is pretty simple: Mobo: MSI MS-7788 CPU: Intel Pentium G630 RAM: 4.00GB GPU: NVIDIA GTX650 In the future I hope to build a new more powerful desktop for faster compile times and such.This one is okay for now because I'm really just a beginner. I think it would be cool to have a list of working hardware builds with different use cases, listing how long it takes to do things like compile a kernel or commands like: emerge -auDN @world . :D
Is it a bad idea to switch the build type from `current` to `stable`? Using `epro build stable`? There is a warning (reported in the command line, as well as in this "epro" wiki-page: http://www.funtoo.org/Funtoo_Profiles): epro build stable WARNING: build already set to current -- typically, user should not change this.
Hello All, I have a question regarding the use flags with the intel64-haswell subarch. Since I don't plan to compile code on any other machine but the computer I'm installing on, why would the use flag -march=core-avx2 be superior to -march=native? Perhaps I'm incorrect, but wouldn't -march=native be best for me? If not, why? I'm really confused by core-avx2. I could be wrong, but I think using -march=native is equivalent to -march=haswell in this case. If so, is -march=haswell different from -march=core-avx2? I did notice that the CPU_FLAGS mentioned on the subarch page missed avx2, so I added that into the CPU_FLAGS within make.conf. Any help would be greatly appreciated. Thanks, Rick