All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
To: Aaron Hamilton <aaron@logicdatasystems.net>
Cc: "backports@vger.kernel.org" <backports@vger.kernel.org>
Subject: Re: 3.14-1 Compile Problem for 2.6.39.4 Kernel
Date: Fri, 2 May 2014 01:45:14 -0700	[thread overview]
Message-ID: <CAB=NE6U6Cxt2cToUJACh3emLDFSKb-Fq864c_kEH3ZBe8mJ0PA@mail.gmail.com> (raw)
In-Reply-To: <CAFjWW+ZzSvWzAWOC3dzDPujszXYs-pHkSr7wNiLJwwc3a-+-wQ@mail.gmail.com>

On Fri, May 2, 2014 at 1:36 AM, Aaron Hamilton
<aaron@logicdatasystems.net> 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

      reply	other threads:[~2014-05-02  8:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-29  9:39 3.14-1 Compile Problem for 2.6.39.4 Kernel Aaron Hamilton
2014-05-02  1:39 ` Luis R. Rodriguez
2014-05-02  6:51   ` Luis R. Rodriguez
2014-05-02  8:36   ` Aaron Hamilton
2014-05-02  8:45     ` Luis R. Rodriguez [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAB=NE6U6Cxt2cToUJACh3emLDFSKb-Fq864c_kEH3ZBe8mJ0PA@mail.gmail.com' \
    --to=mcgrof@do-not-panic.com \
    --cc=aaron@logicdatasystems.net \
    --cc=backports@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.