Re: What is the reason for "section type conflict"?

2008-02-03 Thread Mulyadi Santosa
Hi... On 2/3/08, Peter Teoh <[EMAIL PROTECTED]> wrote: > May be I can help to lower down the learning curve on this part a little bit: Thanks man, I greatly appreciate your help! > > 1. what u said, is about correct. What happens is that GCC > supports a "section" feature - take a look at "s

Re: What is the reason for "section type conflict"?

2008-02-03 Thread Peter Teoh
May be I can help to lower down the learning curve on this part a little bit: On Feb 3, 2008 10:57 AM, Mulyadi Santosa <[EMAIL PROTECTED]> wrote: > Hi all... > > On Feb 2, 2008 1:27 PM, Li Zefan <[EMAIL PROTECTED]> wrote: > > No, the comment is correct. I just made a mistake... > > > > __initdata(

Re: What is the reason for "section type conflict"?

2008-02-02 Thread Mulyadi Santosa
Hi all... On Feb 2, 2008 1:27 PM, Li Zefan <[EMAIL PROTECTED]> wrote: > No, the comment is correct. I just made a mistake... > > __initdata(and __devinidata etc..) can't be mixed with const, because > otherwise > the compiler will generate .init.data sections both with and without the > writeable

Re: What is the reason for "section type conflict"?

2008-02-01 Thread Li Zefan
Peter Teoh wrote: > Further to my earlier statement that either init.h is wrong, or the source > codes are not cleanup, my personal guess is that init.h is not correct (this > line - "Also note, that this data cannot be "const".") This is because > these __data can be either constant or non-c

Re: What is the reason for "section type conflict"?

2008-02-01 Thread Peter Teoh
Further to my earlier statement that either init.h is wrong, or the source codes are not cleanup, my personal guess is that init.h is not correct (this line - "Also note, that this data cannot be "const".") This is because these __data can be either constant or non-constant, and can also be o

Re: What is the reason for "section type conflict"?

2008-02-01 Thread Peter Teoh
Thank you very much for your posting.I shall try..but let me comment further On Feb 2, 2008 1:33 PM, Li Zefan <[EMAIL PROTECTED]> wrote: > > sounds like symbol name's conflict? maybe it happens during linking > > stage..that is a spesific name is assigned to two ELF section. Just a >

Re: What is the reason for "section type conflict"?

2008-02-01 Thread Li Zefan
Mulyadi Santosa wrote: > Hi... > > Just trying to offer idea... > On 2/1/08, Peter Teoh <[EMAIL PROTECTED]> wrote: >> I was puzzled today, as several of machines all compiled the latest git >> pulled kernel with the following errors: >> >>CHK include/linux/version.h >>CHK include/l

Re: What is the reason for "section type conflict"?

2008-02-01 Thread Mulyadi Santosa
Hi... Just trying to offer idea... On 2/1/08, Peter Teoh <[EMAIL PROTECTED]> wrote: > I was puzzled today, as several of machines all compiled the latest git > pulled kernel with the following errors: > >CHK include/linux/version.h >CHK include/linux/utsrelease.h >CALLscrip

What is the reason for "section type conflict"?

2008-01-31 Thread Peter Teoh
I was puzzled today, as several of machines all compiled the latest git pulled kernel with the following errors: CHK include/linux/version.h CHK include/linux/utsrelease.h CALLscripts/checksyscalls.sh CHK include/linux/compile.h CC [M] drivers/net/sis190.o drivers/net/si