Summary: | app-emulation/vmware-modules-271.1 with kernel 3.14 - .../work/vmblock-only/linux/inode.c:138:32: error: incompatible types when assigning to type ‘kgid_t’ from type ‘int’ | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Harris Landgarten <harrisl> |
Component: | [OLD] Library | Assignee: | Gentoo VMWare Bug Squashers [disabled] <vmware+disabled> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | jrmalaq, m.debruijne, markpariente, sven.koehler |
Priority: | Normal | ||
Version: | 10.1 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
build log
modified ebuild patch in inode.c |
Description
Harris Landgarten
2014-04-02 17:06:53 UTC
1) Please post your `emerge --info' output in a comment. 2) Please attach the entire build log to this bug report. Created attachment 374168 [details]
build log
show failure of vmblock to build
Created attachment 374170 [details]
modified ebuild
ebuild modified for vmci and vsock from kernel and vmci renamed to vmw_vmci
I also commented out all the vmci_only and vsock_only parts of 279 patches also still using all the user patches I posted to get kernel-3.13 to work Do you mean 279.1 instead of 271.1? Comment on attachment 374170 [details]
modified ebuild
--- vmware-modules-279.1.ebuild 2013-11-24 17:40:13.625689177 +0100
+++ - 2014-04-04 17:58:30.536451777 +0200
@@ -38,7 +38,7 @@
VMWARE_GROUP=${VMWARE_GROUP:-vmware}
- VMWARE_MODULE_LIST="vmblock vmci vmmon vmnet vsock"
+ VMWARE_MODULE_LIST="vmblock vmmon vmnet"
VMWARE_MOD_DIR="${PN}-${PVR}"
BUILD_TARGETS="auto-build KERNEL_DIR=${KERNEL_DIR} KBUILD_OUTPUT=${KV_OUT_DIR}"
@@ -75,7 +75,7 @@
linux-mod_src_install
local udevrules="${T}/60-vmware.rules"
cat > "${udevrules}" <<-EOF
- KERNEL=="vmci", GROUP="vmware", MODE=660
+ KERNEL=="vmw_vmci", GROUP="vmware", MODE=660
KERNEL=="vmmon", GROUP="vmware", MODE=660
KERNEL=="vsock", GROUP="vmware", MODE=660
EOF
This seems to be fixed by the new 279.1-r1 ebuild. Simply disable vmci and vsock use flags. the new version is still dying on vblock_only with the same error I posted. Must still need a patch. Also the requirement for VMCI_VSOCKETS = y or m in .config is unnecessary for using gentoo as a host. It is only needed for linux as a guest. From my research, it is very possible the vmblock_only error is being caused by gcc-4.8 considering as an error what was a warning in gcc-4.7 Unfortunately we cannot compile a module with 4.7 and use with a kernel compiled by 4.8 I'm using gcc 4.7 and I did not have problems in building vmblock. should we continue this bug as gcc-4.8 only or start a new bug? Created attachment 375322 [details, diff]
patch in inode.c
I cannot get vmblock to build without this patch. It will still not modprobe with getname error but at least vmware-modules builds and installs. I don't think vmblock is used anymore anyway.
*** This bug has been marked as a duplicate of bug 462666 *** |