[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1185358083.4996.6.camel@localhost.localdomain>
Date: Wed, 25 Jul 2007 18:08:03 +0800
From: chengong <g.chen@...escale.com>
To: Sam Ravnborg <sam@...nborg.org>
Cc: Kumar Gala <galak@...nel.crashing.org>, linuxppc-dev@...abs.org,
linux-kernel@...r.kernel.org, Jeff Garzik <jeff@...zik.org>,
netdev@...r.kernel.org
Subject: Re: modpost warning question
On Wed, 2007-07-25 at 09:27 +0200, Sam Ravnborg wrote:
> On Wed, Jul 25, 2007 at 02:14:12AM -0500, Kumar Gala wrote:
> > I'm seeing the following warning:
> >
> > WARNING: vmlinux.o(.init.text+0x1acdc): Section mismatch: reference to
> > .exit.text:gfar_mdio_exit (between 'gfar_init' and 'gfar_mdio_init')
> >
> > I don't understand why its not ok to access .exit.text from .init.text
>
> Several architectures discards .exit.text in the final linker
> script (arch/$(ARCH)/kernel/vmlinux.lds.S
>
> So any references to .exit.text will when a module is build-in result
> in a linker error because ld will flag it as an error when we reference
> a symbol in a discarded section.
But why? Just make kernel size smaller?
>
> For the popular architectures (i386,x86_64) we discard .exit.text at
> runtime so here we do not see the error from ld (sadly).
>>From which version? On my machine I have seen the same problem when
building i386 target with the version 2.6.21.
>
> Sam
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@...abs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists