Re: [R-pkg-devel] Rcpp with clang++ -stdlib=libc++ ?

2020-09-13 Thread Dr . Jens Oehlschlägel
s worth being aware of. > > Best, > Kevin > > On Sat, Sep 12, 2020 at 5:50 AM Dirk Eddelbuettel <mailto:e...@debian.org>> wrote: > > > Hi Jens, > > On 11 September 2020 at 21:00, Dr. Jens Oehlschlägel wrote: > | I can compile a package

[R-pkg-devel] Rcpp with clang++ -stdlib=libc++ ?

2020-09-11 Thread Dr . Jens Oehlschlägel
I can compile a package under clang++ with -stdlib=libstdc++, but with -stdlib=libc++ I get " In file included from /home/jo/R/x86_64-pc-linux-gnu-library/4.0/Rcpp/include/Rcpp/r/headers.h:67: /home/jo/R/x86_64-pc-linux-gnu-library/4.0/Rcpp/include/Rcpp/platform/compiler.h:100:10: fatal error:

[R-pkg-devel] need help to identify ff error on r-oldrel-macos-x86_64

2020-08-24 Thread Dr . Jens Oehlschlägel
Dear Mac users, Can someone of you identify the cause of the problem in https://www.r-project.org/nosvn/R.check/r-oldrel-macos-x86_64/ff-00check.html I can't because I don't have access to a Mac. It seems that gc() after rm(ffobject) does not remove the ff file in rows (@test-zero_lengths.R#34

Re: [R-pkg-devel] Package can't be imported with Suggests

2020-08-06 Thread Dr . Jens Oehlschlägel
Dirk, This sounds familiar: in package 'bit' for bit | bitwhich R did neither S3-dispatch to "|.bit" nor to "|.bitwhich" but nonsensically to the default method. It took me a while to reverse my class thinking enough to realize that I could get control by forcing dispatch to a common clas

Re: [R-pkg-devel] check cross-references error: Non-file package-anchored link(s)

2020-07-02 Thread Dr . Jens Oehlschlägel
sendet: Donnerstag, 02. Juli 2020 um 15:23 Uhr > Von: "Duncan Murdoch" > An: "Dr. Jens Oehlschlägel" , > r-package-devel@r-project.org > Betreff: Re: Aw: Re: Re: [R-pkg-devel] check cross-references error: Non-file > package-anchored link(s) > > On 02

Re: [R-pkg-devel] check cross-references error: Non-file package-anchored link(s)

2020-07-02 Thread Dr . Jens Oehlschlägel
Duncan, > One way is to make bit depend on a particular version of ff. That may > cause a deadlock if both are being updated at once, but I think CRAN > should be able to deal with it if they are informed of the issue. Exactly that I have done: I submitted all three packages bit/bit64/ff in ver

Re: [R-pkg-devel] check cross-references error: Non-file package-anchored link(s)

2020-07-02 Thread Dr . Jens Oehlschlägel
Thanks Gabor and Duncan, > It's actually in ff/man/clone.rd, not clone.ff.rd. There is no > ff/man/clone.ff.rd file. but there *is* clone.ff.rd in the >= 4.0.0 versions of the packages bit/bit64/ff. Hence the check warning is a false alarm resulting from checking bit 4.0.2 (GitHub.com/truecl

Re: [R-pkg-devel] check cross-references error: Non-file package-anchored link(s)

2020-07-01 Thread Dr . Jens Oehlschlägel
Good evening, My package bit 4.0.2 (https://github.com/truecluster/bit) is being rejected by CRAN checks with warning: >Check: Rd cross-references, Result: WARNING > Non-file package-anchored link(s) in documentation object 'clone.Rd': >'[ff]{clone.ff}' > > See section 'Cross-referen