Re: 2.6.3-mjb1 vmware modules compile error..

From: Petr Vandrovec
Date: Sat Feb 21 2004 - 23:30:32 EST


On Sun, Feb 22, 2004 at 02:49:38PM +1100, Steve Kieu wrote:
>
> Hi,
>
>
> bash-2.05b# make
> Unable to find VMware installation database. Using
> 'vmware'.
> Building for VMware Workstation 3.2.0.
> Using 2.6.x kernel build system.
> make -C /lib/modules/2.6.1-mm4/build/include/..
> SUBDIRS=$PWD SRCROOT=$PWD/. modu
> les
> make[1]: Entering directory `/vol/hdb5/linux'
> *** Warning: Overriding SUBDIRS on the command line
> can cause
> *** inconsistencies
> make[2]: `arch/i386/kernel/asm-offsets.s' is up to
> date.
> CHK include/asm-i386/asm_offsets.h
> CC [M] /root/vmmon-6/linux/driver.o
> driver.c:7:27: driver-config.h: No such file or
> directory

> I just extract the vmmon.tar from the vmware-any---
> package and run make in the source dir. It works with
> all vanila kernels and mm tree, but not with mjb1.

WTF? It prepends $(TOPDIR)/ to all include paths. I have
no idea what is this supposed to do, but I can guarantee
that I'm not going to support that kernel.
Petr Vandrovec


diff -purN -X /home/mbligh/.diff.exclude 000-virgin/scripts/Makefile.build 790-irq_vector/scripts/Makefile.build
--- 000-virgin/scripts/Makefile.build 2003-10-14 15:50:40.000000000 -0700
+++ 790-irq_vector/scripts/Makefile.build 2004-02-18 16:23:03.000000000 -0800
@@ -128,7 +128,16 @@ cmd_cc_i_c = $(CPP) $(c_flags) -
quiet_cmd_cc_o_c = CC $(quiet_modtag) $@

ifndef CONFIG_MODVERSIONS
-cmd_cc_o_c = $(CC) $(c_flags) -c -o $@ $<
+new1_c_flags = $(c_flags:-I%=-I$(TOPDIR)/%)
+new2_c_flags = $(new1_c_flags:-Wp%=)
+PWD = $(TOPDIR)
+
+quiet_cmd_cc_o_c = CC $(quiet_modtag) $@
+cmd_cc_o_c = $(CC) $(c_flags) -E -o $@ $< \
+ && cd $(dir $<) \
+ && $(CC) $(new2_c_flags) -c -o $(notdir $@) $(notdir $<) \
+ && cd $(TOPDIR)
+#cmd_cc_o_c = $(CC) $(c_flags) -c -o $@ $<

else
# When module versioning is enabled the following steps are executed:

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/