mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Olaf Titz <olaf@bigred.inka.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ANN: LKMB (Linux Kernel Module Builder) version 0.1.16
Date: Sun, 19 Jan 2003 19:22:50 +0100	[thread overview]
Message-ID: <20030119182250.GA1495@mars.ravnborg.org> (raw)
In-Reply-To: <E18aEyl-0006O0-00@bigred.inka.de>

On Sun, Jan 19, 2003 at 01:55:11PM +0100, Olaf Titz wrote:
> 
> It is a bug that Documentation/modules.txt is so outdated that it
> contains little useful information any more.

An updated version that at least describe how to build modules sanely
outside the kernel tree is queued for inclusion[1].

> It is a bug that
> Documentation/kbuild/makefiles.txt is at least a bit outdated.

A totally revised makefiles.txt is queued for inclusion[1].

> It is a bug that the build process outside of the kernel tree changes
> files inside the kernel tree when MODVERSIONS is enabled. (At least
> this was the case last time I checked.) This means the kernel tree
> can't be mounted read-only, or at least you would have to do dirty
> tricks with symlinks.

I have posted 2-3 version of a "separate src-tree" patch.
But due to the existence of such weird things as oprofile and xfs it did
not work in all cases. I symlinked all makefiles, but wanted to avoid
catching the rest of the directories.
I want my queued stuff applied before revisiting this though.
Main usage has been to build kernels based on different configurations,
not to mount src on a read-only media, that's sort of a side-effect.

> It is a bug that the current Makefile can't compile modules in an
> object directory different from the source directory. This means the
> module source tree can't be mounted read-only (again, without
> resorting to symlinks).

make -C path/to/kernel/src SUBDIRS=$PWD modules
So simple when you know the trick. That what I have documented
in modules.txt.


[1] Most of what I have done has been submitted to lkml within the
past month. It can be found at http://linux-sam.bkbits.net in
the kbuild repository, where it is queued for inclusion.

	Sam

  parent reply	other threads:[~2003-01-19 18:13 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-17 12:31 Shlomi Fish
2003-01-17 12:37 ` Shlomi Fish
2003-01-17 13:12 ` David Woodhouse
2003-01-17 17:00   ` Shlomi Fish
2003-01-17 18:00     ` Sam Ravnborg
2003-01-17 18:28       ` Shlomi Fish
2003-01-18 22:37     ` Olaf Titz
2003-01-18 22:55       ` Arjan van de Ven
2003-01-20 20:03         ` Olaf Titz
2003-01-20 21:39           ` Arjan van de Ven
2003-01-21 21:16             ` Olaf Titz
2003-01-21 21:30               ` David Lang
2003-01-21 21:46               ` Sam Ravnborg
2003-01-22 11:21               ` David Woodhouse
2003-01-22 11:18             ` David Woodhouse
2003-01-22 19:16               ` Bill Davidsen
2003-01-22 22:17                 ` David Woodhouse
2003-01-19  0:12       ` John Levon
2003-01-19 12:55         ` Olaf Titz
2003-01-19 13:06           ` Arjan van de Ven
2003-01-20 20:16             ` Olaf Titz
2003-01-19 18:22           ` Sam Ravnborg [this message]
2003-01-20 20:14             ` Olaf Titz
2003-01-20 20:46               ` Sam Ravnborg
2003-01-19 21:17 Paul Zimmerman
2003-01-19 21:24 Paul Zimmerman
2003-01-23  0:20 Hal Duston

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=20030119182250.GA1495@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olaf@bigred.inka.de \
    /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®