Re: [R-pkg-devel] [Re] warning: type of ‘zhpevx_’ does not match original declaration [-Wlto-type-mismatch]

2020-12-17 Thread Ivan Krylov
Dear Pierre L., I think that the zhpevxC wrapper, as written, may result in undefined behaviour: >const char *JOBZ = jobz[0]; >delete[] JOBZ; >delete[] Cap; This could work okay, depending on how the rest of the package is written, but in general, it is considered a bad idea for

Re: [R-pkg-devel] [Re] warning: type of ‘zhpevx_’ does not match original declaration [-Wlto-type-mismatch]

2020-12-17 Thread Pierre Lafaye de Micheaux
Of course, I meant: double _Complex *Cap; memcpy(, , sizeof(ap)); and not double _Complex *Cap; memcpy(, , sizeof(ap)); Best regards, Pierre From: R-package-devel on behalf of Pierre Lafaye de Micheaux Sent: Friday, 18 December 2020 16:15 To:

[R-pkg-devel] [Re] warning: type of ‘zhpevx_’ does not match original declaration [-Wlto-type-mismatch]

2020-12-17 Thread Pierre Lafaye de Micheaux
Dear Tomas, Thank you very much for your feedback. This was really helpful and helped me to find a solution. Even if it is not entirely satisfactory to me (in the sense that I now create new extra pointers which will take unnecessary space in memory), at least the LTO errors are not displayed

Re: [R-pkg-devel] Used package not updated - needs java < V 11

2020-12-17 Thread Knut Krueger
Am 16.12.20 um 16:57 schrieb Duncan Murdoch: > No, you should drop the @importFrom comment completely, and in your R > code use those fully qualified forms. > > Duncan Murdoch Sorry I did not read carefully Knut __ R-package-devel@r-project.org

Re: [R-pkg-devel] Used package not updated - needs java < V 11

2020-12-17 Thread Knut Krueger
  Also, I received an email from CRAN maintainers months ago saying that "gdata" was being obsoleted.  It's still on CRAN with a date of 2017-06-06 and a huge number of reverse dependencies.  The CRAN maintainers may have gotten someone to agree to take it over who just hasn't

Re: [R-pkg-devel] Used package not updated - needs java < V 11

2020-12-17 Thread Spencer Graves
On 2020-12-17 12:22, Knut Krueger wrote:    Also, I received an email from CRAN maintainers months ago saying that "gdata" was being obsoleted.  It's still on CRAN with a date of 2017-06-06 and a huge number of reverse dependencies.  The CRAN maintainers may have gotten someone to

Re: [R-pkg-devel] Package Encoding and Literal Strings

2020-12-17 Thread jo...@jorisgoosen.nl
On Thu, 17 Dec 2020 at 18:22, Tomas Kalibera wrote: > On 12/17/20 5:17 PM, jo...@jorisgoosen.nl wrote: > > > > On Thu, 17 Dec 2020 at 10:46, Tomas Kalibera > wrote: > >> On 12/16/20 11:07 PM, jo...@jorisgoosen.nl wrote: >> > David, >> > >> > Thanks for the response! >> > >> > So the problem is

Re: [R-pkg-devel] Package Encoding and Literal Strings

2020-12-17 Thread Tomas Kalibera
On 12/17/20 5:17 PM, jo...@jorisgoosen.nl wrote: > > > On Thu, 17 Dec 2020 at 10:46, Tomas Kalibera > wrote: > > On 12/16/20 11:07 PM, jo...@jorisgoosen.nl > wrote: > > David, > > > > Thanks for the response! >

Re: [R-pkg-devel] Package Encoding and Literal Strings

2020-12-17 Thread jo...@jorisgoosen.nl
Ps. I will try to have a go at using your experimental version to see if that could help us out. If I run into trouble I will mail you personally. On Thu, 17 Dec 2020 at 17:17, jo...@jorisgoosen.nl wrote: > > > On Thu, 17 Dec 2020 at 10:46, Tomas Kalibera > wrote: > >> On 12/16/20 11:07 PM,

Re: [R-pkg-devel] unexpected CRAN pretest failure

