public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bodo Eggert <7eggert@elstempel.de>
To: Sam Ravnborg <sam@ravnborg.org>,
	clowncoder <clowncoder@clowncode.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: New version of ClownToolKit
Date: Thu, 17 Aug 2006 01:15:43 +0200	[thread overview]
Message-ID: <E1GDUcG-00016M-Nu@be1.lrz> (raw)
In-Reply-To: 6KyCM-1w7-1@gated-at.bofh.it

Sam Ravnborg <sam@ravnborg.org> wrote:

> A small nitpick about the way ou build the ekrnel module:
> 
> In mk_and_insmod you can replace:
> make -C /usr/src/linux SUBDIRS=$PWD modules
> with
> LIBDIR=/lib/modules/`uname -r`
> make -C $LIBDIR/source O=$LIBDIR/build SUBDIRS=`pwd` modules
> 
> For a normal kernel installation this will do the right thing.
> source points to the kernel source and build point to the output
> directory (they are often equal but not always).

Please don't tell module authors to unconditionally use `uname -r`.
I frequently build kernels for differentd hosts, and if I don't, I'll
certainly compile the needed modules before installing the kernel.
Therefore /lib/modules/`uname -r` is most certainly the completely
wrong place to look for the kernel source.
-- 
Ich danke GMX dafür, die Verwendung meiner Adressen mittels per SPF
verbreiteten Lügen zu sabotieren.

http://david.woodhou.se/why-not-spf.html

       reply	other threads:[~2006-08-16 23:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6Kxx5-7PT-7@gated-at.bofh.it>
     [not found] ` <6KyCM-1w7-1@gated-at.bofh.it>
2006-08-16 23:15   ` Bodo Eggert [this message]
2006-08-17  4:42     ` New version of ClownToolKit Sam Ravnborg
2006-08-17  7:47       ` Jan Engelhardt
2006-08-17 17:04         ` clowncoder
2006-08-16 17:33 clowncoder
2006-08-16 18:48 ` Sam Ravnborg
2006-08-17  7:45   ` Jan Engelhardt

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=E1GDUcG-00016M-Nu@be1.lrz \
    --to=7eggert@elstempel.de \
    --cc=7eggert@gmx.de \
    --cc=clowncoder@clowncode.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.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