| View previous topic :: View next topic |
| Author |
Message |
Jhedron
n00b
Joined: 07 Jun 2005
Posts: 45
Location: Michigan, USA
|
 Posted: Tue Oct 05, 2010 7:19 pm Post subject: [SOLVED] open-vm-tools: conflicting types for 'Bool' |
 |
|
I have been unable to build open-vm-tools for the past month or so. I get the same errors (see below) in all versions since 0.0.0.0.20100616.268169-r1 (I haven't tested with anything earlier). As this is the version currently installed, it was obviously building successfully at some point. I think there may have been some other update which caused this, but I'm not sure where to start looking.
The first error:
| Code: | In file included from /usr/include/X11/extensions/render.h:29,
from /usr/include/X11/extensions/Xrender.h:33,
from /usr/include/X11/extensions/Xrandr.h:33,
from resolutionX11.c:32:
/usr/include/X11/Xdefs.h:47: error: conflicting types for ‘Bool’
/var/tmp/portage/app-emulation/open-vm-tools-0.0.20100919.301124/work/open-vm-tools-2010.09.19-301124/lib/include/vm_basic_types.h:86: note: previous declaration of ‘Bool’ was here |
And then, a little later on in the output:
| Code: | resolutionX11.c:115: error: conflicting types for ‘ResolutionBackendInit’
resolutionInt.h:73: note: previous declaration of ‘ResolutionBackendInit’ was here
resolutionX11.c:168: error: conflicting types for ‘ResolutionSetResolution’
resolutionInt.h:76: note: previous declaration of ‘ResolutionSetResolution’ was here
resolutionX11.c:205: error: conflicting types for ‘ResolutionSetTopology’
resolutionInt.h:81: note: previous declaration of ‘ResolutionSetTopology’ was here |
I believe the second group of errors is caused by the first, as all of the functions referenced by the messages have a return type of 'Bool'.
For reference, I am running Gentoo as a 64-bit guest in VMWare Workstation 7.1 on a Windows 7 (64-bit) host.
Last edited by Jhedron on Thu Jan 20, 2011 3:33 pm; edited 1 time in total |
|
| Back to top |
|
 |
Hu
Administrator
Joined: 06 Mar 2007
Posts: 22148
|
| Posted: Wed Oct 06, 2010 2:27 am Post subject: Re: Can't build open-vm-tools: conflicting types for 'Bool' |
|
|
| Jhedron wrote: | I'm not sure where to start looking.
The first error:
| Code: | In file included from /usr/include/X11/extensions/render.h:29,
from /usr/include/X11/extensions/Xrender.h:33,
from /usr/include/X11/extensions/Xrandr.h:33,
from resolutionX11.c:32:
/usr/include/X11/Xdefs.h:47: error: conflicting types for ‘Bool’
|
|
I would start looking at when you last upgraded Xdefs.h. For me, it is owned by x11-proto/xproto and was installed a few months ago. When did you last successfully reinstall app-emulation/open-vm-tools? When did you last install/upgrade the package that owns Xdefs.h on your system? |
|
| Back to top |
|
|
Jhedron
n00b
Joined: 07 Jun 2005
Posts: 45
Location: Michigan, USA
|
| Posted: Thu Oct 07, 2010 3:47 am Post subject: Re: Can't build open-vm-tools: conflicting types for 'Bool' |
|
|
| Hu wrote: | | When did you last successfully reinstall app-emulation/open-vm-tools? |
I wasn't able to check the exact date (the VM is installed on my computer at work and I was swamped today), but it was sometime in mid-July.
| Hu wrote: | | When did you last install/upgrade the package that owns Xdefs.h on your system? |
Like you, Xdefs.h is owned by x11-proto/xproto on this system. Again, I wasn't able to check the exact date, but it was last updated to 7.0.18 in mid-August.
I should also mention that I have attempted to install each of the versions of x11-proto/xproto in portage (7.0.16, 7.0.17, and 7.0.18 ) and I get the same error with all combinations of xproto + open-vm-tools.
I'll try to look up more specific dates tomorrow if I get a chance. |
|
| Back to top |
|
|
Jhedron
n00b
Joined: 07 Jun 2005
Posts: 45
Location: Michigan, USA
|
| Posted: Fri Oct 08, 2010 1:35 pm Post subject: |
|
|
As promised, here are some more specific dates/times.
Currently, open-vm-tools-0.0.20100616.268169-r1 is installed. The last successful install was on 2010/07/09. The first (failed) attempt to update (to version 0.0.20100824.292196) occurred on 2010/08/30.
The currently installed version of xproto is 7.0.18. At the time open-vm-tools was last successfully installed, I was running xproto-7.0.17 which was installed on 2010/05/17. At the time of the first failed attempt to update open-vm-tools, I was running 7.0.18 which had been installed on 2010/08/11. |
|
| Back to top |
|
|
Hu
Administrator
Joined: 06 Mar 2007
Posts: 22148
|
| Posted: Fri Oct 08, 2010 10:35 pm Post subject: |
|
|
| Weird. The basic problem is that the VM tools redeclared a symbol provided by xproto, but without a deeper investigation, I cannot explain why a combination that allowed you to install it now fails. If I were to guess, I would say that some third factor not yet determined influenced the situation, either enabling the prior install or encouraging this one to fail. |
|
| Back to top |
|
|
Child_of_Sun_24
Guru
Joined: 28 Jul 2004
Posts: 590
|
| Posted: Mon Oct 11, 2010 12:08 am Post subject: |
|
|
Same problem here.
I have setup my System today but open-vm-tools won't build with the same error message.
Have you got a Solution already ?
CoS24 |
|
| Back to top |
|
|
Child_of_Sun_24
Guru
Joined: 28 Jul 2004
Posts: 590
|
| Posted: Mon Oct 11, 2010 2:09 pm Post subject: |
|
|
I have tried it now with xorg-server 1.9 and with different combinations of use flags, only completly without X it compiles.
Now i have uninstalled the open-vm-tools and open-vm-tools-kmod and use the vmware-tools-distrib package which ships with vmware, now it works for me.
CoS |
|
| Back to top |
|
|
Jhedron
n00b
Joined: 07 Jun 2005
Posts: 45
Location: Michigan, USA
|
| Posted: Wed Oct 13, 2010 3:42 pm Post subject: |
|
|
| Child_of_Sun_24 wrote: | Same problem here.
I have setup my System today but open-vm-tools won't build with the same error message.
Have you got a Solution already ?
CoS24 |
Sorry, no, I have not managed to successfully install open-vm-tools yet. Then again, I haven't had a chance to work on it much either. There are a few things I'm going to look at when I get a chance. Hopefully I'll find something. |
|
| Back to top |
|
|
AdmiralNemo
Apprentice
Joined: 25 Sep 2004
Posts: 247
Location: Overland Park, KS
|
| Posted: Tue Nov 23, 2010 5:16 am Post subject: |
|
|
Does anybody have any updates on this yet? I just built a fresh VMWare virtual machine (~amd64) and I encountered this problem. On my other VMs, it wasn't a problem because the old version was still installed and functional, but this new virtual machine has no old version, obviously. I can't seem to find mention of this problem anywhere on the 'net except this thread, either.
_________________
Help the Unanswered |
|
| Back to top |
|
|
Jhedron
n00b
Joined: 07 Jun 2005
Posts: 45
Location: Michigan, USA
|
| Posted: Wed Nov 24, 2010 1:49 pm Post subject: |
|
|
| AdmiralNemo wrote: | | Does anybody have any updates on this yet? |
I am continuing to struggle with this issue. I tried following the trail of #includes to see if I could find anything, but I just don't have the time to spend on something like that right now. I did find some places where header files may have been included indirectly when they weren't expected to be. There also appeared to be some places where this problem may have occurred before as there were #undef's following the include of the XLib headers. Like I said, though, I can't really spend much time analyzing the code so I may have misread something.
| AdmiralNemo wrote: | | I just built a fresh VMWare virtual machine (~amd64) and I encountered this problem. |
Nuts. I was going to try starting fresh with a new VM, but I guess that won't work. I have also recently rebuilt all of my installed packages, but this issue persists. |
|
| Back to top |
|
|
Child_of_Sun_24
Guru
Joined: 28 Jul 2004
Posts: 590
|
| Posted: Mon Jan 03, 2011 1:45 pm Post subject: Hi there |
|
|
I have solved the Problem very dirty and i don't know if it works perfectly (For me it works).
Search for /usr/include/X11/Xdefs.h
There is in line 47
44:#ifndef Bool
45:# ifndef _XTYPEDEF_BOOL
46:# define _XTYPEDEF_BOOL
47:typedef int Bool;
48:# endif
49:#endif
there you change:
typedef int Bool;
to
typedef int char;
then it Compiles fine without an error.
After compile just change it back for compatibility issues.
It' very dirty but i don't know how to change the code in the open-vm-tools source files.
CoS24 |
|
| Back to top |
|
|
Child_of_Sun_24
Guru
Joined: 28 Jul 2004
Posts: 590
|
| Posted: Mon Jan 03, 2011 4:44 pm Post subject: Re: Hi there |
|
|
| Quote: | there you change:
typedef int Bool;
to
typedef int char;
|
Sorry my error you must change it to:
typedef char Bool;
CoS24 |
|
| Back to top |
|
|
BtbN
n00b
Joined: 24 Sep 2007
Posts: 4
|
| Posted: Sat Jan 15, 2011 10:12 pm Post subject: |
|
|
This Patch makes it build:
| Quote: | --- lib/include/vm_basic_types.h.orig 2011-01-15 21:56:10.676998930 +0100
+++ lib/include/vm_basic_types.h 2011-01-15 21:56:30.867002098 +0100
@@ -83,7 +83,7 @@
/* STRICT ANSI means the Xserver build and X defines Bool differently. */
#if !defined(__STRICT_ANSI__) || defined(__FreeBSD__) || defined(__MINGW32__)
-typedef char Bool;
+typedef int Bool;
#endif
#ifndef FALSE
--- lib/include/vmxrpc.h.orig 2011-01-15 22:05:09.738001018 +0100
+++ lib/include/vmxrpc.h 2011-01-15 22:05:57.358952495 +0100
@@ -260,7 +260,7 @@
xdr_Bool(XDR *xdrs, // IN
Bool *ip) // IN/OUT
{
- return xdr_char(xdrs, ip);
+ return xdr_int32(xdrs, ip);
}
#endif |
|
|
| Back to top |
|
|
Jhedron
n00b
Joined: 07 Jun 2005
Posts: 45
Location: Michigan, USA
|
| Posted: Thu Jan 20, 2011 3:29 pm Post subject: |
|
|
I just emerged the latest version of open-vm-tools this morning with the 'X' use flag enabled and it compiled without error. Whatever the issue, this now appears to be working correctly.
| Code: | | app-emulation/open-vm-tools-0.0.20101219.339835 USE="X fuse icu pic -doc -unity -xinerama" |
|
|
| Back to top |
|
|
|
Portage & Programming
