On Sun, Feb 17, 2008 at 09:38:55PM +0100, Geert Uytterhoeven wrote:
> On Sun, 17 Feb 2008, Sam Ravnborg wrote:
> > On Sun, Feb 17, 2008 at 01:31:14PM +0100, Geert Uytterhoeven wrote:
> > > On Sun, 17 Feb 2008, Geert Uytterhoeven wrote:
> > > > On m68k (CONFIG_SPARSEMEM is not set), I get:
> > > >
On Sun, Feb 17, 2008 at 09:38:55PM +0100, Geert Uytterhoeven wrote:
On Sun, 17 Feb 2008, Sam Ravnborg wrote:
On Sun, Feb 17, 2008 at 01:31:14PM +0100, Geert Uytterhoeven wrote:
On Sun, 17 Feb 2008, Geert Uytterhoeven wrote:
On m68k (CONFIG_SPARSEMEM is not set), I get:
>
> > I would need a config where the mismatch triggers for one
> > of the more popular architectures (as in where I have a toolchain).
>
> That was with plain m68k defconfig.
>
> > I could not reproduce it with x86 64bit - not even with
> > -fno-inline-functions
>
> If it helps, my
On Sun, 17 Feb 2008, Sam Ravnborg wrote:
> On Sun, Feb 17, 2008 at 01:31:14PM +0100, Geert Uytterhoeven wrote:
> > On Sun, 17 Feb 2008, Geert Uytterhoeven wrote:
> > > On m68k (CONFIG_SPARSEMEM is not set), I get:
> > >
> > > WARNING: vmlinux.o(.meminit.text+0x36c): Section mismatch in
> > >
On Sun, Feb 17, 2008 at 01:31:14PM +0100, Geert Uytterhoeven wrote:
> On Sun, 17 Feb 2008, Geert Uytterhoeven wrote:
> > On m68k (CONFIG_SPARSEMEM is not set), I get:
> >
> > WARNING: vmlinux.o(.meminit.text+0x36c): Section mismatch in reference
> > from the function free_area_init_core() to
On Sun, 17 Feb 2008, Geert Uytterhoeven wrote:
> On m68k (CONFIG_SPARSEMEM is not set), I get:
>
> WARNING: vmlinux.o(.meminit.text+0x36c): Section mismatch in reference
> from the function free_area_init_core() to the function
> .init.text:setup_usemap()
> The function __meminit
On m68k (CONFIG_SPARSEMEM is not set), I get:
WARNING: vmlinux.o(.meminit.text+0x36c): Section mismatch in reference from
the function free_area_init_core() to the function .init.text:setup_usemap()
The function __meminit free_area_init_core() references
a function __init
On Sun, 17 Feb 2008, Geert Uytterhoeven wrote:
On m68k (CONFIG_SPARSEMEM is not set), I get:
WARNING: vmlinux.o(.meminit.text+0x36c): Section mismatch in reference
from the function free_area_init_core() to the function
.init.text:setup_usemap()
The function __meminit
On m68k (CONFIG_SPARSEMEM is not set), I get:
WARNING: vmlinux.o(.meminit.text+0x36c): Section mismatch in reference from
the function free_area_init_core() to the function .init.text:setup_usemap()
The function __meminit free_area_init_core() references
a function __init
On Sun, Feb 17, 2008 at 01:31:14PM +0100, Geert Uytterhoeven wrote:
On Sun, 17 Feb 2008, Geert Uytterhoeven wrote:
On m68k (CONFIG_SPARSEMEM is not set), I get:
WARNING: vmlinux.o(.meminit.text+0x36c): Section mismatch in reference
from the function free_area_init_core() to the
On Sun, 17 Feb 2008, Sam Ravnborg wrote:
On Sun, Feb 17, 2008 at 01:31:14PM +0100, Geert Uytterhoeven wrote:
On Sun, 17 Feb 2008, Geert Uytterhoeven wrote:
On m68k (CONFIG_SPARSEMEM is not set), I get:
WARNING: vmlinux.o(.meminit.text+0x36c): Section mismatch in
reference from
I would need a config where the mismatch triggers for one
of the more popular architectures (as in where I have a toolchain).
That was with plain m68k defconfig.
I could not reproduce it with x86 64bit - not even with
-fno-inline-functions
If it helps, my cross-compiler is gcc
12 matches
Mail list logo