Re: Installing cipe in a different directory|
"Hans Steegers" <J.Steegers,AT,chello,DOT,nl>|
Thu, 3 Jul 2003 09:27:29 +0200|
"Hans Steegers" <steegers,AT,steegers,DOT,nl>|
The locations are 'hard coded'; however you can modify this file.
KVERS is created in the configure script (search for AC_SUBST(KVERS)).
If you want BINDIR to be configurable, adapt the configure.in
script to define, for example, AC_SUBST(BIN_DIR)
and adapt also conf/Makefile-obj.in:
Note that you _must_ install the modules in:
because that is the location the kernel expects to find them.
The modules are specific to the kernel-version. You cannot
use a module compiled for kernel a for another kernel b.
Why would you want another location? Very obscure indeed!
If you need more information on the configure script, read the
From: Christoph Biedl <cbiedl,AT,gmx,DOT,de>
To: cipe-l,AT,inka,DOT,de <cipe-l,AT,inka,DOT,de>
Date: Thursday, July 03, 2003 3:08 AM
Subject: Installing cipe in a different directory
>for some obscure reason I want the cipe module, dæmon etc. installed in
>another directory. './configure --help' suggested that
>--prefix=/somewhere/else should do the trick. However, BINDIR and MODDIR
>in the Makefile show no difference and 'make install' still wants to
>install in /lib/modules etc.
>Is this by intention, or did I oversee something? The ./configure thing
>is still full of mysteries for me.
>Message sent by the cipe-l,AT,inka,DOT,de mailing list.
>Unsubscribe: mail majordomo,AT,inka,DOT,de, "unsubscribe cipe-l" in body
>Other commands available with "help" in body to the same address.
>CIPE info and list archive: