On 7/7/20 1:55 PM, Giuseppe Sacco wrote: >> Why aren't you bisecting the kernel using git so you find the actual >> commit that broke the build? This way you will find the problem much >> quicker. > > This is a possibility, but I was unaware that the bisect works between > branches (5.4 and 5.6). And, each recompile from scratch last about 6-7 > hours, so I prefer to work on a single kernel version, adding printk > somewhere and rebuilding only what is changed.
You don't have to bother about branches, just work with the master branch. And I wouldn't recommend building the kernel natively but rather cross-compile from a fast x86 machine. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
