Bug 18408 – Modules for VMWare2.02 would not install on RH 7.0

Bug 18408 - Modules for VMWare2.02 would not install on RH 7.0

Summary:	Modules for VMWare2.02 would not install on RH 7.0

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	kernel (Show other bugs)
Sub Component:
Version:	7.0
Hardware:	i686 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Michael K. Johnson
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2000-10-05 11:31 EDT by Frank Bures
Modified:	2008-05-01 11:37 EDT (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2000-10-09 13:22:50 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Frank Bures 2000-10-05 11:31:46 EDT

While running /usr/bin/vmware-config.pl on RH7.0 smp machine with a standard RH 7.0 installation, the following error message is 
generated:

The directory of kernel headers (version 2.4.0-0.26) does not match your running
kernel (version 2.2.16-22smp). Consequently, even if the compilation of the     
module was successful, the module would not load into the running kernel.       

It is therefore impossible to install the VMware.

Comment 1 Arjan van de Ven 2000-10-05 12:09:35 EDT

This is a bug in VMWARE, as VMWARE incorrectly uses the headers in
/usr/include/linux
instead of /usr/src/linux/include to compile the VMWare kernel modules. Adding 
-I/usr/src/linux/include to the VMWare modules Makefile should fix this. 

Please also report this bug to VMWare support. This is a long-standing bug.

Comment 2 Michael J. Saletnik 2000-10-09 13:22:48 EDT

How can that be - they're supposed to be the same thing -
 /usr/include/linux is a symlink to ../src/linux/include/linux
You're never supposed to directly #include from /usr/src/linux;
VMWare is doing the right thing.

Comment 3 Alan Cox 2000-10-09 20:04:39 EDT

Vmware is wrong. /usr/include/ uses the kernel interface headers that match the
glibc not the
kernel. The kernel/library interface is glibc's business. The fact this worked
before is luck.

Note You need to log in before you can comment on or make changes to this bug.