On Fri, Jan 18, 2008 at 02:22:42PM +0100, Sam Ravnborg wrote:
>On Fri, Jan 18, 2008 at 08:51:44PM +0800, WANG Cong wrote:
>> On Fri, Jan 18, 2008 at 01:46:27PM +0100, Sam Ravnborg wrote:
>> >On Fri, Jan 18, 2008 at 08:29:17PM +0800, WANG Cong wrote:
>> >> On Fri, Jan 18, 2008 at 01:18:27PM +0100, Toralf Förster wrote:
>> >> >Hello,
>> >> >
>> >> >the build with the attached .config was successful however I got during 
>> >> >make :
>> >> >  AS      .tmp_kallsyms2.o
>> >> >  LD      vmlinux.o
>> >> >  MODPOST vmlinux.o
>> >> >WARNING: vmlinux.o(.text.head+0x247): Section mismatch: reference to 
>> >> >.init.text.1:start_kernel (between 'is386' and 'check_x87')
>> >> >  CHK     include/linux/version.h
>> >> >  HOSTCC  scripts/unifdef
>> >> >  MKDIR   include
>> >> >
>> >> >Does it help / make sense to report such warning ?
>> >> >
>> >> >The build was made with :
>> >> >$> make mrproper && make rndconfig && <tweak config file> && make 
>> >> >oldconfig && make
>> >> >
>> >> >Here's the config:
>> >> 
>> >> Thanks. You have reported this. ;)
>> >> 
>> >> I can't solve this problem. Let's Cc Rusty and Sam to see
>> >> if they can solve this.
>> >
>> >modpost gets confused by the section named ".init.text.1" - the additional 
>> >'.1'
>> >is unexpected.
>> >
>> >Following untested patch should fix it.
>> >
>> 
>> Still has the same problem. ;(
>Could you please doublecheck that you applied the patch and modpost is rebuilt.
>If you continue to see the problem could you send me the config (off-list) and
>I will fix it.

Sure thing.

I got something like this:

  HOSTCC  scripts/mod/modpost.o
  HOSTLD  scripts/mod/modpost

So modpost was rebuilt. And I am quite sure I had applied your patch.

My .config is just the one provided by Toralf. If you need me to send
you again, please tell me.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to