All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
To: Adrian Bunk <bunk@kernel.org>
Cc: rusty@rustcorp.com.au, LKML <linux-kernel@vger.kernel.org>,
	linux-input@vger.kernel.org, Andy Whitcroft <apw@shadowen.org>,
	Balbir Singh <balbir@linux.vnet.ibm.com>,
	Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Subject: Re: [BUILD_FAILURE] 2.6.24-git18 build fails section type conflict psmouse-base
Date: Fri, 08 Feb 2008 18:20:52 +0530	[thread overview]
Message-ID: <47AC502C.70809@linux.vnet.ibm.com> (raw)
In-Reply-To: <20080208104851.GI7198@cs181133002.pp.htv.fi>

Adrian Bunk wrote:
> On Fri, Feb 08, 2008 at 04:02:59PM +0530, Kamalesh Babulal wrote:
>> Hi,
>>
>> The 2.6.24-git18 kernel build fails on the power machine with following message
>>
>> drivers/input/mouse/psmouse-base.c:44: error: __param_proto causes a section type conflict
>> drivers/input/mouse/psmouse-base.c:44: error: __param_proto causes a section type conflict
>> make[3]: *** [drivers/input/mouse/psmouse-base.o] Error 1
>> make[2]: *** [drivers/input/mouse] Error 2
>> make[1]: *** [drivers/input] Error 2
>> make: *** [drivers] Error 2
>>
>> this failure was reported earlier http://lkml.org/lkml/2007/9/22/64
> 
> You need the patch from [1] manually applied (due to changed context) 
> and with " || defined(__powerpc__)" added for getting it compiling.
> 
> @Rusty:
> Can you look at this issue? It's a modules problem on 3 architectures.
> 
> cu
> Adrian
> 
> [1] http://lkml.org/lkml/2007/12/27/29
> 
I tried manually applying the patch and added ||defined(__powerpc__), the above
build failure was resolved but it started failing at another place, 

  CC      kernel/printk.o
kernel/printk.c:568: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘static’
make[1]: *** [kernel/printk.o] Error 1
make: *** [kernel] Error 2


-- 
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
-
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
To: Adrian Bunk <bunk@kernel.org>
Cc: rusty@rustcorp.com.au, LKML <linux-kernel@vger.kernel.org>,
	linux-input@vger.kernel.org, Andy Whitcroft <apw@shadowen.org>,
	Balbir Singh <balbir@linux.vnet.ibm.com>,
	Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Subject: Re: [BUILD_FAILURE] 2.6.24-git18 build fails section type conflict psmouse-base
Date: Fri, 08 Feb 2008 18:20:52 +0530	[thread overview]
Message-ID: <47AC502C.70809@linux.vnet.ibm.com> (raw)
In-Reply-To: <20080208104851.GI7198@cs181133002.pp.htv.fi>

Adrian Bunk wrote:
> On Fri, Feb 08, 2008 at 04:02:59PM +0530, Kamalesh Babulal wrote:
>> Hi,
>>
>> The 2.6.24-git18 kernel build fails on the power machine with following message
>>
>> drivers/input/mouse/psmouse-base.c:44: error: __param_proto causes a section type conflict
>> drivers/input/mouse/psmouse-base.c:44: error: __param_proto causes a section type conflict
>> make[3]: *** [drivers/input/mouse/psmouse-base.o] Error 1
>> make[2]: *** [drivers/input/mouse] Error 2
>> make[1]: *** [drivers/input] Error 2
>> make: *** [drivers] Error 2
>>
>> this failure was reported earlier http://lkml.org/lkml/2007/9/22/64
> 
> You need the patch from [1] manually applied (due to changed context) 
> and with " || defined(__powerpc__)" added for getting it compiling.
> 
> @Rusty:
> Can you look at this issue? It's a modules problem on 3 architectures.
> 
> cu
> Adrian
> 
> [1] http://lkml.org/lkml/2007/12/27/29
> 
I tried manually applying the patch and added ||defined(__powerpc__), the above
build failure was resolved but it started failing at another place, 

  CC      kernel/printk.o
kernel/printk.c:568: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘static’
make[1]: *** [kernel/printk.o] Error 1
make: *** [kernel] Error 2


-- 
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.

  reply	other threads:[~2008-02-08 12:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-08 10:32 [BUILD_FAILURE] 2.6.24-git18 build fails section type conflict psmouse-base Kamalesh Babulal
2008-02-08 10:48 ` Adrian Bunk
2008-02-08 12:50   ` Kamalesh Babulal [this message]
2008-02-08 12:50     ` Kamalesh Babulal
2008-02-08 13:30     ` Adrian Bunk
2008-02-08 13:30       ` Adrian Bunk
2008-02-08 14:23       ` Kamalesh Babulal
2008-02-08 14:23         ` Kamalesh Babulal
2008-02-08 22:25       ` Ivan Kokshaysky
2008-03-03  4:35   ` Rusty Russell
2008-03-03  8:13     ` Adrian Bunk
2008-03-04  2:35       ` Rusty Russell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47AC502C.70809@linux.vnet.ibm.com \
    --to=kamalesh@linux.vnet.ibm.com \
    --cc=apw@shadowen.org \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=bunk@kernel.org \
    --cc=ink@jurassic.park.msu.ru \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.