I tracked down that strange "unresolved symbol" error I was getting. It turns out that rpy2 tip includes a reference to R_ProcessEvents unconditionally, but in fact R_ProcessEvents is not a portable API. R_ProcessEvents only exists on Win32 and OS X/Aqua builds of R.
And on OS X, unless someone has used the C api to define a special hook function, all it does is check R_interrupts_pending. The only time it really does anything useful is on Win32, and most calls to it in the R source are protected by #ifdef Win32. Attached patch stubs out the call to R_ProcessEvents unless defined(Win32). Built and tested on Linux (after also stubbing out the new device code, since it fails to compile). -- Nathaniel
NEW_make-ProcessEvents-windows-only
Description: Binary data
------------------------------------------------------------------------------ Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
_______________________________________________ rpy-list mailing list rpy-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rpy-list
