Hello Richard!
Sorry, I saw this post of yours too late to include in my previous
message.
On Mon, Nov 17, 2003 at 03:30:07PM +, Richard Kimber wrote:
On Mon, 17 Nov 2003 08:36:34 +0100
Florian Ernst <[EMAIL PROTECTED]> wrote:
Patches won't be automatically uninstalled, quoting 'man make-kpkg'
Hello Richard!
Hello Kevin (CCed to)!
Regarding instruction from
http://newbiedoc.sourceforge.net/system/kernel-pkg.html
On Mon, Nov 17, 2003 at 01:06:08PM +, Richard Kimber wrote:
On Mon, 17 Nov 2003 08:36:34 +0100
Florian Ernst <[EMAIL PROTECTED]> wrote:
So don't forget to run 'make-kpkg clea
On Mon, 17 Nov 2003 08:36:34 +0100
Florian Ernst <[EMAIL PROTECTED]> wrote:
> Patches won't be automatically uninstalled, quoting 'man make-kpkg':
> |Please note that the patches are UN-installed from the source when you
> |run the clean target. This cleanup can be prevented by setting the
> |env
On Mon, 17 Nov 2003 08:36:34 +0100
Florian Ernst <[EMAIL PROTECTED]> wrote:
> So don't forget to run 'make-kpkg clean' before attempting a
> recompile, which incidentally is just what '5.6. Making the kernel
> image' from above doc recommends.
Hmmn, well that's what I think I was doing.
However,
Hello Richard!
On Sun, Nov 16, 2003 at 06:45:13PM +, Richard Kimber wrote:
http://newbiedoc.sourceforge.net/system/kernel-pkg.html
says that after the kernel is built, make-kpkg reverses the patches you
applied, so that each new build starts with an unpatched source tree.
However, whenever I t
I have been experimenting with the low latency and preempt patches.
http://newbiedoc.sourceforge.net/system/kernel-pkg.html
says that after the kernel is built, make-kpkg reverses the patches you
applied, so that each new build starts with an unpatched source tree.
However, whenever I try to re-b
6 matches
Mail list logo