Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

problem about pqR on windows #9

Closed
armgong opened this issue Jun 25, 2013 · 2 comments
Closed

problem about pqR on windows #9

armgong opened this issue Jun 25, 2013 · 2 comments

Comments

@armgong
Copy link

armgong commented Jun 25, 2013

Hi Radford.

Thank you for your brilliant work on pqR.

Today I compiled pqR on windows 64 use mingw-w64 (http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/rubenvb/gcc-4.8-release/)

after modify some files(the patch file already sent to your gmail ),Now pqR seems work on windows x64,Rgui can success started,but When start RGUI.exe it show following message in console (please see the attachment picture
error
)

Could help me find the error?

thank you very much

@radfordneal
Copy link
Owner

I think this has to do with tracemem not existing in pqR, but being enabled by default in the Windows build process. In eliminating tracemem from pqR, I made a minimal change to the Unix build process so that it just never defines R_MEMORY_PROFILING, so the tracemem code (which won't work now) is never enabled. You need to be sure that R_MEMORY_PROFILING is never defined on Windows too. Possibly putting #undef R_MEMORY_PROFILING at the start of src/include/Rinternals.h will do the trick (though that's not the way it should really be done).

@armgong
Copy link
Author

armgong commented Jun 25, 2013

thank you ,in windows build this is defined in config.h ,just undefine it , the warnings is gone

@armgong armgong closed this as completed Jun 25, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants