From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <491C689E.4050208@domain.hid> Date: Thu, 13 Nov 2008 18:49:18 +0100 From: Philippe Gerum MIME-Version: 1.0 References: <223a70540811122148o73ae3d2ex1689b5d03f77f825@domain.hid> <491C5B24.60202@domain.hid> In-Reply-To: <491C5B24.60202@domain.hid> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai-help] Problem compiling patched kernel: multiple definitions of mcount Reply-To: rpm@xenomai.org List-Id: Help regarding installation and common use of Xenomai List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: James Doebbler , xenomai@xenomai.org Jan Kiszka wrote: > James Doebbler wrote: >> Hello, >> I am trying to patch and install a kernel using Xenomai (on Ubuntu >> 8.10). I am using a vanilla linux-2.6.27 kernel and the latest >> xenomai version (2.4.6.1). I had some earlier problems that I >> resolved by using the latest adeos patch (now I see that has been >> fixed in 2.4.6.1), but I've been running into another problem. I get >> an error when compiling due to multiple definitions of mcount in the >> entry_32.S and mcount_32.S files. I looked at the code and decided >> that disabling function tracing (CONFIG_FTRACE) in the kernel config >> would eliminate the kernel function tracing and the ipipe function >> tracing from stepping on each others' toes. The kernel seems to be >> compiling okay now (still in progress). I just wanted to ask if this >> is a bug or expected, and if the action I took was appropriate. Do I >> lose anything by disabling kernel function tracing? > > OK, that experience confirms my first glance on the latest patch /wrt > FTRACE integration: unfinished. Not quite. Not addressed would be more appropriate. The solution will be using the FTRACE > mcount functions for the ipipe tracer - should be feasible, except for > dynamic FRTRACE, ie. the thing that killed puppies and e1000 NICs. :) > > Hope I'll find some time to look into this, but I can't promise when. > For now, if you want FTRACE (probably not, when you don't know it yet), > disable CONFIG_IPIPE_TRACE. > > Jan > -- Philippe.