Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Will Moore <will.moore@beran.co.uk>
To: buildroot@busybox.net
Subject: [Buildroot] How to incorporate linux kernel patch correctly
Date: Wed, 22 Apr 2009 16:32:54 +0100	[thread overview]
Message-ID: <066C96D66D20444B9FCC41A62BC2BA97@AP366> (raw)
In-Reply-To: <87zle8oiz4.fsf@macbook.be.48ers.dk>

Is there a buildroot user mail list where I might get assistance but not
disturb the developers?  I looked but could not find so, apologies ...

I am using buildroot 2009.02 release and have successfully produced a linux
kernel, rootfs and cross tool kit for a 486 SX PC104 PC104 CPU.  I need to
apply a patch to the 2.6.24 kernel and have initially used a kernel .config
provided by the PC104 manufacturer which I did by manually applying the
patch in project_build_486/uclibc/linux-2.6.24 and copying the kernel
.config there too.  I can see that there is support in the buildroot menu
Kernel->Patches for Additional patch to apply (from $(DL_DIR)) but when I
put the kernel patch file in /dl and entered the filename in the menu
configuration buildroot complained:

Make: *** No rule to make target 'patch-2.4.6-DMP', needed by
'../project_build_i486/uclibc/linux-2.6.24/.patched'.  Stop.

Your assistance to better understand how to get buildroot to automatically
apply a kernel patch would be appreciated.

Regards


Will

  reply	other threads:[~2009-04-22 15:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-26  9:10 [Buildroot] [PATCH] Add host-libglib2 dependencie to dbus-glib Jean-Christian de Rivaz
2009-04-22 12:48 ` Steffen Schulz
2009-04-22 12:52   ` Sven Neumann
2009-04-22 13:17     ` Steffen Schulz
2009-04-22 13:58       ` Sven Neumann
2009-04-22 14:15     ` Jean-Christian de Rivaz
2009-04-22 14:27       ` Sven Neumann
2009-04-22 14:34       ` Peter Korsgaard
2009-04-22 15:32         ` Will Moore [this message]
2009-04-23  8:24         ` Jean-Christian de Rivaz
2009-04-23  8:40           ` Peter Korsgaard
2009-04-23  8:57             ` Jean-Christian de Rivaz

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=066C96D66D20444B9FCC41A62BC2BA97@AP366 \
    --to=will.moore@beran.co.uk \
    --cc=buildroot@busybox.net \
    /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