From: Randy Dunlap <randy.dunlap@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for November 13 (auditsc)
Date: Thu, 13 Nov 2008 09:55:01 -0800 [thread overview]
Message-ID: <20081113095501.7d91cd91.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20081113183316.3601c13d.sfr@canb.auug.org.au>
On Thu, 13 Nov 2008 18:33:16 +1100 Stephen Rothwell wrote:
auditsc build fails when
CONFIG_KEYS=y
CONFIG_KEYS_DEBUG_PROC_KEYS=y
CONFIG_SECURITY=y
# CONFIG_SECURITYFS is not set
# CONFIG_SECURITY_NETWORK is not set
# CONFIG_SECURITY_FILE_CAPABILITIES is not set
error is:
auditsc.c:(.text+0x2afaf): undefined reference to `get_vfs_caps_from_disk'
---
~Randy-r5905
next prev parent reply other threads:[~2008-11-13 17:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-13 7:33 linux-next: Tree for November 13 Stephen Rothwell
2008-11-13 9:03 ` Missing CONFIG_IDE_LEGACY definition (Re: linux-next: Tree for November 13) Takashi Iwai
2008-11-13 21:08 ` Bartlomiej Zolnierkiewicz
2008-11-13 17:36 ` linux-next: Tree for November 13 (v4l2 build error) Randy Dunlap
2008-11-13 17:55 ` Randy Dunlap [this message]
2008-11-14 0:31 ` next-20081113: ndefined ureference to `freeze_processes' Alexey Dobriyan
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=20081113095501.7d91cd91.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).