![]() ![]() Those that have never had a hard drive fail. ![]() Silentoldconfig, run at the start of the build, does not always fix it. config that produces a kernel with strange hard to diagnose bugs. If you don't get them all, you end up with an illegal. Some menuconfig options flip many CONFIG symbols. Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5 Of course you need to know your own hardware and usage practices well, so as not to disable something your system requires. If you've never actually gone through your kernel config either manually (editing the file) or with menu config, or xconfig, it's likely you're building far more items than your hardware requires, thus making the compile time much longer than it needs to be. Keep in mind the time required to compile a kernel on any given system is directly dependent on how many items you have enabled in your kernel config. I have dropped to -j1 a few times over 15 years due to weird quirks in compiling certain packages, but for general day-in and day-out practices you would just make sure your cpu cooling is good, and set it for the number of cores your cpu has. j8 on the same cpu and same system -j8 would be utilizing twice the number of cores -j4 would, so all things being equal, take roughly half the time.īut IMO constantly changing your MAKE_OPTS= setting makes little sense. If I understand the question correctly, -j4 vs. What are the compile times when you actually push the chip? ie -j4 (or -j8 for an octal core chip) Gentoo Forums :: View topic - AMD Zen/Ryzen thread ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |