Re: [R-pkg-devel] truncating strings on purpose

2024-12-13 Thread Brad Eck
stions are also welcome. Brad On Wed, Dec 11, 2024 at 1:29 PM Ivan Krylov wrote: > В Wed, 11 Dec 2024 12:12:11 + > Brad Eck пишет: > > > Found the following significant warnings: > > input2.c:863:5: warning: ‘__builtin_strncpy’ output may be > > truncated cop

[R-pkg-devel] duplicating gcc-UBSAN warning

2024-12-12 Thread Brad Eck
Dear List I'm trying to duplicate a warning CRAN is seeing on the additional checks for gcc-UBSAN. That is using: CRAN's gcc-UBSAN: * using R Under development (unstable) (2024-12-04 r87420) * using platform: x86_64-pc-linux-gnu * R was compiled by gcc-14 (GCC) 14.2.0 GNU Fortran (GCC) 1

[R-pkg-devel] truncating strings on purpose

2024-12-11 Thread Brad Eck
Dear List The latest update to my epanet2toolkit package bounced from CRAN due to some warnings about string truncation in C code from gcc. Found the following significant warnings: input2.c:863:5: warning: ‘__builtin_strncpy’ output may be truncated copying 225 bytes from a string of length

Re: [R-pkg-devel] gcc14 checks on fedora

2024-05-27 Thread Brad Eck
the > `-Wformat-truncation=` flag with the compiler you have, it is possible > that you don't need gcc 14.1. If you do, then the `fedora:40` > container should be good. > > Gabor > > On Fri, May 24, 2024 at 9:02 PM Brad Eck wrote: > > > > Dear List -

[R-pkg-devel] gcc14 checks on fedora

2024-05-24 Thread Brad Eck
Dear List - I received a note that my package -- epanet2toolkit -- was showing a warning in the fedora-gcc results on CRAN. https://www.stats.ox.ac.uk/pub/bdr/gcc12/epanet2toolkit.out I'd like to reproduce the warning and fix it. Usually I'd do that with Docker. Is anyone aware of a docker imag

Re: [R-pkg-devel] tinyfiledialogs - The bindings are ready, but I need help to make of package of it

2023-09-22 Thread Brad Eck
Dear Guillaume - Here is a minimal example of an R package that uses C source: https://github.com/bradleyjeck/fancyRpkg As the timestamps show, I made this a few years ago, so some things might not conform to the current version of Writing R Extensions. But it should get you started. The motiva

[R-pkg-devel] reproducing cran warnings

2023-02-03 Thread Brad Eck
Dear List - What’s the latest best practice on trying to reproduce warnings raised on CRAN checks? I updated my epanet2toolkit package earlier this week. R CMD check —as-cran was clean on RHUB and Winbuilder and my local machines. But on CRAN a few variations are causing warnings. For example R

Re: [R-pkg-devel] compiling C sources on windows

2021-04-19 Thread Brad Eck
t; If you need to test locally on Windows, there are free virtual > machines available here: > https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/ > > Best, > Kevin > > On Mon, Apr 19, 2021 at 2:14 AM Brad Eck wrote: > > > > Dear List - > > >

[R-pkg-devel] compiling C sources on windows

2021-04-19 Thread Brad Eck
Dear List - I'm working to get a package of mine that was archived last year back on to CRAN. The epanet2toolkit provides an R interface to the EPANET simulation engine that is written in C. The latest development version of the package builds and checks ok on mac and linux but fails to compile a

Re: [R-pkg-devel] can't reproduce cran-pretest error

2018-07-27 Thread Brad Eck
t; > https://github.com/bradleyjeck/epanet2toolkit/blob/ > ef66748de5b357bfe6bbad4b3ba7e5f271baa797/src/Repanet2.c#L81 > > This more or less matches the error shown in the pre-test, i.e.: > > "array over-run in .C("RENgettimeparam") in character argument 2, element &

[R-pkg-devel] can't reproduce cran-pretest error

2018-07-26 Thread Brad Eck
Dear list, I'm having trouble reproducing errors from CRAN's pretests. I have a package on CRAN called epanet2toolkit that provides R bindings to a legacy simulation engine written in C. So far I've released two versions to CRAN without trouble. Now I'm making a third release, principally to in