Bug#734449: open-vm-tools-dkms: Some modules still fail to compile
On 08.01.14 Jim Barber (jim.bar...@ddihealth.com) wrote: Hi, It's interesting that 3.12 only arrived into unstable for you today. I have had 3.12 on offer for the 'testing' distribution for a few days now, and I installed it onto my 'unstable' boxes on Dec 31st. Is the Debian mirror you use a bit behind perhaps? Not sure what the version 3.12 denotes: hille@sid:~ $ apt-cache policy open-vm-tools-dkms open-vm-tools-dkms: Installed: 2:9.4.0-1280544-1 Candidate: 2:9.4.0-1280544-1 Version table: *** 2:9.4.0-1280544-1 0 500 http://ftp.de.debian.org/debian/ unstable/main i386 Packages 100 /var/lib/dpkg/status H. -- http://www.hilmar-preusse.de.vu/#206401 http://counter.li.org signature.asc Description: Digital signature
Bug#734449: open-vm-tools-dkms: Some modules still fail to compile
Package: open-vm-tools-dkms Version: 2:9.4.0-1280544-1 Severity: important Dear Maintainer, Some modules still do not build. This does not cause a failed installation - Sev important. make.log is attached. Hilmar -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.12-1-686-pae (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages open-vm-tools-dkms depends on: ii dkms 2.2.0.3-1.2 ii make 3.81-8.3 Versions of packages open-vm-tools-dkms recommends: ii open-vm-tools 2:9.4.0-1280544-1 Versions of packages open-vm-tools-dkms suggests: pn open-vm-tools-desktop none -- no debconf information DKMS make.log for open-vm-tools-9.4.0 for kernel 3.12-1-686-pae (i686) Tue 7 Jan 11:08:18 CET 2014 Using 2.6.x kernel build system. make: Entering directory `/var/lib/dkms/open-vm-tools/9.4.0/build/vmblock' make -C /lib/modules/3.12-1-686-pae/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \ MODULEBUILDDIR=/var/lib/dkms/open-vm-tools/9.4.0/build modules make[1]: Entering directory `/usr/src/linux-headers-3.12-1-686-pae' CC [M] /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/block.o CC [M] /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/control.o /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/control.c: In function ‘ExecuteBlockOp’: /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/control.c:286:9: warning: assignment from incompatible pointer type [enabled by default] name = getname(buf); ^ CC [M] /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/dentry.o /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/dentry.c:38:4: warning: initialization from incompatible pointer type [enabled by default] .d_revalidate = DentryOpRevalidate, ^ /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/dentry.c:38:4: warning: (near initialization for ‘LinkDentryOps.d_revalidate’) [enabled by default] /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/dentry.c: In function ‘DentryOpRevalidate’: /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/dentry.c:104:7: warning: passing argument 2 of ‘actualDentry-d_op-d_revalidate’ makes integer from pointer without a cast [enabled by default] return actualDentry-d_op-d_revalidate(actualDentry, nd); ^ /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/dentry.c:104:7: note: expected ‘unsigned int’ but argument is of type ‘struct nameidata *’ CC [M] /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/file.o CC [M] /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/filesystem.o CC [M] /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/inode.o /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/inode.c:49:4: warning: initialization from incompatible pointer type [enabled by default] .lookup = InodeOpLookup, ^ /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/inode.c:49:4: warning: (near initialization for ‘RootInodeOps.lookup’) [enabled by default] /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/inode.c: In function ‘InodeOpLookup’: /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/inode.c:138:32: error: incompatible types when assigning to type ‘kgid_t’ from type ‘int’ inode-i_uid = inode-i_gid = 0; ^ /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/inode.c: In function ‘InodeOpFollowlink’: /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/inode.c:224:4: error: implicit declaration of function ‘vfs_follow_link’ [-Werror=implicit-function-declaration] ret = vfs_follow_link(nd, iinfo-name); ^ cc1: some warnings being treated as errors make[4]: *** [/var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/inode.o] Error 1 make[3]: *** [_module_/var/lib/dkms/open-vm-tools/9.4.0/build/vmblock] Error 2 make[2]: *** [sub-make] Error 2 make[1]: *** [all] Error 2 make[1]: Leaving directory `/usr/src/linux-headers-3.12-1-686-pae' make: *** [vmblock.ko] Error 2 make: Leaving directory `/var/lib/dkms/open-vm-tools/9.4.0/build/vmblock' Using 2.6.x kernel build system. Building vmhgfs without VMCI module symbols. make: Entering directory `/var/lib/dkms/open-vm-tools/9.4.0/build/vmhgfs' make -C /lib/modules/3.12-1-686-pae/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \ MODULEBUILDDIR=/var/lib/dkms/open-vm-tools/9.4.0/build modules make[1]: Entering directory `/usr/src/linux-headers-3.12-1-686-pae' CC [M] /var/lib/dkms/open-vm-tools/9.4.0/build/vmhgfs/backdoor.o In file included from /var/lib/dkms/open-vm-tools/9.4.0/build/vmhgfs/backdoor.h:44:0, from /var/lib/dkms/open-vm-tools/9.4.0/build/vmhgfs/backdoor.c:49: /var/lib/dkms/open-vm-tools/9.4.0/build/vmhgfs/./shared/backdoor_types.h: In function ‘BACKDOOR_STRUCT_SIZES’:
Bug#734449: open-vm-tools-dkms: Some modules still fail to compile
uups, forgot to attach the patch :)
On 07.01.2014 13:30, Bernd Zeimetz wrote:
Hi Hilmar, hi Jim,
could you give the dkms package from
http://devel.recluse.de/~bzed/.publish/2014-01-07-WisBjJ7x0Vg/
a try? If you don't trust random packages from random sources in the
net,
please take the source from unstable and apply the attached patch,
rebuild
it and see if it works.
(I'd give it a try, but there is no amd64 kernel 3.11 in the
repository
at the moment )
Thanks,
Bernd
On 07.01.2014 11:35, Hilmar Preuße wrote:
Package: open-vm-tools-dkms
Version: 2:9.4.0-1280544-1
Severity: important
Dear Maintainer,
Some modules still do not build. This does not cause a failed
installation
- Sev important. make.log is attached.
Hilmar
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.12-1-686-pae (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
(ignored: LC_ALL set to en_GB.UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages open-vm-tools-dkms depends on:
ii dkms 2.2.0.3-1.2
ii make 3.81-8.3
Versions of packages open-vm-tools-dkms recommends:
ii open-vm-tools 2:9.4.0-1280544-1
Versions of packages open-vm-tools-dkms suggests:
pn open-vm-tools-desktop none
-- no debconf information
--
Bernd ZeimetzDebian GNU/Linux Developer
http://bzed.dehttp://www.debian.org
GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435Fcommit 242d45e44c923c5de9fee5a9134ac1f79e1ea50d
Author: Bernd Zeimetz be...@bzed.de
Date: Tue Jan 7 12:46:43 2014 +0100
Pick patch from upstream to build with gcc 4.8
diff --git a/debian/control b/debian/control
index 6298fe1..bc7bfd0 100644
--- a/debian/control
+++ b/debian/control
@@ -3,7 +3,7 @@ Section: admin
Priority: extra
Maintainer: Bernd Zeimetz b...@debian.org
Build-Depends:
- debhelper (= 9), autotools-dev, gcc-4.7, dkms, doxygen, libcunit1-dev,
+ debhelper (= 9), autotools-dev, dkms, doxygen, libcunit1-dev,
libdumbnet-dev, libfuse-dev, libgtk2.0-dev, libgtkmm-2.4-dev,
libicu-dev, libnotify-dev, libpam0g-dev, libprocps0-dev, libx11-dev,
libxinerama-dev, libxss-dev, libxtst-dev
diff --git
a/debian/patches/1a3eb34_Fix-AssertOnCompileFailed-for-GCC-4.8-kernel-3.10
b/debian/patches/1a3eb34_Fix-AssertOnCompileFailed-for-GCC-4.8-kernel-3.10
new file mode 100644
index 000..5adc6b6
--- /dev/null
+++ b/debian/patches/1a3eb34_Fix-AssertOnCompileFailed-for-GCC-4.8-kernel-3.10
@@ -0,0 +1,75 @@
+From 1a3eb34dd0ad5aa3e51d586cf1fcf310c1f4350e Mon Sep 17 00:00:00 2001
+From: VMware, Inc
+Date: Tue, 17 Sep 2013 20:35:40 -0700
+Subject: [PATCH] Fix AssertOnCompileFailed for GCC 4.8 (kernel 3.10+)
+
+GCC 4.8 now includes -Wunused-local-typedefs as part of -Wall. This
+causes it to spew a gazillion warnings when compiling our modules on
+3.10+ kernels. Because it's a typedef we can't use the (void) cast
+trick, so we need to use attributes. This change introduces
+UNUSED_TYPE to vm_basic_types.h and uses it where appropriate to make
+the compiler happy when building our modules.
+
+Signed-off-by: Dmitry Torokhov d...@vmware.com
+---
+ open-vm-tools/lib/include/vm_assert.h | 7 ++-
+ open-vm-tools/lib/include/vm_atomic.h | 5 -
+ open-vm-tools/lib/include/vm_basic_types.h | 5 +
+ 3 files changed, 15 insertions(+), 2 deletions(-)
+
+--- a/lib/include/vm_assert.h
b/lib/include/vm_assert.h
+@@ -358,12 +358,17 @@ void WarningThrottled(uint32 *count, con
+ * The implementation uses both enum and typedef because the typedef alone is
+ * insufficient; gcc allows arrays to be declared with non-constant
expressions
+ * (even in typedefs, where it makes no sense).
++ *
++ * NOTE: if GCC ever changes so that it ignores unused types altogether, this
++ * assert might not fire! We explicitly mark it as unused because GCC 4.8+
++ * uses -Wunused-local-typedefs as part of -Wall, which means the typedef will
++ * generate a warning.
+ */
+
+ #define ASSERT_ON_COMPILE(e) \
+do { \
+ enum { AssertOnCompileMisused = ((e) ? 1 : -1) }; \
+- typedef char AssertOnCompileFailed[AssertOnCompileMisused]; \
++ UNUSED_TYPE(typedef char
AssertOnCompileFailed[AssertOnCompileMisused]); \
+} while (0)
+
+
+--- a/lib/include/vm_atomic.h
b/lib/include/vm_atomic.h
+@@ -2447,6 +2447,9 @@ Atomic_TestBit64(Atomic_uint64 *var, //
+ * (void *)val, we have (void *)(uintptr_t)val.
+ * The specific problem case is the Windows ddk compiler
+ * (as used by the SVGA driver). -- edward
++ *
++ * NOTE: See the comment in vm_assert.h for why we need UNUSED_TYPE in
++ * AtomicAssertOnCompile(), and why we need to be very careful doing so.
+ */
+
+ #define MAKE_ATOMIC_TYPE(name, size, in, out, cast)
\
+@@ -2460,7 +2463,7 @@ Atomic_TestBit64(Atomic_uint64 *var, //
+
Bug#734449: open-vm-tools-dkms: Some modules still fail to compile
Hi Hilmar, hi Jim, could you give the dkms package from http://devel.recluse.de/~bzed/.publish/2014-01-07-WisBjJ7x0Vg/ a try? If you don't trust random packages from random sources in the net, please take the source from unstable and apply the attached patch, rebuild it and see if it works. (I'd give it a try, but there is no amd64 kernel 3.11 in the repository at the moment ) Thanks, Bernd On 07.01.2014 11:35, Hilmar Preuße wrote: Package: open-vm-tools-dkms Version: 2:9.4.0-1280544-1 Severity: important Dear Maintainer, Some modules still do not build. This does not cause a failed installation - Sev important. make.log is attached. Hilmar -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.12-1-686-pae (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages open-vm-tools-dkms depends on: ii dkms 2.2.0.3-1.2 ii make 3.81-8.3 Versions of packages open-vm-tools-dkms recommends: ii open-vm-tools 2:9.4.0-1280544-1 Versions of packages open-vm-tools-dkms suggests: pn open-vm-tools-desktop none -- no debconf information -- Bernd ZeimetzDebian GNU/Linux Developer http://bzed.dehttp://www.debian.org GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#734449: open-vm-tools-dkms: Some modules still fail to compile
On 07.01.14 Bernd Zeimetz (be...@bzed.de) wrote: Hi, uups, forgot to attach the patch :) On the URI were only amd64 packages: If have to rebuild. The orig.tar.gz was also not there, hence I downloaded the source from unstable and tried to integrate the patch. Put it into /debian/patches and added an entry in the series file. The build fails: dpkg-source: info: using options from open-vm-tools-9.4.0-1280544/debian/source/options: --compression=xz dpkg-source: info: using source format `3.0 (quilt)' dpkg-source: info: building open-vm-tools using existing ./open-vm-tools_9.4.0-1280544.orig.tar.gz patching file debian/control patching file debian/patches/1a3eb34_Fix-AssertOnCompileFailed-for-GCC-4.8-kernel-3.10 patching file debian/patches/series Hunk #1 FAILED at 6. 1 out of 1 hunk FAILED patching file debian/rules dpkg-source: info: fuzz is not allowed when applying patches dpkg-source: info: if patch 'gcc-4.8-kernel-fixes.patch' is correctly applied by quilt, use 'quilt refresh' to update it dpkg-source: error: LC_ALL=C patch -t -F 0 -N -p1 -u -V never -g0 -E -b -B .pc/gcc-4.8-kernel-fixes.patch/ --reject-file=- open-vm-tools-9.4.0-1280544.orig.SgkJ1N/debian/patches/gcc-4.8-kernel-fixes.patch gave error exit status 1 Hilmar -- sigmentation fault signature.asc Description: Digital signature
Bug#734449: open-vm-tools-dkms: Some modules still fail to compile
Ah, sorry, you have to apply the patch to the sources from unstable instead of putting it into debian/patches. It removes the gcc 4.7 stuff from all files in debian/ Hilmar Preusse hill...@web.de schrieb: On 07.01.14 Bernd Zeimetz (be...@bzed.de) wrote: Hi, uups, forgot to attach the patch :) On the URI were only amd64 packages: If have to rebuild. The orig.tar.gz was also not there, hence I downloaded the source from unstable and tried to integrate the patch. Put it into /debian/patches and added an entry in the series file. The build fails: dpkg-source: info: using options from open-vm-tools-9.4.0-1280544/debian/source/options: --compression=xz dpkg-source: info: using source format `3.0 (quilt)' dpkg-source: info: building open-vm-tools using existing ./open-vm-tools_9.4.0-1280544.orig.tar.gz patching file debian/control patching file debian/patches/1a3eb34_Fix-AssertOnCompileFailed-for-GCC-4.8-kernel-3.10 patching file debian/patches/series Hunk #1 FAILED at 6. 1 out of 1 hunk FAILED patching file debian/rules dpkg-source: info: fuzz is not allowed when applying patches dpkg-source: info: if patch 'gcc-4.8-kernel-fixes.patch' is correctly applied by quilt, use 'quilt refresh' to update it dpkg-source: error: LC_ALL=C patch -t -F 0 -N -p1 -u -V never -g0 -E -b -B .pc/gcc-4.8-kernel-fixes.patch/ --reject-file=- open-vm-tools-9.4.0-1280544.orig.SgkJ1N/debian/patches/gcc-4.8-kernel-fixes.patch gave error exit status 1 Hilmar -- sigmentation fault -- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
Bug#734449: open-vm-tools-dkms: Some modules still fail to compile
On 07.01.14 Bernd Zeimetz (be...@bzed.de) wrote: Hi, Ah, sorry, you have to apply the patch to the sources from unstable instead of putting it into debian/patches. It removes the gcc 4.7 stuff from all files in debian/ Patch applies now. I can build the new packages and installed it. The make.log now has less warnings, but the error message itself remains and the modules fail to compile. New make.log attached. Hilmar -- sigmentation fault DKMS make.log for open-vm-tools-9.4.0 for kernel 3.12-1-686-pae (i686) Tue 7 Jan 23:40:47 CET 2014 Using 2.6.x kernel build system. make: Entering directory `/var/lib/dkms/open-vm-tools/9.4.0/build/vmblock' make -C /lib/modules/3.12-1-686-pae/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \ MODULEBUILDDIR=/var/lib/dkms/open-vm-tools/9.4.0/build modules make[1]: Entering directory `/usr/src/linux-headers-3.12-1-686-pae' CC [M] /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/block.o CC [M] /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/control.o /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/control.c: In function ‘ExecuteBlockOp’: /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/control.c:286:9: warning: assignment from incompatible pointer type [enabled by default] name = getname(buf); ^ CC [M] /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/dentry.o /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/dentry.c:38:4: warning: initialization from incompatible pointer type [enabled by default] .d_revalidate = DentryOpRevalidate, ^ /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/dentry.c:38:4: warning: (near initialization for ‘LinkDentryOps.d_revalidate’) [enabled by default] /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/dentry.c: In function ‘DentryOpRevalidate’: /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/dentry.c:104:7: warning: passing argument 2 of ‘actualDentry-d_op-d_revalidate’ makes integer from pointer without a cast [enabled by default] return actualDentry-d_op-d_revalidate(actualDentry, nd); ^ /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/dentry.c:104:7: note: expected ‘unsigned int’ but argument is of type ‘struct nameidata *’ CC [M] /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/file.o CC [M] /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/filesystem.o CC [M] /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/inode.o /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/inode.c:49:4: warning: initialization from incompatible pointer type [enabled by default] .lookup = InodeOpLookup, ^ /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/inode.c:49:4: warning: (near initialization for ‘RootInodeOps.lookup’) [enabled by default] /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/inode.c: In function ‘InodeOpLookup’: /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/inode.c:138:32: error: incompatible types when assigning to type ‘kgid_t’ from type ‘int’ inode-i_uid = inode-i_gid = 0; ^ /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/inode.c: In function ‘InodeOpFollowlink’: /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/inode.c:224:4: error: implicit declaration of function ‘vfs_follow_link’ [-Werror=implicit-function-declaration] ret = vfs_follow_link(nd, iinfo-name); ^ cc1: some warnings being treated as errors make[4]: *** [/var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/inode.o] Error 1 make[3]: *** [_module_/var/lib/dkms/open-vm-tools/9.4.0/build/vmblock] Error 2 make[2]: *** [sub-make] Error 2 make[1]: *** [all] Error 2 make[1]: Leaving directory `/usr/src/linux-headers-3.12-1-686-pae' make: *** [vmblock.ko] Error 2 make: Leaving directory `/var/lib/dkms/open-vm-tools/9.4.0/build/vmblock' Using 2.6.x kernel build system. Building vmhgfs without VMCI module symbols. make: Entering directory `/var/lib/dkms/open-vm-tools/9.4.0/build/vmhgfs' make -C /lib/modules/3.12-1-686-pae/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \ MODULEBUILDDIR=/var/lib/dkms/open-vm-tools/9.4.0/build modules make[1]: Entering directory `/usr/src/linux-headers-3.12-1-686-pae' CC [M] /var/lib/dkms/open-vm-tools/9.4.0/build/vmhgfs/backdoor.o CC [M] /var/lib/dkms/open-vm-tools/9.4.0/build/vmhgfs/backdoorGcc32.o CC [M] /var/lib/dkms/open-vm-tools/9.4.0/build/vmhgfs/bdhandler.o CC [M] /var/lib/dkms/open-vm-tools/9.4.0/build/vmhgfs/cpName.o CC [M] /var/lib/dkms/open-vm-tools/9.4.0/build/vmhgfs/cpNameLinux.o CC [M] /var/lib/dkms/open-vm-tools/9.4.0/build/vmhgfs/cpNameLite.o CC [M] /var/lib/dkms/open-vm-tools/9.4.0/build/vmhgfs/cpNameUtil.o CC [M] /var/lib/dkms/open-vm-tools/9.4.0/build/vmhgfs/cpNameUtilLinux.o CC [M] /var/lib/dkms/open-vm-tools/9.4.0/build/vmhgfs/dentry.o CC [M] /var/lib/dkms/open-vm-tools/9.4.0/build/vmhgfs/dir.o /var/lib/dkms/open-vm-tools/9.4.0/build/vmhgfs/dir.c:82:4: error: unknown
Bug#734449: open-vm-tools-dkms: Some modules still fail to compile
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Hilmar, thanks for your help so far! As 3.12 for amd64 arrive in unstable today, I was able to poke a bit at the code. By picking some patches from upstream and (hopefully!) adding a few from_kuid() I should be able to make it build with 3.12 tomorrow. I'll let you know! Thanks, Bernd On 01/07/2014 11:46 PM, Hilmar Preusse wrote: On 07.01.14 Bernd Zeimetz (be...@bzed.de) wrote: Hi, Ah, sorry, you have to apply the patch to the sources from unstable instead of putting it into debian/patches. It removes the gcc 4.7 stuff from all files in debian/ Patch applies now. I can build the new packages and installed it. The make.log now has less warnings, but the error message itself remains and the modules fail to compile. New make.log attached. Hilmar - -- Bernd ZeimetzDebian GNU/Linux Developer http://bzed.dehttp://www.debian.org GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iQIcBAEBCAAGBQJSzKlGAAoJEOs2Fxpv+UNfMlgQAJRDDY8ftqiW76Nlup43pXGG c478qhmG8Irqnt0kMgVm0i56IoFwtYZENYyC2O8tY03ZRu8OwJ1a7+73R3WWCaEz eOeF/ETTcloAzfr2Oogm2piCuopVYLLulF2+SjTANSjQq017tXkX4u/hIPw7luK7 tT7CP2zcWUSLD8w+PN7iSk7cS7OD5C68+fMMco0QoLv3E23GEufQhB1wIsBAWuaL 72lrZwTKcURV8bkRY3TQvQtPGebdms/0VQSvBCwQ4Gqj9PKuEAdRbVskVauHzaBn 4kHTSDL6TomfcAqygDZb5vnz9PbOpAR0exSRPGdYa7PMNWqXgj4D+jKm3osHQAML GSyqoW7RPSqk5c8CVu6NX+ENlApFCaK9ilj8Z7FPopVH79w3cJ1GWtIsrtq89xgB A2nl0YLKW38AKlqLcX3Pdk1ke+lqjq+xSeuYDVf7KlDE/nhFGXS2JADnoZ8uQlK/ F40bcK+WfwHWxr7GK5AlCE0KNttMDt2dSXxbYHTuZEyx6RGqlYiBR8XzxofLxqpG oZiOvdzPvdIKGwuwaKBFa7KPR4AdrYSltVzuu3RASkObWzpef09JvT4IUBFgaEFl cVp4u30RZ4cjQTAbwH4uWrVo3UhOeLF9p/ykhYXJ598i6JKLbhvgveWpzCi8Ibl4 oX0OBQntEGcQZIOmu7GM =9DxJ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
