[Rcpp-devel] Rtools not finding *.o files during compilation

[Dirk Eddelbuettel]

On 7 July 2016 at 07:30, Charles Determan wrote:
| I am trying to help a user debug the installation of one of my packages and
| have come across an error I don't understand.
| 
| The current process has been as follows:
| 
| 1. User using Windows OS
| 2. User trying to install development version from my github
| 3. User has current Rtools installed
| 4. User behind firewall so downloaded local copy
| 5. User extracted tar version and re-archived as zip file.
| 6. User runs install.packages('package.zip", repos=NULL, type="source")

I don't understand 5 and 6. Why would you do that?

*Either* create a binary zip the way one does Windows (it's a documented
option to R CMD INSTALL, if memory serves -- I no longer manually touch
Windows) *or* work from .tar.gz source like everybody else, especially given
1. to 3.

Dirk
 
| Compilation appears to run normally and all environmental variables are
| recognized but when reaching the linking stage it returns multiple statements
| such as:
| 
| C:\Rtools\mingw_64\bin\nm.exe: 'RcppExports.o': No such file
| 
| For every *.o file.  You could see the full user output here (http://
| pastebin.com/itNbaMJg).  What could have resulted in this problem?
| 
| Regards,
| Charles
| _______________________________________________
| Rcpp-devel mailing list
| Rcpp-devel at lists.r-forge.r-project.org
| https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | edd at debian.org