linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Christian Zigotzky <chzigotzky@xenosoft.de>
To: linuxppc-dev@lists.ozlabs.org,
	"kvm-ppc@vger.kernel.org" <kvm-ppc@vger.kernel.org>
Subject: Re: arch/powerpc/kvm/trace.h:9:0: error: "TRACE_INCLUDE_PATH" redefined
Date: Wed, 31 Oct 2018 11:09:37 +0100	[thread overview]
Message-ID: <a999fed3-ad83-ae96-0639-0640053cad55@xenosoft.de> (raw)
In-Reply-To: <009777be-1025-a309-2804-c76cd00d3947@xenosoft.de>

Hello,

I compiled the latest Git kernel today. The error 'TRACE_INCLUDE_PATH 
redefined' still exist.

Cheers,
Christian


On 29 October 2018 at 11:22AM, Christian Zigotzky wrote:
> Hello,
>
> The latest Git kernel doesn't compile currently because of the 
> following error:
>
>
> christian@christian-virtual-machine:~/Downloads/a$ env LANG=C make 
> CROSS_COMPILE=powerpc-linux-gnu- ARCH=powerpc uImage
>   CALL    scripts/checksyscalls.sh
>   CHK     include/generated/compile.h
>   CALL    arch/powerpc/kernel/systbl_chk.sh
>   CC      arch/powerpc/kvm/powerpc.o
> In file included from arch/powerpc/kvm/powerpc.c:51:0:
> arch/powerpc/kvm/trace.h:9:0: error: "TRACE_INCLUDE_PATH" redefined 
> [-Werror]
>  #define TRACE_INCLUDE_PATH .
>  ^
> In file included from arch/powerpc/kvm/../mm/mmu_decl.h:25:0,
>                  from arch/powerpc/kvm/powerpc.c:48:
> ./arch/powerpc/include/asm/trace.h:224:0: note: this is the location 
> of the previous definition
>  #define TRACE_INCLUDE_PATH asm
>  ^
> cc1: all warnings being treated as errors
> scripts/Makefile.build:305: recipe for target 
> 'arch/powerpc/kvm/powerpc.o' failed
> make[2]: *** [arch/powerpc/kvm/powerpc.o] Error 1
> scripts/Makefile.build:546: recipe for target 'arch/powerpc/kvm' failed
> make[1]: *** [arch/powerpc/kvm] Error 2
> Makefile:1052: recipe for target 'arch/powerpc' failed
> make: *** [arch/powerpc] Error 2
>
> ---
>
> I deleted the definition of 'TRACE_INCLUDE_PATH' in 
> 'arch/powerpc/kvm/trace.h'. After that the kernel compiled without any 
> problems.
>
> -- Christian
>


  reply	other threads:[~2018-10-31 10:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-28 16:35 NXP P50XX/e5500: SMP doesn't work anymore with the latest Git kernel Christian Zigotzky
2018-10-29  9:56 ` Christian Zigotzky
2018-10-29 10:22   ` arch/powerpc/kvm/trace.h:9:0: error: "TRACE_INCLUDE_PATH" redefined Christian Zigotzky
2018-10-31 10:09     ` Christian Zigotzky [this message]
2018-11-05  7:09       ` Christian Zigotzky
2018-10-29 17:00   ` NXP P50XX/e5500: SMP doesn't work anymore with the latest Git kernel Christian Zigotzky
2018-10-29 18:13     ` LEROY Christophe
2018-10-29 20:12       ` Christian Zigotzky
2018-10-29 23:04         ` Scott Wood
2018-10-30  0:41           ` Christian Zigotzky
2018-10-30  1:42             ` Christian Zigotzky
2018-10-30  1:59               ` Benjamin Herrenschmidt
2018-10-30  7:27                 ` Christian Zigotzky
2018-10-30 15:05                   ` Christian Zigotzky
2018-10-29 22:24     ` Christian Zigotzky
2018-10-31 13:20       ` Michael Ellerman
2018-10-31 13:38         ` Christian Zigotzky
2018-11-07  2:11 ` Scott Wood
2018-11-07  6:46   ` Christian Zigotzky

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=a999fed3-ad83-ae96-0639-0640053cad55@xenosoft.de \
    --to=chzigotzky@xenosoft.de \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).