qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] qemu 0.10.6 on Mac OS X Tiger: NSFullScreenModeAllScreens u


From: Ryan Schmidt
Subject: [Qemu-devel] qemu 0.10.6 on Mac OS X Tiger: NSFullScreenModeAllScreens undeclared
Date: Wed, 12 Aug 2009 05:11:53 -0500

Hi. I'm with the MacPorts project (a package management system for Mac OS X), and we've received some reports that qemu 0.10.6 can't be built on Mac OS X 10.4 Tiger. This is what I get on 10.4.11 Intel:


  OBJC  cocoa.o
cocoa.m:233: warning: no previous prototype for 'cocoa_keycode_to_qemu'
cocoa.m: In function '-[QemuCocoaView toggleFullScreen:]':
cocoa.m:426: warning: 'QemuCocoaView' may not respond to '- exitFullScreenModeWithOptions:'
cocoa.m:426: warning: (Messages without a matching method signature
cocoa.m:426: warning: will be assumed to return 'id' and accept
cocoa.m:426: warning: '...' as arguments.)
cocoa.m:444: error: 'NSFullScreenModeAllScreens' undeclared (first use in this function)
cocoa.m:444: error: (Each undeclared identifier is reported only once
cocoa.m:444: error: for each function it appears in.)
cocoa.m:445: error: 'NSFullScreenModeSetting' undeclared (first use in this function) cocoa.m:446: warning: 'QemuCocoaView' may not respond to '- enterFullScreenMode:withOptions:' cocoa.m: In function '-[QemuCocoaAppController openPanelDidEnd:returnCode:contextInfo:]': cocoa.m:786: warning: initialization discards qualifiers from pointer target type
make: *** [cocoa.o] Error 1


This has been reported in many places:

http://lists.gnu.org/archive/html/qemu-devel/2008-10/msg00336.html

http://lists.macosforge.org/pipermail/macports-users/2009-April/ 014665.html

http://lists.macosforge.org/pipermail/macports-users/2009-May/ 015353.html

http://qemu-forum.ipi.fi/viewtopic.php?f=6&t=5161&p=15200

In response to the October 2008 report of this problem on qemu-devel, this response included a patch:

http://lists.gnu.org/archive/html/qemu-devel/2008-10/msg00393.html

So, what is the status of this issue? Will the patch be incorporated? It doesn't apply cleanly anymore to the 0.10.6 sources; 3 of the 16 hunks fail to apply, so I don't know if it actually fixes the issue.






reply via email to

[Prev in Thread] Current Thread [Next in Thread]