Hi Keith, I'm using arch linux which keeps it's kernels fairly up to date. If the kernel version isn't too old, i.e. 4.5 or later then that should be fine. Still I think it will be worth commenting out all three config options on your system and then trying. Cheers, Okash > On 17 Apr 2017, at 23:28, Keith Barrett <lists@xxxxxxxxxxxxxxxxxxx> wrote: > > > Hi Okash, > > What system are you using for your tests? > > I was using stretch am64 rc3 but as the machine is not being used for anything else, I could get something else on it for testing. > > >> On 17/04/17 22:57, Okash Khawaja wrote: >> Hi Keith, >> >> This might be because the existing config is too old for 4.10 kernel. >> I wouldn't know the solution without trying it out. From one of the >> links I posted above, they removed following in 4.5 kernel: >> >> CONFIG_MODULE_SIG_ALL >> CONFIG_MODULE_SIG_KEY >> CONFIG_SYSTEM_TRUSTED_KEYS >> >> So it might be worth removing all three of them and then trying. >> >> Cheers, >> Okash >> >> >> On Sat, Apr 15, 2017 at 5:57 PM, Keith Barrett >> <lists@xxxxxxxxxxxxxxxxxxx> wrote: >>> Hi Okash, >>> >>> I commented out the two entries and now we get:- >>> >>> certs/system_keyring/o make[1] no rule to make target >>> 'debian/certs/benh@xxxxxxxxxxxxxxxxxxx' needed by >>> 'certs/si09_certificate_list' stop recipe for target failed' >>> >>> >>> >>> >>>> On 15/04/17 07:35, Okash Khawaja wrote: >>>> >>>> Hi Keith, >>>> >>>>> On 14 Apr 2017, at 17:28, Keith Barrett <lists@xxxxxxxxxxxxxxxxxxx> >>>>> wrote: >>>>>> >>>>>> >>>>>> No Rule to make target 'debian/certs/benh@xxxxxxxxxxxxxxxxxxx' needed by >>>>>> certs/si09-certificate_list. >>>>> >>>>> makefile 988: recipe for target 'certs' failed make certs error 2. >>>> >>>> >>>> Found this by searching the error online: >>>> >>>> >>>> https://unix.stackexchange.com/questions/293642/attempting-to-compile-any-kernel-yields-a-certification-error >>>> >>>> Here's the reply from that link: >>>> >>>> "I ran into this several years ago on a Debian build. In the .config file >>>> you copied from /boot find and comment out the lines >>>> CONFIG_SYSTEM_TRUSTED_KEY and CONFIG_MODULE_SIG_KEY." >>>> >>>> There's also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823107 >>>> >>>> >>>> >>>> Basically make oldconfig should have taken care of this. >>>> >>>> Hope that helps. >>>> >>>> Okash >>>> _______________________________________________ >>>> Speakup mailing list >>>> Speakup@xxxxxxxxxxxxxxxxx >>>> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup >>> _______________________________________________ >>> Speakup mailing list >>> Speakup@xxxxxxxxxxxxxxxxx >>> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup >> _______________________________________________ >> Speakup mailing list >> Speakup@xxxxxxxxxxxxxxxxx >> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup > _______________________________________________ > Speakup mailing list > Speakup@xxxxxxxxxxxxxxxxx > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup _______________________________________________ Speakup mailing list Speakup@xxxxxxxxxxxxxxxxx http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
