On 12/02/2016 11:57, Dirk Eddelbuettel wrote:
On 11 February 2016 at 17:42, Dirk Eddelbuettel wrote:
|
| On 11 February 2016 at 15:02, Kevin Ushey wrote:
| | I think this needs to be _WIN32 rather than WIN32. Thanks for pointing this
out!
|
| Could well be. That (IIRC) changed recently so could
On 11 February 2016 at 17:42, Dirk Eddelbuettel wrote:
|
| On 11 February 2016 at 15:02, Kevin Ushey wrote:
| | I think this needs to be _WIN32 rather than WIN32. Thanks for pointing this
out!
|
| Could well be. That (IIRC) changed recently so could you (ie Jonathon) try it
| with _WIN32 and re
On 11 February 2016 at 15:02, Kevin Ushey wrote:
| I think this needs to be _WIN32 rather than WIN32. Thanks for pointing this
out!
Could well be. That (IIRC) changed recently so could you (ie Jonathon) try it
with _WIN32 and report back and/or supply a PR?
Dirk
|
| On Thu, Feb 11, 2016 at 2:
I think this needs to be _WIN32 rather than WIN32. Thanks for pointing this out!
On Thu, Feb 11, 2016 at 2:41 PM, Jonathon Love wrote:
> hi dirk,
>
> i've been compiling RInside on windows with the new RTools based on GCC 4.9.
> with stock settings, this all compiles successfully.
>
> however, if
hi dirk,
i've been compiling RInside on windows with the new RTools based on GCC
4.9. with stock settings, this all compiles successfully.
however, if i add "-std=c++11" to CXX_FLAGS, then the compilation fails.
it chokes on line 27 of RInside.cpp [1]. what makes this more
interesting is tha
