[ltt-dev] multiple definition of `trace_clock' problem on linux-2.6.30-rc5

[Steve Langstaff]

> From: Mathieu Desnoyers [mailto:compudj at krystal.dyndns.org]
> Sent: 28 May 2009 15:52
> To: Steve Langstaff
> Cc: ltt-dev at lists.casi.polymtl.ca
> Subject: Re: [ltt-dev] multiple definition of `trace_clock' problem on
> linux-2.6.30-rc5
> 
> * Steve Langstaff (steve.langstaff at pebblebay.com) wrote:
> > Hi All.
> >
> > I am having the following trouble compiling kernel linux-2.6.30-rc5
> when
> > patched with patch-2.6.30-rc5-lttng-0.136 and wondered if this is a
> known
> > problem...

> > kernel/trace/trace-clock.o:(.bss+0x0): multiple definition of
> `trace_clock'
> > kernel/trace/trace_clock.o:trace_clock.c:(.text+0x0): first defined
> here
> > arm-linux-ld: Warning: size of symbol `trace_clock' changed from 8 in
> > kernel/trace/trace_clock.o to 4 in kernel/trace/trace-clock.o
> > arm-linux-ld: Warning: type of symbol `trace_clock' changed from 2 to
> 1 in
> > kernel/trace/trace-clock.o
> > make[2]: *** [kernel/trace/built-in.o] Error 1
> > make[1]: *** [kernel/trace] Error 2
> > make: *** [kernel] Error 2


> Hrm, yes. This is caused by ftrace. But given they are in mainline and
> LTTng isn't, the LTTng trace clock identifier will have to move.
> 
> Can you try the following patch ?

Thanks for the patch Mathieu, that got me compiling again.