I apologize for the ambiguous subject; I could not think of a more accurate one. Updating packages reported that 'later' did not build, but I did not see which dependency needs updating. Looking at the CRAN page for this package I see potentials and would like advice on which are the ones needing explicit updating: LinkingTo: Rcpp, BH Suggests: knitr, rmarkdown, testthat ... Reverse imports: eplusr, fiery, httpuv, pool, promises, shiny Reverse linking to: httpuv, promises Reverse suggests: blogdown, servr Learning which package(s) need to be rebuilt here for 'later' will help me the next time I encounter this situaion. TIA, Rich
>>>>> Rich Shepard >>>>> on Sun, 24 Feb 2019 11:08:43 -0800 writes:> I apologize for the ambiguous subject; I could not think of a more accurate > one. > Updating packages reported that 'later' did not build, but I did not see > which dependency needs updating. Looking at the CRAN page for this package I > see potentials and would like advice on which are the ones needing explicit > updating: > LinkingTo: Rcpp, BH > Suggests: knitr, rmarkdown, testthat > ... > Reverse imports: eplusr, fiery, httpuv, pool, promises, shiny > Reverse linking to: httpuv, promises > Reverse suggests: blogdown, servr I'm not the expert on these problems, but as nobody else has replied: My experience is that both Rcpp and BH need "often" to be re-installed if your system updates in some way. IIUC, 'LinkingTo:' is actually a misnomer (as e.g. the Rcpp maintainer has known and told us about often enough), here, because it's more a "including C++ header templates from" So, I'd re-install first Rcpp, then BH, and then "your" package. Please let us (= the audience) know if that helped. Best, Martin > Learning which package(s) need to be rebuilt here for 'later' will help me > the next time I encounter this situaion. > TIA, > Rich > ______________________________________________ > R-help at r-project.org mailing list -- To UNSUBSCRIBE and more, see > https://stat.ethz.ch/mailman/listinfo/r-help > PLEASE do read the posting guide http://www.R-project.org/posting-guide.html > and provide commented, minimal, self-contained, reproducible code.
On Tue, 26 Feb 2019, Martin Maechler wrote:> I'm not the expert on these problems, but as nobody else has > replied:Martin, Thanks for responding.> My experience is that both Rcpp and BH need "often" to be re-installed if > your system updates in some way. IIUC, 'LinkingTo:' is actually a misnomer > (as e.g. the Rcpp maintainer has known and told us about often enough), > here, because it's more a "including C++ header templates from" > > So, I'd re-install first Rcpp, then BH, and then "your" > package.Did this, and ...> Please let us (= the audience) know if that helped.there's still an unresolved issue with package 'later': ** testing if installed package can be loaded Error: package or namespace load failed for ?later? in dyn.load(file, DLLpath = DLLpath, ...): unable to load shared object '/usr/lib/R/library/later/libs/later.so': /usr/lib/R/library/later/libs/later.so: undefined symbol: __atomic_fetch_add_8 Error: loading failed Execution halted ERROR: loading failed * removing ?/usr/lib/R/library/later? * restoring previous ?/usr/lib/R/library/later? I urge everyone with more ideas to share them. Regards, Rich
On Wed, 27 Feb 2019, Rainer Krug wrote:> I am sure, you have uninstalled the package completely and tried it again? > > Have you tried at looking at the shared objects required by ` > /usr/lib/R/library/later/libs/later.so` using ldd ? > > I had similar problems on Mac (with other packages) and re-installing some > home-brew packages fixed it.Rainer, In truth, I've ignored the issue for now. :-) Regardless, I will take your advice and report results when completed. Thanks very much, Rich
On Wed, 27 Feb 2019, Rainer Krug wrote:> I am sure, you have uninstalled the package completely and tried it again?Rainer, Yes. Just did so with the same result: R could not load the shared library.> Have you tried at looking at the shared objects required by > `/usr/lib/R/library/later/libs/later.so` using ldd ?Because later was removed and could not be rebuilt, there is no later.so to be queried for dependencies. I'll look again at later's dependencies and ensure they're all rebuilt. Regards, Rich
Add the --no-test-load option to the install command and the unloadable .so file should be left there so you can look at its dependencies with, e.g., 'R CMD ldd .../libs/later.so'. Bill Dunlap TIBCO Software wdunlap tibco.com On Wed, Feb 27, 2019 at 9:40 AM Rich Shepard <rshepard at appl-ecosys.com> wrote:> On Wed, 27 Feb 2019, Rainer Krug wrote: > > > I am sure, you have uninstalled the package completely and tried it > again? > > Rainer, > > Yes. Just did so with the same result: R could not load the shared library. > > > Have you tried at looking at the shared objects required by > > `/usr/lib/R/library/later/libs/later.so` using ldd ? > > Because later was removed and could not be rebuilt, there is no later.so to > be queried for dependencies. > > I'll look again at later's dependencies and ensure they're all rebuilt. > > Regards, > > Rich > > ______________________________________________ > R-help at r-project.org mailing list -- To UNSUBSCRIBE and more, see > https://stat.ethz.ch/mailman/listinfo/r-help > PLEASE do read the posting guide > http://www.R-project.org/posting-guide.html > and provide commented, minimal, self-contained, reproducible code. >[[alternative HTML version deleted]]