[NBLUG/talk] vmplayer configuration question
Jack Smith
jack.delbert at gmail.com
Sat May 5 12:01:38 PDT 2007
I installed the kernel-dev package and got the right headers, but the config
program was unable to build the vmmon module. I get
Extracting the sources of the vmmon module.
Building the vmmon module.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config1/vmmon-only'
make -C /usr/src/kernels/2.6.18-1.2239.fc5-i686/include/.. SUBDIRS=$PWD
SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.18- 1.2239.fc5-i686'
CC [M] /tmp/vmware-config1/vmmon-only/linux/driver.o
In file included from /tmp/vmware-config1/vmmon-only/linux/driver.c:11:
include/linux/kernel.h:115: warning: conflicting types for built-in function
'snprintf'
include/linux/kernel.h:117: warning: conflicting types for built-in function
'vsnprintf'
In file included from include/linux/string.h:21,
from include/linux/bitmap.h:8,
from include/linux/cpumask.h:86,
from include/asm/processor.h:22,
from include/asm/thread_info.h:16,
from include/linux/thread_info.h:21,
from include/linux/preempt.h:9,
from include/linux/spinlock.h:49,
from include/linux/capability.h:45,
from include/linux/sched.h:44,
from include/linux/module.h:9,
from /tmp/vmware-config1/vmmon-only/linux/driver.c:12:
include/asm/string.h:44: warning: conflicting types for built-in function
'strncpy'
include/asm/string.h:80: warning: conflicting types for built-in function
'strncat'
include/asm/string.h:125: warning: conflicting types for built-in function
'strncmp'
include/asm/string.h:189: warning: conflicting types for built-in function
'strlen'
include/asm/string.h:326: warning: conflicting types for built-in function
'memmove'
In file included from include/linux/bitmap.h:8,
from include/linux/cpumask.h:86,
from include/asm/processor.h:22,
from include/asm/thread_info.h:16,
from include/linux/thread_info.h:21,
from include/linux/preempt.h:9,
from include/linux/spinlock.h:49,
from include/linux/capability.h:45,
from include/linux/sched.h:44,
from include/linux/module.h:9,
from /tmp/vmware-config1/vmmon-only/linux/driver.c:12:
include/linux/string.h:76: warning: conflicting types for built-in function
'strspn'
include/linux/string.h:79: warning: conflicting types for built-in function
'strcspn'
include/linux/string.h:95: warning: conflicting types for built-in function
'__builtin_memcmp'
In file included from include/asm/elf.h:52,
from include/linux/elf.h:7,
from include/linux/module.h:16,
from /tmp/vmware-config1/vmmon-only/linux/driver.c:12:
include/asm/desc.h: In function '__set_tss_desc':
include/asm/desc.h:69: warning: cast from pointer to integer of different
size
include/asm/desc.h: In function 'set_ldt_desc':
include/asm/desc.h:77: warning: cast from pointer to integer of different
size
In file included from include/linux/irq.h:22,
from include/asm/hardirq.h:5,
from include/linux/hardirq.h:7,
from include/linux/interrupt.h:11,
from /tmp/vmware-config1/vmmon-only/linux/driver.c:20:
include/asm/irq.h:15:25: error: irq_vectors.h: No such file or directory
In file included from include/asm/hardirq.h:5,
from include/linux/hardirq.h:7,
from include/linux/interrupt.h:11,
from /tmp/vmware-config1/vmmon-only/linux/driver.c:20:
include/linux/irq.h: At top level:
include/linux/irq.h:169: error: 'NR_IRQS' undeclared here (not in a
function)
In file included from include/linux/irq.h:182,
from include/asm/hardirq.h:5,
from include/linux/hardirq.h:7,
from include/linux/interrupt.h:11,
from /tmp/vmware-config1/vmmon-only/linux/driver.c:20:
include/asm/hw_irq.h:31: error: 'NR_IRQ_VECTORS' undeclared here (not in a
function)
In file included from include/linux/interrupt.h:11,
from /tmp/vmware-config1/vmmon-only/linux/driver.c:20:
include/linux/hardirq.h:35:27: warning: "NR_IRQS" is not defined
In file included from /tmp/vmware-config1/vmmon-only/linux/driver.h:20,
from /tmp/vmware-config1/vmmon-only/linux/driver.c:49:
/tmp/vmware-config1/vmmon-only/./include/compat_wait.h:37:5: warning:
"VMW_HAVE_EPOLL" is not defined
/tmp/vmware-config1/vmmon-only/./include/compat_wait.h:43:5: warning:
"VMW_HAVE_EPOLL" is not defined
In file included from /tmp/vmware-config1/vmmon-only/linux/driver.h:20,
from /tmp/vmware-config1/vmmon-only/linux/driver.c:49:
/tmp/vmware-config1/vmmon-only/./include/compat_wait.h:60: error:
conflicting types for 'poll_initwait'
include/linux/poll.h:62: error: previous declaration of 'poll_initwait' was
here/tmp/vmware-config1/vmmon-only/linux/driver.c:145: warning:
initialization from incompatible pointer type
/tmp/vmware-config1/vmmon-only/linux/driver.c:149: warning: initialization
from incompatible pointer type
make[2]: *** [/tmp/vmware-config1/vmmon-only/linux/driver.o] Error 1
make[1]: *** [_module_/tmp/vmware-config1/vmmon-only] Error 2
make[1]: Leaving directory `/usr/src/kernels/2.6.18-1.2239.fc5-i686'
make: *** [ vmmon.ko] Error 2
make: Leaving directory `/tmp/vmware-config1/vmmon-only'
Unable to build the vmmon module.
For more information on how to troubleshoot module-related problems, please
visit our Web site at " http://www.vmware.com/download/modules/modules.html"
and
" http://www.vmware.com/support/reference/linux/prebuilt_modules_linux.html
".
Execution aborted.
Aaarghh. So doesn't it work in Core 5? Should I upgrade? Build the player
from the tar file instead of using the rpm? Something simple and obvious (I
hope) that I'm missing?
Thanks everybody,
Jack
On 5/5/07, matt <matt at cfxnetworks.com> wrote:
>
> On Saturday 05 May 2007 09:11:26 Jack Smith wrote:
> > OK, looks the the most direct way to get a windows partition running is
> to
> > load vmplayer and create an image at easyvmx.com . Of course, it can't
> be
> > that easy. I installed vmplayer using the .rpm and then ran the
> configure
> > program. A few prompts down, I get the message
> >
> > What is the location of the directory of C header files that match your
> > running
> > kernel? [/usr/src/linux/include]
> >
> > using the default I get
> >
> > The directory of kernel headers (version 2.6.17-prep) does not match
> your
> > running kernel (version 2.6.18-1.2239.fc5 ). Even if the module were to
> > compile
> > successfully, it would not load into the running kernel.
> >
> > So... where do I go to find the right kernel headers?
> >
> > Thanks,
> > Jack
>
> Install the kernel-devel package, and that should get you the right
> headers.
> They'll be located in /usr/src/linux/2.6.18-1.2239.fc5/include.
>
> --
> Salud,
> Matt
> matt at cfxnetworks.com
>
> Your Fortune:
> Well, I'm INVISIBLE AGAIN ... I might as well pay a visit to the LADIES
> ROOM ...
>
> _______________________________________________
> talk mailing list
> talk at nblug.org
> http://nblug.org/cgi-bin/mailman/listinfo/talk
>
--
English doesn't borrow from other languages -- English follows other
languages down dark alleys and takes what it wants.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://nblug.org/pipermail/talk/attachments/20070505/301c303e/attachment.htm
More information about the talk
mailing list