Apparently, this is a bug in MinGW. The same problem is described here.
http://comments.gmane.org/gmane.linux.utilities.smartmontools/8440
And reported as a bug here:
http://sourceforge.net/p/mingw/bugs/2045/
I haven't read all of it, but perhaps you can try out the attached patch?
Regards,
Peter
On Sat, 8 Feb 2014, Brian Hinz wrote:
Hi,
Did anyone else get a commit notification for r5158? I did not, but in either
case the nightly build failed with the following error:
make[3]: Entering directory
`/c/jenkins/workspace/win32-binaries/build/tigervnc-1.3.80+20140207svn5158'
[ 84%] [32mBuilding CXX object
win/winvnc/CMakeFiles/winvnc4.dir/buildTime.cxx.obj
[0m[ 84%] [32mBuilding CXX object
win/winvnc/CMakeFiles/winvnc4.dir/ControlPanel.cxx.obj
[0m[ 85%] [32mBuilding CXX object
win/winvnc/CMakeFiles/winvnc4.dir/JavaViewer.cxx.obj
[0m[ 85%] [32mBuilding CXX object
win/winvnc/CMakeFiles/winvnc4.dir/ManagedListener.cxx.obj
[0m[ 86%] [32mBuilding CXX object
win/winvnc/CMakeFiles/winvnc4.dir/QueryConnectDialog.cxx.obj
[0m[ 86%] [32mBuilding CXX object
win/winvnc/CMakeFiles/winvnc4.dir/STrayIcon.cxx.obj
[0m[ 87%] [32mBuilding CXX object
win/winvnc/CMakeFiles/winvnc4.dir/VNCServerService.cxx.obj
[0mIn file included from
c:/jenkins/workspace/win32-binaries/build/tigervnc-1.3.80+20140207svn5158/win/winvnc/VNCServerService.cxx:25:0:
c:\mingw\bin\../lib/gcc/mingw32/4.7.2/../../../../include/wtsapi32.h:82:3:
error: 'WTS_CONNECTSTATE_CLASS' does not name a type
c:\mingw\bin\../lib/gcc/mingw32/4.7.2/../../../../include/wtsapi32.h:88:3:
error: 'WTS_CONNECTSTATE_CLASS' does not name a type
c:\mingw\bin\../lib/gcc/mingw32/4.7.2/../../../../include/wtsapi32.h:117:74:
error: 'WTS_INFO_CLASS' has not been declared
c:\mingw\bin\../lib/gcc/mingw32/4.7.2/../../../../include/wtsapi32.h:119:74:
error: 'WTS_INFO_CLASS' has not been declared
make[3]: *** [win/winvnc/CMakeFiles/winvnc4.dir/VNCServerService.cxx.obj] Error
1
make[3]: Leaving directory
`/c/jenkins/workspace/win32-binaries/build/tigervnc-1.3.80+20140207svn5158'
make[2]: *** [win/winvnc/CMakeFiles/winvnc4.dir/all] Error 2
make[2]: Leaving directory
`/c/jenkins/workspace/win32-binaries/build/tigervnc-1.3.80+20140207svn5158'
make[1]: *** [all] Error 2
make[1]: Leaving directory
`/c/jenkins/workspace/win32-binaries/build/tigervnc-1.3.80+20140207svn5158'
make: *** [exe] Error 2
Build step 'Execute shell' marked build as failure
Archiving artifacts
Finished: FAILURE
I'm reviewing the build script to make sure it's not a setup issue on my part,
but this has been stable for several months.
-brian
---
Peter Astrand ThinLinc Chief Developer
Cendio AB http://cendio.com
Teknikringen 8 http://twitter.com/ThinLinc
583 30 Linkoping http://facebook.com/ThinLinc
Phone: +46-13-214600 http://google.com/+CendioThinLinc
------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
_______________________________________________
Tigervnc-devel mailing list
Tigervnc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
