build failure with current linus tree

build failure with current linus tree

[JONGMAN HEO]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-8, Size: 503 bytes --]


With current linus git (commit a25a2b84), I got following build error,

arch/x86/kernel/vm86_32.c: In function ??do_sys_vm86??:
arch/x86/kernel/vm86_32.c:340: error: implicit declaration of function ??__audit_syscall_exit??
make[3]: *** [arch/x86/kernel/vm86_32.o] Error 1

I do not have CONFIG_AUDITSYSCALL in my .config.

Regards,
Jongman.
ÿôèº{.nÇ+‰·Ÿ®‰­†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±þG«éÿŠ{ayº\x1dʇڙë,j\a­¢f£¢·hšïêÿ‘êçz_è®\x03(­éšŽŠÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?™¨è­Ú&£ø§~á¶iO•æ¬z·švØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?–I¥

Re: build failure with current linus tree

[Al Viro]

On Wed, Jan 18, 2012 at 01:17:31AM +0000, JONGMAN HEO wrote:
> 
> With current linus git (commit a25a2b84), I got following build error,
> 
> arch/x86/kernel/vm86_32.c: In function ??do_sys_vm86??:
> arch/x86/kernel/vm86_32.c:340: error: implicit declaration of function ??__audit_syscall_exit??
> make[3]: *** [arch/x86/kernel/vm86_32.o] Error 1
> 
> I do not have CONFIG_AUDITSYSCALL in my .config.

Um...  OK, I can reproduce it (32bit allmodconfig with AUDIT=y, AUDITSYSCALL=n)
Crap...  It's "Audit: push audit success and retcode into arch ptrace.h".

Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
---
diff --git a/arch/x86/kernel/vm86_32.c b/arch/x86/kernel/vm86_32.c
index af17e1c..b466cab 100644
--- a/arch/x86/kernel/vm86_32.c
+++ b/arch/x86/kernel/vm86_32.c
@@ -336,8 +336,10 @@ static void do_sys_vm86(struct kernel_vm86_struct *info, struct task_struct *tsk
 		mark_screen_rdonly(tsk->mm);
 
 	/*call __audit_syscall_exit since we do not exit via the normal paths */
+#ifdef CONFIG_AUDITSYSCALL
 	if (unlikely(current->audit_context))
 		__audit_syscall_exit(1, 0);
+#endif
 
 	__asm__ __volatile__(
 		"movl %0,%%esp\n\t"

build failure with current linus tree

[Christoph Hellwig]

Current linus tree fail to build for me for a 64bit powerpc config with:

WARNING: modpost: Found 13 section mismatch(es).
To see full details build your kernel with:
'make CONFIG_DEBUG_SECTION_MISMATCH=y'
mm/built-in.o: In function `.strndup_user':
(.text+0x1401a): undefined reference to `.LCTOC0'
mm/built-in.o: In function `.walk_page_range':
(.text+0x269ae): undefined reference to `.LCTOC0'
fs/built-in.o: In function `.posix_acl_alloc':
(.text+0x5f62a): undefined reference to `.LCTOC0'
fs/built-in.o: In function `.posix_acl_from_xattr':
(.text+0x5feda): undefined reference to `.LCTOC0'
fs/built-in.o: In function `.ext3fs_dirhash':
(.text+0x8e17e): undefined reference to `.LCTOC0'
fs/built-in.o:(.text+0xe844e): more undefined references to `.LCTOC0'
follow
make[2]: *** [.tmp_vmlinux1] Error 1
make[1]: *** [sub-make] Error 2
make: *** [all] Error 2

The config is at http://verein.lst.de/~hch/.config, I'm using gcc 3.4.6.

Re: build failure with current linus tree

[Christoph Hellwig]

On Fri, Sep 05, 2008 at 03:06:18AM +0200, Christoph Hellwig wrote:
> Current linus tree fail to build for me for a 64bit powerpc config with:

This is cause by

commit 7563dc64585324f443f5ac107eb6d89ee813a2d2
Author: Tony Breeds <tony@bakeyournoodle.com>
Date:   Tue Sep 2 16:50:38 2008 +1000

    powerpc: Work around gcc's -fno-omit-frame-pointer bug

Re: build failure with current linus tree

[Chris Friesen]

Christoph Hellwig wrote:
> On Fri, Sep 05, 2008 at 03:06:18AM +0200, Christoph Hellwig wrote:
> 
>>Current linus tree fail to build for me for a 64bit powerpc config with:
> 
> 
> This is cause by
> 
> commit 7563dc64585324f443f5ac107eb6d89ee813a2d2
> Author: Tony Breeds <tony@bakeyournoodle.com>
> Date:   Tue Sep 2 16:50:38 2008 +1000
> 
>     powerpc: Work around gcc's -fno-omit-frame-pointer bug


Is there a proper fix other than simply reverting that commit?

Chris

Re: build failure with current linus tree

[Paul Mackerras]

Chris Friesen writes:

> Is there a proper fix other than simply reverting that commit?

It appears that we have a choice between having CONFIG_FTRACE work
with gcc 4 and not gcc 3 (the current situation), and having
CONFIG_FTRACE work with gcc 3 and not gcc 4 (which is what we would
have if that commit was reverted).

I think more people use gcc 4 than gcc 3 these days, which is why I
haven't reverted that commit.

Paul.