 | | | RHEL3 CIFS won 't compile | RHEL3 CIFS won 't compile 2005-09-27 - By Arjan van de Ven
Back
On Mon, 2005-09-26 at 16:32 -0400, Wagner, Chris (GE Trans, Non-GE)
wrote:
> It's not really "touching" the kernel tree. U copy the cifs dir under the
kernel fs dir, where all the other file system code is and patch the config
files so it knows CIFS is there.
> Then u tell it to include that new dir in make menuconfig. CIFS shows up
there and u put an M to tell it to make a module.
there is where you touch the tree by modifying all the carefully laid
out headers in the kernel-source package that are set up for building
external modules.
> That's it, there's no alteration of any existing kernel code.
.c files.. perhaps. But by doing even make menuconfig (and then the next
steps) you modify what is on the fs, esp the headers.
> The CIFS code needs to be in the kernel tree to satisfy the #includes.
that is an absolutely incorrect statement. For includes you need an -I
line in the cflags, in fact you need
-I /lib/modules/`uname -r/build/include
in the makefile for external builds. There is absolutely no requirement
to be patched into a source tree to use the headers. Just about no other
external kernel module does it like this.. and they all need the kernel
headers and kernel inlines to function.
> Now if I do a plain make rather than make modules it successfully compiles a
kernel.
and you've just destroyed all the tricky setup to get external module
building working automagic for different kernel arch/variants..
> Since it works with the raw kernel source, there has to be something changed
by Red Hat to make it not work.
it works with the RH kernel too if you do make mrproper first. That
cleans out the stuff RH does to make external module builds work. It's
just VERY much the wrong thing to do for building an external module.
--
Taroon-list mailing list
Taroon-list@(protected)
https://www.redhat.com/mailman/listinfo/taroon-list
|
|
|