mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Keith Owens <kaos@sgi.com>
To: Srikanth Srinivasan <ssrikanth1@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Error patching linux-2.6.9 with kdb-v4.4-2.6.9-i386-1
Date: Thu, 29 Dec 2005 02:41:33 +1100	[thread overview]
Message-ID: <17955.1135784493@ocs3.ocs.com.au> (raw)
In-Reply-To: Your message of "Wed, 28 Dec 2005 11:55:12 +0530." <ddce9dad0512272225l5fccba3boe2c0fb7d05f626c8@mail.gmail.com>

Srikanth Srinivasan (on Wed, 28 Dec 2005 11:55:12 +0530) wrote:
>Am relatively new to the linux kernel. I have a problem patching the
>linux kernel with the kdb kernel debugger.... Here are the steps i
>followed. Am not sure if i have missed anything... Kindly help me
>out...
>
>1) Untarred the linux-2.6.9 to my home directory
>[srikanth@zeus linux]$ pwd
>/home/srikanth/work/src/linux
>
>2) Copied kdb-v4.4-2.6.9-i386-1 to /home/srikanth/work/src/linux
>
>3) [srikanth@zeus linux]$ patch -p1 < kdb-v4.4-2.6.9-i386-1
>
>4) Ran menuconfig and chose  Built-in Kernel Debugger support from
>Kernel hacking.
>I alos chose KDB modules to be built.in
>
>5) Then when i ran make bzImage i got the error as linux/kdb.h not found

You did not read the README file in ftp://oss.sgi.com/projects/kdb/download/v4.4,
so you forgot to apply the common kdb patch as well.  The KDB README says -

Starting with kdb v2.0 there is a common patch against each kernel which
contains all the architecture independent code plus separate architecture
dependent patches.  Apply the common patch for your kernel plus at least
one architecture dependent patch, the architecture patches activate kdb.

The naming convention for kdb patches is :-

 vx.y    The version of kdb.  x.y is updated as new features are added to kdb.
 -v.p.s  The kernel version that the patch applies to.  's' may include -pre,
         -rc or whatever numbering system the kernel keepers have thought up this
         week.
 -common The common kdb code.  Everybody needs this.
 -i386   Architecture dependent code for i386.
 -ia64   Architecture dependent code for ia64, etc.
 -n      If there are multiple kdb patches against the same kernel version then
         the last number is incremented.

To build kdb for your kernel, apply the common kdb patch which is less
than or equal to the kernel v.p.s, taking the highest value of '-n'
if there is more than one.  Apply the relevant arch dependent patch
with the same value of 'vx.y-v.p.s-', taking the highest value of '-n'
if there is more than one.

For example, to use kdb for i386 on kernel 2.6.6, apply
  kdb-v4.4-2.6.6-common-<n>            (use highest value of <n>)
  kdb-v4.4-2.6.6-i386-<n>              (use highest value of <n>)
in that order.  To use kdb for ia64 with patch 040521 on kernel 2.6.6, apply
  kdb-v4.4-2.6.6-common-<n>            (use highest value of <n>)
  kdb-v4.4-2.6.6-ia64-040521-<n>       (use highest value of <n>)
in that order.

Use patch -p1 for all patches.



  reply	other threads:[~2005-12-28 15:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-28  6:25 Srikanth Srinivasan
2005-12-28 15:41 ` Keith Owens [this message]
2005-12-28 17:43   ` Jesper Juhl

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=17955.1135784493@ocs3.ocs.com.au \
    --to=kaos@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ssrikanth1@gmail.com \
    /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

all inboxes | Powered by JetHome®