All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Wessel <jason.wessel@windriver.com>
To: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	amitkale@linsyssoft.com, trini@kernel.crashing.org
Subject: Re: 2.6.23-rc6-mm1 powerpc - kgdb is broken
Date: Wed, 19 Sep 2007 13:53:01 -0500	[thread overview]
Message-ID: <46F1700D.2020205@windriver.com> (raw)
In-Reply-To: <46F114D2.40809@linux.vnet.ibm.com>

I am not exactly sure how to fix this...

Another git tree is overriding the patch to include/asm-powerpc/kgdb.h
in the -mm tree.   The patches as I provide them against 2.6.23-rc6 for
KGDB work correctly for ppc/powerpc in 32 and 64 bit modes and compile
correctly.

At issue is that someone merged a bogus copy of asm-ppc/kgdb.h from the
git tree in -mm that is called: git-powerpc.patch.

Jason.

Kamalesh Babulal wrote:
> Hi Andrew,
>
> The kgdb seems to be broken on the powerpc, while compiling with
> allyesconfig.
>
>   LD [M]  drivers/isdn/hysdn/hysdn.o
>   CC [M]  drivers/net/kgdboe.o
>   CC [M]  drivers/scsi/scsi_wait_scan.o
> In file included from include/linux/kgdb.h:22,
>                  from drivers/net/kgdboe.c:28:
> include/asm/kgdb.h:34: error: 'debugger' redeclared as different kind of symbol
> include/asm/system.h:85: error: previous definition of 'debugger' was here
> include/asm/kgdb.h:35: error: 'debugger_bpt' redeclared as different kind of symbol
> include/asm/system.h:87: error: previous definition of 'debugger_bpt' was here
> include/asm/kgdb.h:36: error: 'debugger_sstep' redeclared as different kind of symbol
> include/asm/system.h:88: error: previous definition of 'debugger_sstep' was here
> include/asm/kgdb.h:37: error: 'debugger_iabr_match' redeclared as different kind of symbol
> include/asm/system.h:89: error: previous definition of 'debugger_iabr_match' was here
> include/asm/kgdb.h:38: error: 'debugger_dabr_match' redeclared as different kind of symbol
> include/asm/system.h:90: error: previous definition of 'debugger_dabr_match' was here
> include/asm/kgdb.h:39: error: 'debugger_fault_handler' redeclared as different kind of symbol
> include/asm/system.h:91: error: previous definition of 'debugger_fault_handler' was here
> In file included from drivers/net/kgdboe.c:28:
> include/linux/kgdb.h:69: error: 'BREAK_INSTR_SIZE' undeclared here (not in a function)
> make[3]: *** [drivers/net/kgdboe.o] Error 1
> make[2]: *** [drivers/net] Error 2
> make[2]: *** Waiting for unfinished jobs....
> make[1]: *** [drivers] Error 2
> make: *** [modules] Error 2
>
>   


  reply	other threads:[~2007-09-19 18:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-19 12:23 2.6.23-rc6-mm1 powerpc - kgdb is broken Kamalesh Babulal
2007-09-19 18:53 ` Jason Wessel [this message]
2007-09-19 19:36   ` Andrew Morton
2007-09-20  5:23     ` Paul Mackerras
2007-09-20  5:53       ` Andrew Morton
2007-09-20  7:38       ` Christoph Hellwig
2007-09-28 10:37         ` Kamalesh Babulal
2007-09-28 10:47           ` Thomas Gleixner
2007-09-28 12:28             ` 2.6.23-rc6-mm1 powerpc - kgdb is broken [Resending PATCH] Kamalesh Babulal

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=46F1700D.2020205@windriver.com \
    --to=jason.wessel@windriver.com \
    --cc=akpm@linux-foundation.org \
    --cc=amitkale@linsyssoft.com \
    --cc=kamalesh@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trini@kernel.crashing.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.