2020-12-17 Thread Joshua Ulrich
On Thu, Dec 17, 2020 at 7:25 AM Rossum, Bart-Jan van wrote: > > Dear Uwe, > > Thanks for your reaction. > I installed the latest available R-devel version (2020-12-15 r79633) on my > own windows pc, but even then the checks pas cleanly. > So, unfortunately I'm not able to reproduce the issue. >

Re: [R-pkg-devel] Package Encoding and Literal Strings

2020-12-17 Thread jo...@jorisgoosen.nl
On Thu, 17 Dec 2020 at 10:46, Tomas Kalibera wrote: > On 12/16/20 11:07 PM, jo...@jorisgoosen.nl wrote: > > David, > > > > Thanks for the response! > > > > So the problem is a bit worse then just setting `encoding="UTF-8"` on > > functions like readLines. > > I'll describe our setup a bit: > >

Re: [R-pkg-devel] unexpected CRAN pretest failure

2020-12-17 Thread Rossum, Bart-Jan van
Dear Uwe, Thanks for your reaction. I installed the latest available R-devel version (2020-12-15 r79633) on my own windows pc, but even then the checks pas cleanly. So, unfortunately I'm not able to reproduce the issue. To be sure, I also retried on Winbuilder, which has a slightly different

Re: [R-pkg-devel] unexpected CRAN pretest failure

2020-12-17 Thread Uwe Ligges
This is form a change in R-devel. Use a more recent R-devel to reproduce the issue. Best, Uwe Ligges On 14.12.2020 15:02, Rossum, Bart-Jan van wrote: Dear community, When trying to update my CRAN (https://cran.r-project.org/web/packages/statgenGxE/index.html) package in ran into unexpected

Re: [R-pkg-devel] R CMD check error on Windows

2020-12-17 Thread Akshit Achara
Dear Uwe, Thank you very much for the explanation. Regards, Akshit Achara On Thu, Dec 17, 2020 at 3:32 PM Uwe Ligges wrote: > > > On 17.12.2020 10:39, Akshit Achara wrote: > > Dear Uwe, > > > > Can you please elaborate? > > > > I generated the configure script from configure.ac

Re: [R-pkg-devel] R CMD check error on Windows

2020-12-17 Thread Uwe Ligges
On 17.12.2020 10:39, Akshit Achara wrote: Dear Uwe, Can you please elaborate? I generated the configure script from configure.ac on Linux and copied it's contents to configure.win (changed ~! /bin/sh to #! /bin/bash). Does it cause any quoting issues? Well, R >

Re: [R-pkg-devel] Package Encoding and Literal Strings

2020-12-17 Thread Tomas Kalibera
On 12/16/20 11:07 PM, jo...@jorisgoosen.nl wrote: David, Thanks for the response! So the problem is a bit worse then just setting `encoding="UTF-8"` on functions like readLines. I'll describe our setup a bit: So we run R embedded in a separate executable and through a whole bunch of C(++)

Re: [R-pkg-devel] R CMD check error on Windows

2020-12-17 Thread Akshit Achara
Dear Uwe, Can you please elaborate? I generated the configure script from configure.ac on Linux and copied it's contents to configure.win (changed ~! /bin/sh to #! /bin/bash). Does it cause any quoting issues? Thanks, Akshit Achara On Thu, Dec 17, 2020 at 3:01 PM Uwe Ligges wrote: > > > On

Re: [R-pkg-devel] R CMD check error on Windows

2020-12-17 Thread Uwe Ligges
On 17.12.2020 10:26, Akshit Achara wrote: Dear Sir, I got this error on rminizinc cran checks for r-oldrel-windows-ix86+x86_64: (The package needs to run ./configure.win during installation) exec: /cygdrive/c/Program: not

[R-pkg-devel] R CMD check error on Windows

2020-12-17 Thread Akshit Achara
Dear Sir, I got this error on rminizinc cran checks for r-oldrel-windows-ix86+x86_64: (The package needs to run ./configure.win during installation) exec: /cygdrive/c/Program: not found Warning in system("sh ./configure.win")