From: clowncoder <clowncoder@clowncode.net>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Sam Ravnborg <sam@ravnborg.org>,
7eggert@gmx.de,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: New version of ClownToolKit
Date: Thu, 17 Aug 2006 19:04:49 +0200 [thread overview]
Message-ID: <1155834289.3673.21.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.61.0608170945410.16217@yvahk01.tjqt.qr>
Le jeudi 17 août 2006 à 09:47 +0200, Jan Engelhardt a écrit :
> >> > 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.
> >
> >/lib/modules/`uname -r` is the general solution that works for most
> >people and should be at least default. It is certainly better than
> >/usr/src/linux.
> >But yes they better make it override able.
>
> In some outoftree modules of mine, the Makefile reads like this
>
> MODULES_DIR := /lib/modules/$(shell uname -r)
> KSRC_DIR := ${MODULES_DIR}/source
> KOBJ_DIR := ${MODULES_DIR}/build
>
> all: modules
> modules:
> make -C "${KOBJ_DIR}" M="$$PWD";
>
> and one can easily override it by calling `make MODULES_DIR=/foo/bar`
> (instead of just `make`).
>
>
> Jan Engelhardt
Thank you all for all those tips, I will use this last one.
Vincent Perrier
next prev parent reply other threads:[~2006-08-17 17:04 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 ` New version of ClownToolKit Bodo Eggert
2006-08-17 4:42 ` Sam Ravnborg
2006-08-17 7:47 ` Jan Engelhardt
2006-08-17 17:04 ` clowncoder [this message]
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=1155834289.3673.21.camel@localhost.localdomain \
--to=clowncoder@clowncode.net \
--cc=7eggert@gmx.de \
--cc=jengelh@linux01.gwdg.de \
--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