[R-pkg-devel] Help with Windows build failure
Hi, everyone. I have done some work this weekend to allow the SnakeCharmR package ( https://github.com/asieira/SnakeCharmR) to be compiled under Windows. For reference, this is an Rcpp-based packages that links to the system's libpython. I have been able to test it on my box using Windows 10 and several Python versions: * Rtools mingw_64/opt Python 2.7.9; * python.org 2.7.13 64-bit; * python.org 3.6.1 64-bit; * python.org 2.7.x 32-bit on Appveyor ( https://ci.appveyor.com/project/asieira/SnakeCharmR). Still, when I submit my source package to win-builder I get an error: https://win-builder.r-project.org/9aqdlW0D6e3m/ https://win-builder.r-project.org/9aqdlW0D6e3m/00install.out shows some warnings on header files that are outside of my control, but ends with a successful compilation. However, it compiles only the 64-bit version of the DLL and gives me this warning: Warning: this package has a non-empty 'configure.win' file, so building only the main architecture Finally, when we look at https://win-builder.r-project.org/9aqdlW0D6e3m/00check.log we see an error due to the fact that the package can’t be tested on i386: ** checking whether the package can be loaded ... ERROR Loading this package had a fatal error status code 1 Loading log: Error: package 'SnakeCharmR' is not installed for 'arch = i386' Execution halted ** DONE Status: 1 ERROR, 1 NOTE I apologize if this is a beginner’s problem, but this is my first R package ever and I’m not really used to working with R on Windows. Would appreciate any guidance and pointers on how to address this and get the package to pass the necessary CRAN automated tests. Thanks in advance for your help. -- Alexandre Sieira CISA, CISSP, ISO 27001 Lead Auditor "The truth is rarely pure and never simple." Oscar Wilde, The Importance of Being Earnest, 1895, Act I [[alternative HTML version deleted]] __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
Re: [R-pkg-devel] Help with Windows build failure
Hi, Dirk. Thank you for responding. I do sympathize with your frustrations, due to the exact complexity you are mentioning and also my ignorance on how R packages compile on Windows, I had SnakeCharmR signal ‘OS_type: Unix’ for the longest time. The thing is that AFAIK this works on Windows now, both with the python.org and Rtools mingw Python distributions. The challenge now is figuring out the best to get this into CRAN as a Windows package as well. Challenge #1: getting past the win builder pre-check. :) I was reading some other posts on this list and maybe setting “Biarch: false” could help? I’ll try that next. -- Alexandre Sieira CISA, CISSP, ISO 27001 Lead Auditor "The truth is rarely pure and never simple." Oscar Wilde, The Importance of Being Earnest, 1895, Act I On 6 April 2017 at 22:21:27, Dirk Eddelbuettel (e...@debian.org) wrote: On 2 April 2017 at 17:21, Alexandre Sieira wrote: | Hi, everyone. | | I have done some work this weekend to allow the SnakeCharmR package ( | https://github.com/asieira/SnakeCharmR) to be compiled under Windows. For | reference, this is an Rcpp-based packages that links to the system's | libpython. | | I have been able to test it on my box using Windows 10 and several Python | versions: | | * Rtools mingw_64/opt Python 2.7.9; | * python.org 2.7.13 64-bit; | * python.org 3.6.1 64-bit; | * python.org 2.7.x 32-bit on Appveyor ( | https://ci.appveyor.com/project/asieira/SnakeCharmR). | | Still, when I submit my source package to win-builder I get an error: | https://win-builder.r-project.org/9aqdlW0D6e3m/ | | https://win-builder.r-project.org/9aqdlW0D6e3m/00install.out shows some | warnings on header files that are outside of my control, but ends with a | successful compilation. However, it compiles only the 64-bit version of the | DLL and gives me this warning: | | Warning: this package has a non-empty 'configure.win' file, | so building only the main architecture | | | Finally, when we look at | https://win-builder.r-project.org/9aqdlW0D6e3m/00check.log we see an error | due to the fact that the package can’t be tested on i386: | | ** checking whether the package can be loaded ... ERROR | Loading this package had a fatal error status code 1 | Loading log: | Error: package 'SnakeCharmR' is not installed for 'arch = i386' | Execution halted | ** DONE | Status: 1 ERROR, 1 NOTE | | | I apologize if this is a beginner’s problem, but this is my first R package | ever and I’m not really used to working with R on Windows. Would appreciate | any guidance and pointers on how to address this and get the package to | pass the necessary CRAN automated tests. I tried to make Python and R co-exist at some point; my conclusion was there aren't enough days in the week to figure out how to do it on Windows. It's easy to do on Linux, and I don't personally have OS X / macOS use cases but here it's feasible if you're careful about your toolchain. I think you should just consider 'OS_type: unix' in your DESCRIPTION. A working and uploaded package on two OSs beats an "almost there but never finished" package on three in my book. Dirk -- http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org [[alternative HTML version deleted]] __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
Re: [R-pkg-devel] Help with Windows build failure
So actually 'Biarch: false’ didn’t help at all, same problem: https://win-builder.r-project.org/KhXyGby5Yhjm/ Does anyone know if the win builder machines have both 32-bit and 64-bit Python installed and in the PATH? -- Alexandre Sieira CISA, CISSP, ISO 27001 Lead Auditor "The truth is rarely pure and never simple." Oscar Wilde, The Importance of Being Earnest, 1895, Act I On 7 April 2017 at 09:28:19, Alexandre Sieira (alexandre.sie...@gmail.com) wrote: Hi, Dirk. Thank you for responding. I do sympathize with your frustrations, due to the exact complexity you are mentioning and also my ignorance on how R packages compile on Windows, I had SnakeCharmR signal ‘OS_type: Unix’ for the longest time. The thing is that AFAIK this works on Windows now, both with the python.org and Rtools mingw Python distributions. The challenge now is figuring out the best to get this into CRAN as a Windows package as well. Challenge #1: getting past the win builder pre-check. :) I was reading some other posts on this list and maybe setting “Biarch: false” could help? I’ll try that next. -- Alexandre Sieira CISA, CISSP, ISO 27001 Lead Auditor "The truth is rarely pure and never simple." Oscar Wilde, The Importance of Being Earnest, 1895, Act I On 6 April 2017 at 22:21:27, Dirk Eddelbuettel (e...@debian.org) wrote: On 2 April 2017 at 17:21, Alexandre Sieira wrote: | Hi, everyone. | | I have done some work this weekend to allow the SnakeCharmR package ( | https://github.com/asieira/SnakeCharmR) to be compiled under Windows. For | reference, this is an Rcpp-based packages that links to the system's | libpython. | | I have been able to test it on my box using Windows 10 and several Python | versions: | | * Rtools mingw_64/opt Python 2.7.9; | * python.org 2.7.13 64-bit; | * python.org 3.6.1 64-bit; | * python.org 2.7.x 32-bit on Appveyor ( | https://ci.appveyor.com/project/asieira/SnakeCharmR). | | Still, when I submit my source package to win-builder I get an error: | https://win-builder.r-project.org/9aqdlW0D6e3m/ | | https://win-builder.r-project.org/9aqdlW0D6e3m/00install.out shows some | warnings on header files that are outside of my control, but ends with a | successful compilation. However, it compiles only the 64-bit version of the | DLL and gives me this warning: | | Warning: this package has a non-empty 'configure.win' file, | so building only the main architecture | | | Finally, when we look at | https://win-builder.r-project.org/9aqdlW0D6e3m/00check.log we see an error | due to the fact that the package can’t be tested on i386: | | ** checking whether the package can be loaded ... ERROR | Loading this package had a fatal error status code 1 | Loading log: | Error: package 'SnakeCharmR' is not installed for 'arch = i386' | Execution halted | ** DONE | Status: 1 ERROR, 1 NOTE | | | I apologize if this is a beginner’s problem, but this is my first R package | ever and I’m not really used to working with R on Windows. Would appreciate | any guidance and pointers on how to address this and get the package to | pass the necessary CRAN automated tests. I tried to make Python and R co-exist at some point; my conclusion was there aren't enough days in the week to figure out how to do it on Windows. It's easy to do on Linux, and I don't personally have OS X / macOS use cases but here it's feasible if you're careful about your toolchain. I think you should just consider 'OS_type: unix' in your DESCRIPTION. A working and uploaded package on two OSs beats an "almost there but never finished" package on three in my book. Dirk -- http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org [[alternative HTML version deleted]] __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
