user/sven/linux.git/scripts/Makefile.modinst, branch v2.6.14.2

kbuild: introduce Kbuild.include

2005-07-25T20:10:36Z

Kbuild.include is a placeholder for definitions originally present in both the top-level Makefile and scripts/Makefile.build. There were a slight difference in the filechk definition, so the most videly used version was kept and usr/Makefile was adopted for this syntax. Signed-off-by: Sam Ravnborg ---

kbuild: Install external modules in a path relative to their own path

2005-03-10T23:38:55Z

When an external module is being built in down in a directory structure keep the relative directory when installing the module. Example: fs/ contains a Makefile used to build both modules: obj-y := myfs/ oldfs/ Install directories fs/myfs/myfs.ko => Will be installed in /lib/modules//extra/fs/myfs/ fs/oldfs/oldfs.o => Will be installed in /lib/modules//extra/fs/oldfs/ Signed-off-by: Sam Ravnborg

kbuild: Allow install of external modules to custom path

2004-10-17T01:48:22Z

Currently, a ``make modules_install'' for an external module will install that module into /lib/modules/$(uname -r)/extra. Allow to override this default by specifying INSTALL_MOD_DIR. Signed-off-by: Andreas Gruenbacher Signed-off-by: Sam Ravnborg

kbuild: Fix modules_install

2004-08-31T23:36:26Z

modules_install failed for modules with 'ko' in their name. Fixes this. Signed-off-by: Sam Ravnborg

kbuild: Solaris fixes in various kbuild Makfiles's

2004-08-29T11:32:19Z

Additional Makefile fixes for Solaris 2.8 On Solaris, 'head' doesn't take a -q argument. But we can use 'grep -h' instead, so do that in Makefile.mod{inst,post}. The built-in test to /bin/sh doesn't like 'if ! cmd' syntax, so when determining if we need to do modversion stuff, invert the if/else cases. The built-in test also doesn't understand -ef, so invoke a real version of test which does. Signed-off-by: Tom Rini Signed-off-by: Sam Ravnborg

[PATCH] kbuild: sort modules for modpost and modinst

2004-07-11T02:29:59Z

Process modules in sorted order during modpost and modules install. Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds

[PATCH] kbuild: clean up module install rules

2004-07-11T02:29:48Z

Consolidate rules for installing internal and external modules. Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds

[PATCH] kbuild: Create .tmp_versions when building external modules

2004-04-13T02:21:59Z

From: Sam Ravnborg When building external modules the $PWD/.tmp_versions directory is used. The .tmp_versions directory in the kernel tree cannot be used because this would clutter up the kernel tree especially when more than one external module is being build for the same kernel tree. This patch make sure to create $PWD/.tmp_versions, and to delete it during make clean. It also removes warning about 'messed with SUBDIRS', this is no longer relevant when .tmp_versions is made outside the kernel tree.

[PATCH] Add a MODULE_VERSION macro

2004-02-26T14:51:58Z

From: Rusty Russell The way it works is that the .mod file contains the name of the module (as before), but succeeding lines are the constituent parts (assumed to be .c files, which usually works: if they use MODULE_VERSION in a file for which this isn't true we'll get a warning). As we postprocess modules, we look in the .modinfo section for a "version=", which is placed by the MODULE_VERSION() macro. This will be of form "version=" "\0" [24 chars] "\0". The 24 chars are replaced by the md4 sum of the .c files and any files they #include using '#include "file"' which are found in the current directory. Whitespace is collapsed outside strings, and comments are ignored for purposes of the sum. The result is a .modinfo entry such as version=1.16ac-rustytest B13E9451C4CA3B89577DEFF At the kernel summit, various people asked for a MODULE_VERSION macro to store module strings (for later access through sysfs). A simple md4 is needed to identify changes in modules which, inevitably, do not update the version. It skips whitespace and comments, and includes #includes which are in the same dir. The module versions should be set according to this definition, based on the RPM one, or CVS Revision tags. Violators will be shot. [`:'][`-'] : A (small) unsigned integer which allows you to start versions anew. If not mentioned, it's zero. eg. "2:1.0" is after "1:2.0". : The may contain only alphanumerics. : Like , but inserted for local customizations, eg "rh3" or "rusty1". Comparison of two versions (assuming same epoch): Split each into all-digit and all-alphabetical parts. Compare each one one at a time: digit parts numerically, alphabetical in ASCII order. So 0.10 comes after 0.9.

kbuild: Fix non-verbose make modules_install output

2003-02-17T08:21:08Z