From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Michael Paesold" Subject: Error compiling with CONFIG_PROFILING (xenoprof) Date: Mon, 10 Apr 2006 11:45:49 +0200 Message-ID: <00a701c65c83$8cb26310$d801a8c0@zaphod> Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="Windows-1252"; reply-type=original Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Xen Devel List-Id: xen-devel@lists.xenproject.org A xen-unstable changeset between 9515:d0d3fef37685 and 9576:050ad9813cdb broke compiling the kernel with CONFIG_PROFILING=y here. (I have not yet tested a later cs.) There were some changesets regarding xenoprof. http://xenbits.xensource.com/xen-unstable.hg?cmd=changelog&rev=xenoprof# Perhaps some of those broke my build. I have disabled CONFIG_PROFILING for now because I don't need it currently, but I thought I'd let you know. Here is the build error: arch/i386/oprofile/xenoprof.c:315: error: unknown field `set_active' specified in initializer arch/i386/oprofile/xenoprof.c:315: warning: initialization from incompatible pointer type make[1]: *** [arch/i386/oprofile/xenoprof.o] Error 1 make: *** [arch/i386/oprofile] Error 2 That is from linux 2.6.16.1 with xen patched into the kernel from "make mkpatches". I can supply the kernel config as well as my kernel source RPM to recreate the problem, if that helps. Best Regards, Michael Paesold