LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Petr Vandrovec <petr@vmware.com>
To: "Philippe Dhont (Sea-ro)" <philippe.dhont@searo.be>
Cc: linux-kernel@vger.kernel.org
Subject: Re: C header files for vmware
Date: Thu, 01 Feb 2007 23:43:42 -0800 [thread overview]
Message-ID: <45C2EBAE.7070600@vmware.com> (raw)
In-Reply-To: <EB998357DB660742877807C9BD7D251B9BD2E8@SRVR1.searo.local>
Philippe Dhont (Sea-ro) wrote:
> hello,
>
> i downloaded latest kernel 2.6.19.2 and installed it and it works fine.
> Now i am trying to install vmware and it asks the location of the
> directory of the C header files.
> So i pointed it to my download/install directory
> /data/kernel/2.6.19.2/linux-2.6.19.2/include/
>
> and i get the error that the directory of kernel headers does not match
> my running kernel ??
> what am i doing wrong ?
> do i need to download something else ?
Error message most probably also contains additional details...
There may be couple of reasons - one of them may be that your product is
too old to run on 2.6.19.2 kernel without additional changes. You
should discuss these issues on http://www.vmware.com/community/index.jspa.
If you are quite sure that you've built your kernel from these sources,
and you did not run 'make clean' (or make *config) after build kernel,
then you most probably have to download
http://knihovny.cvut.cz/ftp/pub/vmware/vmware-any-any-update107.tar.gz,
untar/ungzip it, run runme.pl from package, and follow directions... It
should work with all released Linux products. If you are using
Workstation 6.0 beta, you should contact VMware beta support.
Petr
prev parent reply other threads:[~2007-02-02 7:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-31 9:48 Philippe Dhont (Sea-ro)
2007-02-02 7:43 ` Petr Vandrovec [this message]
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=45C2EBAE.7070600@vmware.com \
--to=petr@vmware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=philippe.dhont@searo.be \
--subject='Re: C header files for vmware' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).