similar to: LinkingTo for 2 packages

Hello, I have a situation where I have numerous files with numerous hard links to each of them on an ext3 RHEL4.2 system. Some of these files are duplicates of the others. I would like to re-link all of the duplicates to point to a single inode. For instance if file1 has hardlinks link1 and link2, and file2 has hardlinks link3 and link4, I need to change it so that link1, link2 (these

Thanks, Vedant. Yes, we have done a lot of testing of Clang/LLVM (and GCC) in the past several years (more details at https://people.inf.ethz.ch/suz/emi/index.html): [GCC/LLVM bugs: *1,602* (total) / *1,007* (fixed)] [Reports: GCC (link1 <http://tinyurl.com/ojzdt78>, link2 <http://tinyurl.com/oxlkmjc>, link3 <http://tinyurl.com/jd3jnl3>, link4

You may also be interested in the following resources on compilers correctness (articles, software, and talks -- from the general topics to the ones specifically focused on testing, validation, and verification): https://github.com/MattPD/cpplinks/blob/master/compilers.correctness.md Best regards, Matt P. Dziubinski On 12/7/2018 20:19, Philip Reames via llvm-dev wrote: > There's also

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

hi, i am using devise gem in my app for authentication. if i enter link1 -> http://localhost:3000/users/sign_in, once i login, it will be redirected to link2 -> http://localhost:3000/user/dashboard. if i can add new posts or comments for that user using this link link3 -> http://localhost:3000/community_managers/posts/new/2/Facebook lets say i am using

Dear all, We are experiencing some trouble when compiling R packages using R 2.6.0 and the new Rtools installer under Windows XP. (1) First, compiling any package using the new setup stops with an errorrelated to some "/" issue on the inst folder. This folder only contains a CITATION file ---------- Making package FLCore ------------ adding build stamp to DESCRIPTION installing

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

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: A" in its description. To illustrate the problem, assume package A is updated so that its C/C++ header interface (in inst/include) is changed. For package B to pick up these changes, we need to reinstall package A. In extreme cases, if

Hi, I'm trying to develop an histogram method for a class called "FLQuant" which is used by the package FLCore (http://flr-project.org). FLQuant is an extension to "array". There is an as.data.frame method that coerces flquant into a data.frame suitable for lattice plotting. The problem is that when I coerce the object and plot it after it works but if the method is

Hi, I'm trying to develop an histogram method for a class called "FLQuant" which is used by the package FLCore (http://flr-project.org). FLQuant is an extension to "array". There is an as.data.frame method that coerces flquant into a data.frame suitable for lattice plotting. The problem is that when I coerce the object and plot it after it works but if the method is

On 16/12/2016 12:35 PM, Karl Millar wrote: > A couple of points: > - rebuilding dependent packages is needed if there is an ABI change, > not just an API change. For packages like Rcpp which export inline > functions or macros that might have changed, this is potentially any > change to existing functions, but for packages like Matrix, it isn't > really an issue at all

I am experimenting with exporting pointers to some of the functions in deSolve so that other packages may import them, using the 'R_RegisterCCallable' mechanism. I have added a header file and some other C code in inst/include of the deSolve source package that need to be accessible to other packages. I have a site-library set up in Rprofile.site where all installed packages go, and as

On 16 December 2016 at 10:14, Duncan Murdoch wrote: | On 16/12/2016 8:37 AM, Dirk Eddelbuettel wrote: | > | > On 16 December 2016 at 08:20, Duncan Murdoch wrote: | > | Perhaps the solution is to recommend that packages which export their | > | C-level entry points either guarantee them not to change or offer | > | (require?) version checks by user code. So dplyr should start out by

Hi, Which version of Mac OS X are you running? If you are on Mac OS 10.5.x then I can only suggest that you try either formating the drive to HFS + or creating a disk image with an HFS+ file system. If you are running Mac OS 10.4.x then ensure that that ACL support is enabled on the drive. The following URL contains information on how to check and enable ACL support :

Hi, I'm writing some functions to generate Rd files for a S4 package. I want to have 2 character vectors with the names of the S4 classes and the methods exported by a package. To get the info about methods I'm using "getGenerics(where="package:FLCore")" however I can not find a similar process to get the S4 classes. Are there functions to access this information

On 16 December 2016 at 11:00, Duncan Murdoch wrote: | On 16/12/2016 10:40 AM, Dirk Eddelbuettel wrote: | > On 16 December 2016 at 10:14, Duncan Murdoch wrote: | > | On 16/12/2016 8:37 AM, Dirk Eddelbuettel wrote: | > | > | > | > On 16 December 2016 at 08:20, Duncan Murdoch wrote: | > | > | Perhaps the solution is to recommend that packages which export their | > | > |

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

Hi everyone, Some of you probably received the following thread from the Rcpp-devel mailing list: http://lists.r-forge.r-project.org/pipermail/rcpp-devel/2018-August/010072.html Summing up, the issue described is the following: pkg1 provides type1 in pkg1.so building on some headers. pkg2 links to pkg1 (BTW, LinkingTo is actually misleading, because it doesn't really link to it), i.e.,

Hello, I'm setting up a system for automated synchronization and backup between different macs (OS X Lion 10.7). I use HFS+ Journaled as filesystem. I wanted to follow these guidelines: http://www.bombich.com/rsync.html but I gave a look inside the patches Mr. Bombich suggested and I thought I could try first by using only the normal ones provided by rsync.samba.org, so I skipped curl -o

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: