Oh, I receive emails from the list again. Nice.
On Tue, 1 Nov 2022 at 03:58, Dirk Eddelbuettel wrote:
>
> On 31 October 2022 at 11:01, Kevin Ushey wrote:
> | For posterity, what machine are you compiling the package on? If you're
> | using a modern Linux system, it's possible the default
On 31 October 2022 at 11:01, Kevin Ushey wrote:
| For posterity, what machine are you compiling the package on? If you're
| using a modern Linux system, it's possible the default compilation flags
| are including stack protection code during compilation that might call
| abort on error. See e.g.
For posterity, what machine are you compiling the package on? If you're
using a modern Linux system, it's possible the default compilation flags
are including stack protection code during compilation that might call
abort on error. See e.g.
Dear Dirk:
Thank you very much for your extremely quick response.
I have cheked with R CMD build + R CMD check, as you suggested,
and I have found the error.
The call to abort is still present with R CMD check but, when I
copy the code in another machine which I have not yet
On 29 October 2022 at 20:41, Juan Domingo Esteve wrote:
| I am new to this list and I am using Rcpp for my first large and serious
package, so
No worries. "By construction" we all were at that point at some point in the
past.
| I apologize if probably this is a naive question, but I have
Dear all:
I am new to this list and I am using Rcpp for my first large and serious
package, so
I apologize if probably this is a naive question, but I have browsed the web
and looked
at the stored mail messages of this list from the beginning of this year
without finding
an answer.
My
