Ah, I see. Thanks for the explanation!
Best
Simon
On Jun 5, 2013, at 4:48 PM, Romain Francois wrote:
> The change affects Rcpp, not RcppArmadillo.
>
> Le 05/06/13 16:45, Simon Zehnder a écrit :
>> Hi Romain,
>>
>> is revision 4331 already in RcppArmadillo 3.9.0?
>>
>> Best
>>
>> Simon
>>
Hi Romain,
is revision 4331 already in RcppArmadillo 3.9.0?
Best
Simon
On Jun 5, 2013, at 4:30 PM, Romain Francois wrote:
> Most of these are in fact happening in armadillo's code base.
>
> Le 05/06/13 16:23, Simon Zehnder a écrit :
>> Hi Rcpp-Users and Rcpp-Devels,
>>
>> I just build an R
The change affects Rcpp, not RcppArmadillo.
Le 05/06/13 16:45, Simon Zehnder a écrit :
Hi Romain,
is revision 4331 already in RcppArmadillo 3.9.0?
Best
Simon
On Jun 5, 2013, at 4:30 PM, Romain Francois wrote:
Most of these are in fact happening in armadillo's code base.
Le 05/06/13 16:2
Hi Romain,
thanks for the fast reply! So nothing to worry about. taking flags
"-Wunused-local-typedefs" away from compilation should let the warnings vanish
from output?
Best
Simon
On Jun 5, 2013, at 4:30 PM, Romain Francois wrote:
> Most of these are in fact happening in armadillo's code
Most of these are in fact happening in armadillo's code base.
Le 05/06/13 16:23, Simon Zehnder a écrit :
Hi Rcpp-Users and Rcpp-Devels,
I just build an RcppArmadillo project on my computer using gcc-4.8.1 and the
newest Version of RcppArmadillo. I got some warnings I cannot explain to
myself.
Hi Rcpp-Users and Rcpp-Devels,
I just build an RcppArmadillo project on my computer using gcc-4.8.1 and the
newest Version of RcppArmadillo. I got some warnings I cannot explain to
myself. It builds the library and installs it. Nevertheless I would like to
know more about my warnings:
In file
