The original vmware-any-any-116.tgz as provided here (modified from some other unknown source as any-any-115) has now just been modified so as to compile on 2.6.25 Linux Kernel. Compilation was successful, except for the last part, when it tried to insmod in my kernel, and init_mm symbol is missing.
Looking at:
./arch/x86/kernel/init_task.c: struct mm_struct init_mm = INIT_MM(init_mm); EXPORT_UNUSED_SYMBOL(init_mm); /* will be removed in 2.6.26 */
SInce EXPORT_UNUSED_SYMBOL() is depending on CONFIG_UNUSED_SYMBOLS being define:
Therefore, the solution is to edit the .config file in the current linux kernel download:
change the following to "y":
# CONFIG_UNUSED_SYMBOLS is not set
And recompile the Linux kernel. After that 117.tgz should proceed successfully.
Please download and test it if u are interested....thanks.
Against kernel 2.6.25 I get problems with vmblock compile:
vmblock-only]# make
Using 2.6.x kernel build system.
make -C /lib/modules/2.6.25-zen1/build/include/.. SUBDIRS=$PWD SRCROOT=
$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.25-zen1'
CC [M] /usr/local/src/vmblock-only/linux/block.o
CC [M] /usr/local/src/vmblock-only/linux/control.o
CC [M] /usr/local/src/vmblock-only/linux/dbllnklst.o
CC [M] /usr/local/src/vmblock-only/linux/dentry.o
/usr/local/src/vmblock-only/linux/dentry.c: In function
'DentryOpRevalidate':
/usr/local/src/vmblock-only/linux/dentry.c:115: error: 'struct
nameidata' has no member named 'dentry'
/usr/local/src/vmblock-only/linux/dentry.c:115: error: 'struct
nameidata' has no member named 'dentry'
/usr/local/src/vmblock-only/linux/dentry.c:116: error: implicit
declaration of function 'path_release'
make[2]: *** [/usr/local/src/vmblock-only/linux/dentry.o] Error 1
make[1]: *** [_module_/usr/local/src/vmblock-only] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.25-zen1'
make: *** [vmblock.ko] Error 2
Ok..same error as yours and greno.....no problem...i made some
progress...vmblock changes is due to path_release() removed (replaced
by path_put()) and then the dentry error have been patch
as .path.dentry......as nameidata has a subfield called path now...so
let me try again....
> Against kernel 2.6.25 I get problems with vmblock compile:
> vmblock-only]# make
> Using 2.6.x kernel build system.
> make -C /lib/modules/2.6.25-zen1/build/include/.. SUBDIRS=$PWD SRCROOT=
> $PWD/. modules
> make[1]: Entering directory `/usr/src/linux-2.6.25-zen1'
> CC [M] /usr/local/src/vmblock-only/linux/block.o
> CC [M] /usr/local/src/vmblock-only/linux/control.o
> CC [M] /usr/local/src/vmblock-only/linux/dbllnklst.o
> CC [M] /usr/local/src/vmblock-only/linux/dentry.o
> /usr/local/src/vmblock-only/linux/dentry.c: In function
> 'DentryOpRevalidate':
> /usr/local/src/vmblock-only/linux/dentry.c:115: error: 'struct
> nameidata' has no member named 'dentry'
> /usr/local/src/vmblock-only/linux/dentry.c:115: error: 'struct
> nameidata' has no member named 'dentry'
> /usr/local/src/vmblock-only/linux/dentry.c:116: error: implicit
> declaration of function 'path_release'
> make[2]: *** [/usr/local/src/vmblock-only/linux/dentry.o] Error 1
> make[1]: *** [_module_/usr/local/src/vmblock-only] Error 2
> make[1]: Leaving directory `/usr/src/linux-2.6.25-zen1'
> make: *** [vmblock.ko] Error 2
After the change, here is the output of compilation (starting from
runme.pl, and remember to compile after booting up into the new kernel
- 2.6.25 in my case here, as the any-any patch will autodetect this -
different color demarcate the different zones of compilation):
/root/download/vmware/vmware-any-any-update117/vmware-any-any-update115>./runme.pl
Updating /usr/bin/vmware ... No patch needed/available
Updating /usr/bin/vmnet-bridge ... No patch needed/available
Updating /usr/lib/vmware/bin/vmware-vmx ... No patch needed/available
Updating /usr/lib/vmware/bin-debug/vmware-vmx ... No patch
needed/available
VMware modules in "/usr/lib/vmware/modules/source" has been updated.
Before running VMware for the first time after update, you need to
configure it
for your running kernel by invoking the following command:
"/usr/bin/vmware-config.pl". Do you want this script to invoke the
command for
you now? [yes]
Making sure services for VMware Workstation are stopped.
Stopping VMware services:
Virtual machine monitor [ OK ]
Blocking file system: [ OK ]
Bridged networking on /dev/vmnet0 [ OK ]
Host network detection [ OK ]
DHCP server on /dev/vmnet1 [ OK ]
Host-only networking on /dev/vmnet1 [ OK ]
DHCP server on /dev/vmnet8 [ OK ]
NAT service on /dev/vmnet8 [ OK ]
Host-only networking on /dev/vmnet8 [ OK ]
Virtual ethernet [ OK ]
Configuring fallback GTK+ 2.4 libraries.
In which directory do you want to install the theme icons?
[/usr/share/icons]
What directory contains your desktop menu entry files? These files have
a
.desktop file extension. [/usr/share/applications]
In which directory do you want to install the application's icon?
[/usr/share/pixmaps]
Trying to find a suitable vmmon module for your running kernel.
None of the pre-built vmmon modules for VMware Workstation is suitable
for your
running kernel. Do you want this program to try to build the vmmon
module for
your system (you need to have a C compiler installed on your system)?
[yes]
Using compiler "/usr/bin/gcc". Use environment variable CC to override.
What is the
location of the directory of C header files that match your running
kernel? [/lib/modules/2.6.25/build/include]
Extracting the sources of the vmmon module.
Building the vmmon module.
Unknown VMware Workstation 6.0.2 build 59824 detected. Building for
Workstation 6.0.0.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config1/vmmon-only'
make -C /lib/modules/2.6.25/build/include/.. SUBDIRS=$PWD
SRCROOT=$PWD/. modules
make[1]: Entering directory `/mnt/sdc2/download/linux-2.6_latest'
CC [M] /tmp/vmware-config1/vmmon-only/linux/driver.o
CC [M] /tmp/vmware-config1/vmmon-only/linux/driverLog.o
CC [M] /tmp/vmware-config1/vmmon-only/linux/hostif.o
CC [M] /tmp/vmware-config1/vmmon-only/common/comport.o
CC [M] /tmp/vmware-config1/vmmon-only/common/cpuid.o
CC [M] /tmp/vmware-config1/vmmon-only/common/hash.o
CC [M] /tmp/vmware-config1/vmmon-only/common/memtrack.o
CC [M] /tmp/vmware-config1/vmmon-only/common/phystrack.o
CC [M] /tmp/vmware-config1/vmmon-only/common/task.o
cc1plus: warning: command line option
"-Werror-implicit-function-declaration" is valid for C/ObjC but not for
C++
cc1plus: warning: command line option "-Wdeclaration-after-statement"
is valid for C/ObjC but not for C++
cc1plus: warning: command line option "-Wno-pointer-sign" is valid for
C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid
for Ada/C/ObjC but not for C++
cc1plus: warning: command line option "-ffreestanding" is valid for
C/ObjC but not for C++
/tmp/vmware-config1/vmmon-only/common/task_compat.h: In function ‘int
Vmx86_RunVM(VMCrossPage*, VMDriver*) [with VMCrossPage =
VMCrossPageV321]’:
/tmp/vmware-config1/vmmon-only/common/task_compat.h:2491: warning:
‘sysenterState.SysenterStateV45::rsp’ is used uninitialized in this
function
/tmp/vmware-config1/vmmon-only/common/task_compat.h:2492: warning:
‘sysenterState.SysenterStateV45::rip’ is used uninitialized in this
function
/tmp/vmware-config1/vmmon-only/common/task_compat.h:3028: warning:
‘sysenterState.SysenterStateV45::validEIP’ may be used uninitialized in
this function
/tmp/vmware-config1/vmmon-only/common/task_compat.h:3028: warning:
‘sysenterState.SysenterStateV45::cs’ may be used uninitialized in this
function
/tmp/vmware-config1/vmmon-only/common/task_compat.h: In function ‘int
Vmx86_RunVM(VMCrossPage*, VMDriver*) [with VMCrossPage =
VMCrossPageV3]’:
/tmp/vmware-config1/vmmon-only/common/task_compat.h:2491: warning:
‘sysenterState.SysenterStateV45::rsp’ is used uninitialized in this
function
/tmp/vmware-config1/vmmon-only/common/task_compat.h:2492: warning:
‘sysenterState.SysenterStateV45::rip’ is used uninitialized in this
function
/tmp/vmware-config1/vmmon-only/common/task_compat.h:3028: warning:
‘sysenterState.SysenterStateV45::validEIP’ may be used uninitialized in
this function
/tmp/vmware-config1/vmmon-only/common/task_compat.h:3028: warning:
‘sysenterState.SysenterStateV45::cs’ may be used uninitialized in this
function
/tmp/vmware-config1/vmmon-only/common/task_compat.h: In function ‘int
Vmx86_RunVM(VMCrossPage*, VMDriver*) [with VMCrossPage =
VMCrossPageGSX1]’:
/tmp/vmware-config1/vmmon-only/common/task_compat.h:2491: warning:
‘sysenterState.SysenterStateV45::rsp’ is used uninitialized in this
function
/tmp/vmware-config1/vmmon-only/common/task_compat.h:2492: warning:
‘sysenterState.SysenterStateV45::rip’ is used uninitialized in this
function
/tmp/vmware-config1/vmmon-only/common/task_compat.h:3028: warning:
‘sysenterState.SysenterStateV45::validEIP’ may be used uninitialized in
this function
/tmp/vmware-config1/vmmon-only/common/task_compat.h:3028: warning:
‘sysenterState.SysenterStateV45::cs’ may be used uninitialized in this
function
/tmp/vmware-config1/vmmon-only/common/task_compat.h: In function ‘int
Vmx86_RunVM(VMCrossPage*, VMDriver*) [with VMCrossPage =
VMCrossPageV2]’:
/tmp/vmware-config1/vmmon-only/common/task_compat.h:2491: warning:
‘sysenterState.SysenterStateV45::rsp’ is used uninitialized in this
function
/tmp/vmware-config1/vmmon-only/common/task_compat.h:2492: warning:
‘sysenterState.SysenterStateV45::rip’ is used uninitialized in this
function
/tmp/vmware-config1/vmmon-only/common/task_compat.h:3028: warning:
...
ok...no problem anymore....after I reboot the machine....next is the
network compilation issues:
On May 8, 1:29 pm, greno <gr...@verizon.net> wrote:
> I think config is unlinking /dev/parport0 and some process may be
> watching and recreate it before the mknod.
/tmp/vmware-config1/vmmon-only/common/task_compat.h:2666: warning:
‘sysenterState.SysenterStateV45::rip’ may be used uninitialized in
this function
CC [M] /tmp/vmware-config1/vmmon-only/common/vmciContext.o
CC [M] /tmp/vmware-config1/vmmon-only/common/vmciDatagram.o
CC [M] /tmp/vmware-config1/vmmon-only/common/vmciDriver.o
CC [M] /tmp/vmware-config1/vmmon-only/common/vmciDs.o
CC [M] /tmp/vmware-config1/vmmon-only/common/vmciGroup.o
CC [M] /tmp/vmware-config1/vmmon-only/common/vmciHashtable.o
CC [M] /tmp/vmware-config1/vmmon-only/common/vmciProcess.o
CC [M] /tmp/vmware-config1/vmmon-only/common/vmciResource.o
CC [M] /tmp/vmware-config1/vmmon-only/common/vmciSharedMem.o
CC [M] /tmp/vmware-config1/vmmon-only/common/vmx86.o
CC [M] /tmp/vmware-config1/vmmon-only/vmcore/compat.o
CC [M] /tmp/vmware-config1/vmmon-only/vmcore/moduleloop.o
LD [M] /tmp/vmware-config1/vmmon-only/vmmon.o
Building modules, stage 2.
MODPOST 1 modules
WARNING: modpost: module vmmon.ko uses symbol 'init_mm' marked UNUSED
CC /tmp/vmware-config1/vmmon-only/vmmon.mod.o
LD [M] /tmp/vmware-config1/vmmon-only/vmmon.ko
make[1]: Leaving directory `/mnt/sdc2/download/linux-2.6_latest'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/tmp/vmware-config1/vmmon-only'
The module loads perfectly in the running kernel.
This program previously created the file /dev/vmmon, and was about to
remove
it. Somebody else apparently did it already.
Trying to find a suitable vmblock module for your running kernel.
None of the pre-built vmblock modules for VMware Workstation is
suitable for
your running kernel. Do you want this program to try to build the
vmblock
module for your system (you need to have a C compiler installed on
your
system)? [yes]
Extracting the sources of the vmblock module.
Building the vmblock module.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config1/vmblock-only'
make -C /lib/modules/2.6.25/build/include/.. SUBDIRS=$PWD SRCROOT=
$PWD/. modules
make[1]: Entering directory `/mnt/sdc2/download/linux-2.6_latest'
CC [M] /tmp/vmware-config1/vmblock-only/linux/block.o
CC [M] /tmp/vmware-config1/vmblock-only/linux/control.o
CC [M] /tmp/vmware-config1/vmblock-only/linux/dbllnklst.o
CC [M] /tmp/vmware-config1/vmblock-only/linux/dentry.o
CC [M] /tmp/vmware-config1/vmblock-only/linux/file.o
CC [M] /tmp/vmware-config1/vmblock-only/linux/filesystem.o
CC [M] /tmp/vmware-config1/vmblock-only/linux/inode.o
CC [M] /tmp/vmware-config1/vmblock-only/linux/module.o
CC [M] /tmp/vmware-config1/vmblock-only/linux/stubs.o
CC [M] /tmp/vmware-config1/vmblock-only/linux/super.o
LD [M] /tmp/vmware-config1/vmblock-only/vmblock.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-config1/vmblock-only/vmblock.mod.o
LD [M] /tmp/vmware-config1/vmblock-only/vmblock.ko
make[1]: Leaving directory `/mnt/sdc2/download/linux-2.6_latest'
cp -f vmblock.ko ./../vmblock.o
make: Leaving directory `/tmp/vmware-config1/vmblock-only'
The module loads perfectly in the running kernel.
You have already setup networking.
Would you like to skip networking setup and keep your old settings as
they are?
(yes/no) [yes]
Trying to find a suitable vmnet module for your running kernel.
None of the pre-built vmnet modules for VMware Workstation is suitable
for your
running kernel. Do you want this program to try to build the vmnet
module for
your system (you need to have a C compiler installed on your system)?
[yes]
Extracting the sources of the vmnet module.
Building the vmnet module.
Unknown VMware Workstation 6.0.2 build 59824 detected. Building for
Workstation 6.0.0.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config1/vmnet-only'
make -C /lib/modules/2.6.25/build/include/.. SUBDIRS=$PWD SRCROOT=
$PWD/. modules
make[1]: Entering directory `/mnt/sdc2/download/linux-2.6_latest'
CC [M] /tmp/vmware-config1/vmnet-only/driver.o
CC [M] /tmp/vmware-config1/vmnet-only/hub.o
CC [M] /tmp/vmware-config1/vmnet-only/userif.o
CC [M] /tmp/vmware-config1/vmnet-only/netif.o
CC [M] /tmp/vmware-config1/vmnet-only/bridge.o
/tmp/vmware-config1/vmnet-only/bridge.c: In function
‘VNetBridgeDevCompatible’:
/tmp/vmware-config1/vmnet-only/bridge.c:278: error: ‘struct
net_device’ has no member named ‘nd_net’
/tmp/vmware-config1/vmnet-only/bridge.c:278: error: ‘struct
net_device’ has no member named ‘nd_net’
/tmp/vmware-config1/vmnet-only/bridge.c: In function ‘VNetBridgeUp’:
/tmp/vmware-config1/vmnet-only/bridge.c:905: error: ‘struct
net_device’ has no member named ‘nd_net’
/tmp/vmware-config1/vmnet-only/bridge.c:943: error: ‘struct
net_device’ has no member named ‘nd_net’
/tmp/vmware-config1/vmnet-only/bridge.c:949: error: implicit
declaration of function ‘sock_valbool_flag’
make[2]: *** [/tmp/vmware-config1/vmnet-only/bridge.o] Error 1
make[1]: *** [_module_/tmp/vmware-config1/vmnet-only] Error 2
make[1]: Leaving directory `/mnt/sdc2/download/linux-2.6_latest'
make: *** [vmnet.ko] Error 2
make: Leaving directory `/tmp/vmware-config1/vmnet-only'
Unable to build the vmnet module.
I am really confused. The nd_net in 2.6.25 is embedded inside
CONFIG_NET_NS (look at net_device inside include/linux/netdevice.h).
But .config don't allow me to specify CONFIG_NET_NS=y, due to some
dependancies issues. (specifying =y always result is its deletion
after I do a "make oldconfig").
Can you confirm that the Japanese patches fix the network issue?
using the sources from any-to-any 117 i apply the all four diffs.
after applying all four diffs i am getting these errors:
make[1]: Entering directory `/usr/src/kernels/2.6.25-14.fc9.x86_64'
CC [M] /tmp/vmware-config22/vmnet-only/driver.o
CC [M] /tmp/vmware-config22/vmnet-only/hub.o
CC [M] /tmp/vmware-config22/vmnet-only/userif.o
CC [M] /tmp/vmware-config22/vmnet-only/netif.o
CC [M] /tmp/vmware-config22/vmnet-only/bridge.o
/tmp/vmware-config22/vmnet-only/bridge.c: In function ‘VNetBridgeUp’:
/tmp/vmware-config22/vmnet-only/bridge.c:913: error: implicit
declaration of function ‘dev_net’
/tmp/vmware-config22/vmnet-only/bridge.c:913: warning: passing
argument 1 of ‘__dev_get_by_name’ makes pointer from integer without a
cast
/tmp/vmware-config22/vmnet-only/bridge.c:951: warning: passing
argument 1 of ‘sk_alloc’ makes pointer from integer without a cast
make[2]: *** [/tmp/vmware-config22/vmnet-only/bridge.o] Error 1
make[1]: *** [_module_/tmp/vmware-config22/vmnet-only] Error 2
make[1]: Leaving directory `/usr/src/kernels/2.6.25-14.fc9.x86_64'
make: *** [vmnet.ko] Error 2
make: Leaving directory `/tmp/vmware-config22/vmnet-only'
Unable to build the vmnet module.
> Can you confirm that the Japanese patches fix the network issue?
> using the sources from any-to-any 117 i apply the all four diffs.
> after applying all four diffs i am getting these errors:
> make[1]: Entering directory `/usr/src/kernels/2.6.25-14.fc9.x86_64'
> CC [M] /tmp/vmware-config22/vmnet-only/driver.o
> CC [M] /tmp/vmware-config22/vmnet-only/hub.o
> CC [M] /tmp/vmware-config22/vmnet-only/userif.o
> CC [M] /tmp/vmware-config22/vmnet-only/netif.o
> CC [M] /tmp/vmware-config22/vmnet-only/bridge.o
> /tmp/vmware-config22/vmnet-only/bridge.c: In function ‘VNetBridgeUp’:
> /tmp/vmware-config22/vmnet-only/bridge.c:913: error: implicit
> declaration of function ‘dev_net’
"implicit declaration" means compiler cannot find out where the
function is declared....so it implicitly deduced it....
my kernel source is in include/linux/netdevice.h declared as static
inline.
> /tmp/vmware-config22/vmnet-only/bridge.c:913: warning: passing
> argument 1 of ‘__dev_get_by_name’ makes pointer from integer without a
> cast
> /tmp/vmware-config22/vmnet-only/bridge.c:951: warning: passing
> argument 1 of ‘sk_alloc’ makes pointer from integer without a cast
> make[2]: *** [/tmp/vmware-config22/vmnet-only/bridge.o] Error 1
By applying the patches listed by ole...@gmail.com above to 116 i have
VMware Workstation 6.0.2 i386 running on Fedora 9. It compiled all
modules without fatal errors.
Here i probe it! :-) Hope it helps you to fix an 117
> > Can you confirm that the Japanese patches fix the network issue?
> > using the sources from any-to-any 117 i apply the all four diffs.
> > after applying all four diffs i am getting these errors:
> > make[1]: Entering directory `/usr/src/kernels/2.6.25-14.fc9.x86_64'
> > CC [M] /tmp/vmware-config22/vmnet-only/driver.o
> > CC [M] /tmp/vmware-config22/vmnet-only/hub.o
> > CC [M] /tmp/vmware-config22/vmnet-only/userif.o
> > CC [M] /tmp/vmware-config22/vmnet-only/netif.o
> > CC [M] /tmp/vmware-config22/vmnet-only/bridge.o
> > /tmp/vmware-config22/vmnet-only/bridge.c: In function ‘VNetBridgeUp’:
> > /tmp/vmware-config22/vmnet-only/bridge.c:913: error: implicit
> > declaration of function ‘dev_net’
> "implicit declaration" means compiler cannot find out where the
> function is declared....so it implicitly deduced it....
> my kernel source is in include/linux/netdevice.h declared as static
> inline.
> > /tmp/vmware-config22/vmnet-only/bridge.c:913: warning: passing
> > argument 1 of ‘__dev_get_by_name’ makes pointer from integer without a
> > cast
> > /tmp/vmware-config22/vmnet-only/bridge.c:951: warning: passing
> > argument 1 of ‘sk_alloc’ makes pointer from integer without a cast
> > make[2]: *** [/tmp/vmware-config22/vmnet-only/bridge.o] Error 1
> By applying the patches listed by ole...@gmail.com above to 116 i have
> VMware Workstation 6.0.2 i386 running on Fedora 9. It compiled all
> modules without fatal errors.
> Here i probe it! :-) Hope it helps you to fix an 117
> > > Can you confirm that the Japanese patches fix the network issue?
> > > using the sources from any-to-any 117 i apply the all four diffs.
> > > after applying all four diffs i am getting these errors:
> > > make[1]: Entering directory `/usr/src/kernels/2.6.25-14.fc9.x86_64'
> > > CC [M] /tmp/vmware-config22/vmnet-only/driver.o
> > > CC [M] /tmp/vmware-config22/vmnet-only/hub.o
> > > CC [M] /tmp/vmware-config22/vmnet-only/userif.o
> > > CC [M] /tmp/vmware-config22/vmnet-only/netif.o
> > > CC [M] /tmp/vmware-config22/vmnet-only/bridge.o
> > > /tmp/vmware-config22/vmnet-only/bridge.c: In function ‘VNetBridgeUp’:
> > > /tmp/vmware-config22/vmnet-only/bridge.c:913: error: implicit
> > > declaration of function ‘dev_net’
> > "implicit declaration" means compiler cannot find out where the
> > function is declared....so it implicitly deduced it....
> > my kernel source is in include/linux/netdevice.h declared as static
> > inline.
> > > /tmp/vmware-config22/vmnet-only/bridge.c:913: warning: passing
> > > argument 1 of ‘__dev_get_by_name’ makes pointer from integer without a
> > > cast
> > > /tmp/vmware-config22/vmnet-only/bridge.c:951: warning: passing
> > > argument 1 of ‘sk_alloc’ makes pointer from integer without a cast
> > > make[2]: *** [/tmp/vmware-config22/vmnet-only/bridge.o] Error 1
> On 11 mayo, 17:31, josemaX <jose...@gmail.com> wrote:
> > Hello,
> > By applying the patches listed by ole...@gmail.com above to 116 i have
> > VMware Workstation 6.0.2 i386 running on Fedora 9. It compiled all
> > modules without fatal errors.
> > Here i probe it! :-) Hope it helps you to fix an 117
> > > > Can you confirm that the Japanese patches fix the network issue?
> > > > using the sources from any-to-any 117 i apply the all four diffs.
> > > > after applying all four diffs i am getting these errors:
> > > > make[1]: Entering directory `/usr/src/kernels/2.6.25-14.fc9.x86_64'
> > > > CC [M] /tmp/vmware-config22/vmnet-only/driver.o
> > > > CC [M] /tmp/vmware-config22/vmnet-only/hub.o
> > > > CC [M] /tmp/vmware-config22/vmnet-only/userif.o
> > > > CC [M] /tmp/vmware-config22/vmnet-only/netif.o
> > > > CC [M] /tmp/vmware-config22/vmnet-only/bridge.o
> > > > /tmp/vmware-config22/vmnet-only/bridge.c: In function ‘VNetBridgeUp’:
> > > > /tmp/vmware-config22/vmnet-only/bridge.c:913: error: implicit
> > > > declaration of function ‘dev_net’
> > > "implicit declaration" means compiler cannot find out where the
> > > function is declared....so it implicitly deduced it....
> > > my kernel source is in include/linux/netdevice.h declared as static
> > > inline.
> > > > /tmp/vmware-config22/vmnet-only/bridge.c:913: warning: passing
> > > > argument 1 of ‘__dev_get_by_name’ makes pointer from integer without a
> > > > cast
> > > > /tmp/vmware-config22/vmnet-only/bridge.c:951: warning: passing
> > > > argument 1 of ‘sk_alloc’ makes pointer from integer without a cast
> > > > make[2]: *** [/tmp/vmware-config22/vmnet-only/bridge.o] Error 1
> On 11 mayo, 17:31, josemaX <jose...@gmail.com> wrote:
> > Hello,
> > By applying the patches listed by ole...@gmail.com above to 116 i have
> > VMware Workstation 6.0.2 i386 running on Fedora 9. It compiled all
> > modules without fatal errors.
> > Here i probe it! :-) Hope it helps you to fix an 117
> > > > Can you confirm that the Japanese patches fix the network issue?
> > > > using the sources from any-to-any 117 i apply the all four diffs.
> > > > after applying all four diffs i am getting these errors:
> > > > make[1]: Entering directory `/usr/src/kernels/2.6.25-14.fc9.x86_64'
> > > > CC [M] /tmp/vmware-config22/vmnet-only/driver.o
> > > > CC [M] /tmp/vmware-config22/vmnet-only/hub.o
> > > > CC [M] /tmp/vmware-config22/vmnet-only/userif.o
> > > > CC [M] /tmp/vmware-config22/vmnet-only/netif.o
> > > > CC [M] /tmp/vmware-config22/vmnet-only/bridge.o
> > > > /tmp/vmware-config22/vmnet-only/bridge.c: In function ‘VNetBridgeUp’:
> > > > /tmp/vmware-config22/vmnet-only/bridge.c:913: error: implicit
> > > > declaration of function ‘dev_net’
> > > "implicit declaration" means compiler cannot find out where the
> > > function is declared....so it implicitly deduced it....
> > > my kernel source is in include/linux/netdevice.h declared as static
> > > inline.
> > > > /tmp/vmware-config22/vmnet-only/bridge.c:913: warning: passing
> > > > argument 1 of ‘__dev_get_by_name’ makes pointer from integer without a
> > > > cast
> > > > /tmp/vmware-config22/vmnet-only/bridge.c:951: warning: passing
> > > > argument 1 of ‘sk_alloc’ makes pointer from integer without a cast
> > > > make[2]: *** [/tmp/vmware-config22/vmnet-only/bridge.o] Error 1
On Sun, Jul 20, 2008 at 6:48 AM, maxima2k <ryh...@gmail.com> wrote: > Where you able to this resolved? I am struggling with the same exact > situation.
|
