[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <49F8232B.4090007@in.ibm.com>
Date: Wed, 29 Apr 2009 15:21:39 +0530
From: Sachin Sant <sachinp@...ibm.com>
To: Heiko Carstens <heiko.carstens@...ibm.com>,
Ingo Molnar <mingo@...e.hu>
CC: Steven Rostedt <rostedt@...dmis.org>,
Frédéric Weisbecker
<fweisbec@...il.com>, linux-s390@...r.kernel.org,
linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: Next April 24: [S390] allmodconfig build failure (trace/events)
Heiko Carstens wrote:
> On Fri, 24 Apr 2009 09:25:33 +0200
> Ingo Molnar <mingo@...e.hu> wrote:
>
>
>> * Sachin Sant <sachinp@...ibm.com> wrote:
>>
>>
>>> Today's next tree build(s390 allmodconfig) failed with
>>>
>>> kernel/built-in.o: In function `trace_softirq_entry'
>>> include/trace/events/irq.h:42: undefined reference to
>>> `'
>>> include/trace/events/irq.h:42: undefined reference to
>>> `__tracepoint_softirq_entry'
>>> kernel/built-in.o: In function `trace_softirq_exit':
>>> include/trace/events/irq.h:48: undefined reference to
>>> `__tracepoint_softirq_exit'
>>> include/trace/events/irq.h:48: undefined reference to
>>> `__tracepoint_softirq_exit'
>>>
>> Hm, that's weird - s390 does not build kernel/softirq.o? Hm, it does
>> - softirq.o is an obj-y object.
>>
>
> s390 does build kernel/softirq.o. However it's anything but obvious to
> me how the tracepoint infrastructure works. Too many #ifdefs, #define's
> and #undefine's...
>
> I would expect that struct __tracepoint_softirq_entry somehow gets
> defined via one of the TRACE_FORMAT macros, no?
Today's next tree also has this failure. Any solution for this problem ?
Thanks
-Sachin
--
---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------
--
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