cran-comments.md

## Test environments
  
* Linux: Ubuntu 18.04.4LTS  (local)
  - R 3.6.3 (production)
  - R 4.2.3 patched (2023-03-29 r84146) (test)
  - R devel (2023-04-02 r84146) (test)
* Windows 7 Enterprise
  - R version 4.2.2 (2022-10-31 ucrt) (test)

  
## R CMD check results
  
  0 ERRORS
  0 WARNINGS
  1 NOTES (new resubmission after archiving)
  
  
## This is a resubmission, after archiving on 2023-04-05

Request from 2023-03-19. All calls to .C() are now explicitly pointing
to symbols instead of function namestrings. Package "gmGeostats" could 
not be uploaded before the archiving deadline because the main dependence 
"compositions" was showing problems as well. 

```
Dear maintainer,

Please see the problems shown on
<https://cran.r-project.org/web/checks/check_results_gmGeostats.html>.

The "DLL requires the use of native symbols" errors in the
r-devel-linux-x86_64-debian-gcc check results are from

r83985 | luke | 2023-03-16 02:31:57 +0100 (Thu, 16 Mar 2023) | 3 lines
Enforce R_forceSymbols for namespaces, but for now only if an
environment variable is set.

which makes R_forceSymbols work correctly, for now provided that env var
R_REALLY_FORCE_SYMBOLS is set.

You can conveniently extract the non-symbols in your package's foreign
function calls via tools:::package_native_routine_registration_db(),
e.g.,

R> tools:::package_native_routine_registration_db("/data/rsync/PKGS/tibble")
  cname                  s n
1 .Call tibble_need_coerce 1

but please note that there may be several such calls in your code.

Please correct before 2023-04-02 to safely retain your package on CRAN.

Best,
-k
```