From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-la0-f46.google.com ([209.85.215.46]:55619 "EHLO mail-la0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751505AbaEBIpg (ORCPT ); Fri, 2 May 2014 04:45:36 -0400 Received: by mail-la0-f46.google.com with SMTP id pv20so2876040lab.33 for ; Fri, 02 May 2014 01:45:35 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <20140502013948.GH957@garbanzo.do-not-panic.com> From: "Luis R. Rodriguez" Date: Fri, 2 May 2014 01:45:14 -0700 Message-ID: (sfid-20140502_104539_389789_AEA15C54) Subject: Re: 3.14-1 Compile Problem for 2.6.39.4 Kernel To: Aaron Hamilton Cc: "backports@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Sender: backports-owner@vger.kernel.org List-ID: On Fri, May 2, 2014 at 1:36 AM, Aaron Hamilton wrote: > If I recall correctly, I was able to get this to compile by enabling > CONFIG_CRYPTO_CCM in my kernel. Without it, it won't compile. Yeah that would do it: mcgrof@drvbp1 ~/ksrc-backports $ grep CRYPTO_CCM lib/modules/2.6.39-02063904-generic/build/.config CONFIG_CRYPTO_CCM=m Unfortunately right now we don't compile tests against random configs but as you can imagine doing so would take quite a bit of time. Even so, we need a way to be able to nudge the config a bit to compile everything we do expect to ship without compromising the config enough. That might be tricky, best I can say for now is that we do need a bit more review / help with alternative base configs. Luis