From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Petr Vandrovec <vandrove@vc.cvut.cz>, Steve Kieu <haiquy@yahoo.com>
Cc: kernel <linux-kernel@vger.kernel.org>,
Paul Larson <plars@linuxtestproject.org>
Subject: Re: 2.6.3-mjb1 vmware modules compile error..
Date: Sun, 22 Feb 2004 07:49:12 -0800 [thread overview]
Message-ID: <35790000.1077464951@[10.10.2.4]> (raw)
In-Reply-To: <20040222042853.GD7483@vana.vc.cvut.cz>
>> 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
>
Sigh. That's gcov. Paul, any idea why it's doing that?
M.
> 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:
next prev parent reply other threads:[~2004-02-22 15:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-22 0:57 Steve Kieu
2004-02-22 1:13 ` Petr Vandrovec
2004-02-22 3:49 ` Steve Kieu
2004-02-22 4:28 ` Petr Vandrovec
2004-02-22 15:49 ` Martin J. Bligh [this message]
2004-02-22 19:46 ` Petr Vandrovec
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='35790000.1077464951@[10.10.2.4]' \
--to=mbligh@aracnet.com \
--cc=haiquy@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=plars@linuxtestproject.org \
--cc=vandrove@vc.cvut.cz \
/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®