Hi James,
After merging the security-testing tree, today's linux-next build
(powerpc ppc64_defconfig) failed like this:
security/Kconfig:144: can't open file "security/apparmor/Kconfig"
Caused by commit 32bd8e5273c0be4189274ab55c4d16862f0dd87d ("AppArmor:
Enable configuring and building of the AppArmor security module"). Looks
like a file was missed.
I have used the security-testing from next-20100729 for today.
--
Cheers,
Stephen Rothwell [email protected]
http://www.canb.auug.org.au/~sfr/
On Fri, 30 Jul 2010, Stephen Rothwell wrote:
> Hi James,
>
> After merging the security-testing tree, today's linux-next build
> (powerpc ppc64_defconfig) failed like this:
>
> security/Kconfig:144: can't open file "security/apparmor/Kconfig"
>
> Caused by commit 32bd8e5273c0be4189274ab55c4d16862f0dd87d ("AppArmor:
> Enable configuring and building of the AppArmor security module"). Looks
> like a file was missed.
I don't know how to use git.
Should be fixed now.
>
--
James Morris
<[email protected]>
Hi James,
On Fri, 30 Jul 2010 13:54:01 +1000 (EST) James Morris <[email protected]> wrote:
>
> I don't know how to use git.
:-)
> Should be fixed now.
Thanks.
--
Cheers,
Stephen Rothwell [email protected]
http://www.canb.auug.org.au/~sfr/
On 07/29/2010 08:54 PM, James Morris wrote:
> On Fri, 30 Jul 2010, Stephen Rothwell wrote:
>
>> Hi James,
>>
>> After merging the security-testing tree, today's linux-next build
>> (powerpc ppc64_defconfig) failed like this:
>>
>> security/Kconfig:144: can't open file "security/apparmor/Kconfig"
>>
>> Caused by commit 32bd8e5273c0be4189274ab55c4d16862f0dd87d ("AppArmor:
>> Enable configuring and building of the AppArmor security module"). Looks
>> like a file was missed.
>
> I don't know how to use git.
>
> Should be fixed now.
>
works for me,
thanks James