similar to: Consider setting RTLD_GLOBAL when loading packages in LinkingTo

Hi, I have already asked a similar question twice without response on the r-help list https://stat.ethz.ch/pipermail/r-help/2009-June/200300.html but this list might be more appropriate. If there is a particular reason for the lacking answers (unclear, missing information, the solution is obvious to everyone except me, etc), I would like to know. The description below is generalized, but I

Hi, I have already asked a similar question without response (https://stat.ethz.ch/pipermail/r-help/2009-June/200300.html) so I am here reformulating in the hope that someone is able to help. If something is unclear, please ask. I am working on the development of two packages, pkg1 and pkg2 (based on work in two different projects). pkg1 is quite generic, pkg2 tries to solve a particular

Hi, I am currently involved in the development of two R-packages, pkg1 and pkg2. They should not be dependent on each other, as most users will only be interested in one of them. Still, I want pkg2 to provide one extra S3 method for three functions (fun1-3) in pkg1 for objects of a class defined in pkg2 (class2), for those users who actually have both packages installed. I think this

Dear R devels, let's say I have three packages "pkg1", "pkg2" and "pkg3" which all contain new S4 classes and methods. Where "pkg3" depends on "pkg2" and "pkg2" depends on "pkg1". Moreover, all three packages have namespaces. 1) I use ".onLoad <- function(lib, pkg) require(methods)". Do I also have to

Hi, I want to cross-reference from the documentation of pkg1 to pkg2, which is imported in the NAMESPACE of pkg1, and under Depends in DESCRIPTION of pkg1. According to "Writing R extensions", this can be done by: \code{\link{foo}} when foo is an aliased function in the documentation of pkg2. This works as it should when I install the package, but when I run R CMD check pgk1, I get

I am trying to re-organizing my Makefile for testing my R packages and I am having trouble finding a structure I like. The problem seems to be that "R CMD check", which does wonderful things, does not allow dependency information to flow through very gracefully. That is, since everything is copied into the pkg.Rcheck directory, it is difficult to make any changes to source files without

Hi, I have built two R packages. One of them (PKG1) needs to use the functions of the other package (PKG2). So I need to link these two packages together, so that the functions of PKG2 can be available to PKG1. And when I load one package using 'library("PKG1")', PKG2 can be loaded at the same. Any ideas welcome. -- View this message in context:

I am being asked to modernize the Depends line in the DESCRIPTION file of some packages. Writing R Extensions says: The general rules are Packages whose namespace only is needed to load the package using library(pkgname) must be listed in the ?Imports? field and not in the ?Depends? field. Packages listed in imports or importFrom directives in the NAMESPACE file should

Hello, unfortunately I had to compile latest version of R-2.0.1 by myself. I'd rather would prefer vendors binaries but since the current version of Ubuntu defaults to 1.9.x I had to compile R on my own in order to be up to date! So far, everything went fine and R runs smoothly. Unfortunately I am not able to use R CMD INSTALL command to install add-on packages. I followed RNews 3/3 and

I am just experimenting with a plugin loader and I found that there are problems with external symbols which are loaded at runtime. The solution is to add RTLD_GLOBAL to the dlopen mode, but I am not sure if this would cause other problems. Is this patch OK to go in? -------------- next part -------------- A non-text attachment was scrubbed... Name: rtld_global.diff Type: text/x-patch Size:

CanUse? If the 'Suggests' field "lists packages that are not necessarily needed" (Writing R Extensions), then why is the user required to have the package installed to pass R CMD check? Likewise, if a CanMakeUseOf field is added, then why would one choose to use Suggests at all? That is, is there an advantage to requiring that the user have a package available (to pass R CMD

Hi, Today, I've made the transition from LLVM 2.1 to 2.3. I invoke opt with two dynamic libraries to "-load", the first of which contains transformation passes and support code whereas the second one provides extra passes which make use of the first library's support code. In other words, the symbols loaded in for the first library should be available when the second

Hello, One of our packages contains C++ code that needs to be compiled against 2 other packages. So the LinkingTo field in DESCRIPTION looks like this LinkingTo: FLCore,FLash Both packages are also in the Depends field. In R 2.6.2, first thing we noticed was that both names could not have any space between them, althoguh the example in the html version of "Writing R Extensions" does

On Wed, 9 Jul 2008, Bram Adams wrote: > Today, I've made the transition from LLVM 2.1 to 2.3. I invoke opt > with two dynamic libraries to "-load", the first of which contains > transformation passes and support code whereas the second one provides > extra passes which make use of the first library's support code. In > other words, the symbols loaded in for the

All, I use a code which has a python (I use python36) wrapper loading shared libraries. The code worked fine in RHEL 7 but as I was testing it on Centos 8, python cannot import the shared library (the import is done via dlopen with flags set as > sys.setdlopenflags(os.RTLD_LAZY | os.RTLD_GLOBAL) python then does a bunch of imports and most results in a shared library with indefined

Hello, I've been trying to make LinkingTo work when the package linked to has c++ code. I've put dumb packages to illustrate this emails here ; http://addictedtor.free.fr/misc/linkingto Package A defines this C++ class: class A { public: A() ; ~A() ; SEXP hello() ; } ; Package B has this function : SEXP say_hello(){ A a ; return a.hello() ; } headers of package A are copied

I think that this problem is actually more general than just ABI versioning. The common definition of ABI refers to compiled code, but with R packages similar problems might happen (and they to happen) without any compiled code. I think the key issue is the concept of build-time dependencies. While R packages usually does not distinguish between build-time and run-time dependencies, they still do

I think there's one typo in your post which may confuse some readers; I've edited it inline below. My comments on the suggestion are at the bottom of the message. On 16/12/2016 5:35 AM, Kirill M?ller wrote: > Hi > > > I'd like to suggest to make R more informative when a user updates a > package A where there's at least one package B that has "LinkingTo:

i am able to install zip files of packages from local zip files using the file.choose() for the package argument in install.packages() function in R console and also from the Packages menu>install from local zip files. But if there are many packages to install (say >15 or 20), then i have to factor in dependencies of 15-20 packages which may be more than 100 or 200 packages in all to be

Dear List, R packages may specify a "LinkingTo" attribute to specify dependencies to the source code (mainly the header files) of other packages. Unfortunately, it is not possible to also have a reference to the generated library (.dll on Windows) of the other package. So including a header file from another package to call an (exported) function will just not help. I've tried