[Rquantlib-devel] RQuantLib fixed-income discussion (Re: 1 Rquantlib-devel moderator request(s) waiting)

Dirk Eddelbuettel edd at debian.org
Thu Oct 9 16:23:47 CEST 2014


On 9 October 2014 at 15:55, Michele Salvadore wrote:
| On 9 October 2014 13:26, Dirk Eddelbuettel <edd at debian.org> wrote:
|     Now it turns out that the suggested change breaks the Travis auto-builder.
|     That is something to avoid as we set up continuous integration to catch
|     these
|     things. The error happens right at the top of R CMD check:
| 
|       * checking whether package ‘RQuantLib’ can be installed ... ERROR
|       Installation failed.
|       See ‘/home/travis/build/eddelbuettel/rquantlib/RQuantLib.Rcheck/
|     00install.out’ for details.
| 
|     But I don;t have access to the log...
| 
|     I also note that you switched to using auto -- RQuantLib is not (yet?) a
|     C++11 project, and it may good to not force that just yet.
| 
|  
| I thought C++11 had to be switched on already in order to support for long long
| type, see your comment here:
| http://lists.r-forge.r-project.org/pipermail/rquantlib-devel/2014-September/
| 000015.html

It was a guess of mine, the code may also fail to build for other reasons.

But I think it would be preferable for you to keep the repo buildable ;-) 
So let's fix this now before adding further pull requests, or expanding the
current one.
 
| Sorry about that, will revert to use explicit types.
| In regards to the build I apologize, unfortunately I am stuck on a windows box
| for this project and I am struggling a bit with the platform. Any chance you
| recall how the win-builder get around the issue with the long long type
| discussed in the thread above without -std=c++0x?

win-builder has not changed in a while, and RQuantLib passed all tests when
uploaded.  CRAN also continues to build and test once released --- the best
of why knowledge would be encoded on src/Makevars.win.  And as you can see
there are no particular switches. 

Can you remind me what the issue is, then?   Boost usage from R tends to
issue copious __warnings__ about long long but still builds.  I may have been
refering to suppressing the warning by turning on C++11, but I am not doing
that yet for RQuantLib.

Hope this clarifies things and helps,  Dirk



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


More information about the Rquantlib-devel mailing list