From: David Howells <dhowells@redhat.com>
To: Jesper Juhl <juhl-lkml@dif.dk>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: security/keys/key.c broken with defconfig
Date: Thu, 24 Mar 2005 11:46:04 +0000 [thread overview]
Message-ID: <24082.1111664764@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0503222223180.2683@dragon.hyggekrogen.localhost>
Jesper Juhl <juhl-lkml@dif.dk> wrote:
> If I just do a 'make defconfig' and then try to build security/keys/ the
> build breaks. Doing 'make allyesconfig' fixes it by defining CONFIG_KEYS
> which makes include/linux/key-ui.h include the full struct key definition.
>
> I've not attempted to fix this yet, but thought I'd at least report it.
>
>
> juhl@dragon:~/download/kernel/linux-2.6.12-rc1-mm1$ make defconfig
> juhl@dragon:~/download/kernel/linux-2.6.12-rc1-mm1$ make security/keys/
Ah. Why would you do that last command at all?
If you look in security/Makefile, you'll see that the security/keys/ directory
is only entered if CONFIG_KEYS is defined; which in your config it isn't.
David
next prev parent reply other threads:[~2005-03-24 11:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-22 21:28 security/keys/key.c broken with defconfig Jesper Juhl
2005-03-23 10:38 ` David Howells
2005-03-23 21:40 ` Jesper Juhl
2005-03-24 11:46 ` David Howells [this message]
2005-03-25 14:09 ` Jesper Juhl
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=24082.1111664764@redhat.com \
--to=dhowells@redhat.com \
--cc=juhl-lkml@dif.dk \
--cc=linux-kernel@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.