To be more precise, while the build process worked, the check did not. When it got to the point "* checking for portable compilation flags in Makevars ..." a number of shells popped up (to run c:\Rtools\sh.exe) and the process died. This happens with Rcpp and cxxPack on an AMD machine running Windows 7 (64bit), using the 64bit version of R.
On Mon, Jul 5, 2010 at 7:53 PM, Dominick Samperi <djsamp...@gmail.com>wrote: > Hello, > > After much tinkering I managed to build packages using the 64bit version of > R with the help of hints from > http://www.murdoch-sutherland.com/Rtools/ > and > http://www.stats.ox.ac.uk/~ripley/Win64/W64porting.html<http://www.stats.ox.ac.uk/%7Eripley/Win64/W64porting.html> > and > R-admin Manual. > > But a hack was required, and this seems to be related to > a comment about underscores at the end of the second > reference above (but this comment is about FUTURE > changes in R starting with 2.12.x, and I'm not sure how > it applies to the current problem using 2.11.1). > > If I simply follow the instructions of the first reference I > get lots of "cannot export / symbol not defined" errors because > by default the leading underscore is stripped off during the > shared library build process, specifically, all names in > tmp.def (created in share/winshlib.mk) do not contain a > leading underscore. > > If I modify share/winshlib.mk so that the leading underscore > is not stripped everything works fine. > > Have I missed some documentation explaining what is > going on here? > > Thanks, > Dominick > > > [[alternative HTML version deleted]] ______________________________________________ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
