build failure with current linus tree

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.