similar to: Sections 5.8.1 and 5.8.2 of Writing R Extensions (LinkingTo)

hello how to solve these errors /var/lib/asterisk/agi-bin/agi-rad-auth.pl line 10 use Asterisk::AGI; vi /etc/asterisk/extensions.conf exten => _X.,1,agi,agi-rad-auth.pl|Routing=SIP&AuthorizeBy=SIP vi /etc/asterisk/modules.conf load => res_agi.so <---------------errors------------------------> *CLI> Can't locate Asterisk/AGI.pm in @INC (@INC contains:

I'm trying to use nmap2nagios (a perl script) on CentOS, but when I run it, I get the following error: (If this is offtopic for this list, please let me know) ./nmap2nagios.pl -v -r /tmp/nmap.xml -o /tmp/new.cfg ./nmap2nagios.pl: line 9: use: command not found ./nmap2nagios.pl: line 10: use: command not found ./nmap2nagios.pl: line 11: use: command not found ./nmap2nagios.pl: line 14: use:

Hello, I am observing the following strange behavior when I try to load a shared library using dyn.load() under Linux... The library foo.so refers to a symbol in another package bar (with shared library bar.so), I get: dyn.load('foo.so') # error message because I forgot to load bar library(bar) # so I fix it dyn.load('foo.so') # works this time and everything is fine But, if

when I issue a command to populate my ldap directory I receive an erro cant find Net/SSleay.pm how can I find an Net:SSleay rpm to install on FC3 -------------- next part -------------- [root@matrix ~]# smbldap-populate Using builtin directory structure Can't locate Net/SSLeay.pm in @INC (@INC contains: /usr/local/sbin// /usr/lib/perl5/5.8.5/i386-linux-thread-multi /usr/lib/perl5/5.8.5

When trying to run a Perl program, I get this error (even though I have both Perl and perl-net-dns installed via yum) Can't locate Net/DNS.pm in @INC (@INC contains: /usr/lib/nagios/plugins /usr/lib/perl5/5.8.5/i386-linux-thread-multi /usr/lib/perl5/5.8.5 /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.4/i386-linux-thread-multi

Hello, I am encountering problems when there is a '%' character in package .Rd files. More precisely, CRAN is having problems with these characters when running check, whereas I am not seeing any problems under Linux and Windows. I did see these problems, and found that escaping the %'s fixes the problem in my testing, but apparently this does not fix the problem when check is run at

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.,

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:

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

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 > | saying "I'm using Rcpp interface 0.12.8".

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 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 > | > | C-level entry points either guarantee them not to change or offer

I've got httpd and mod_perl installed, but I seem to have an application that requires part of mod_perl that doesn't seem to be properly installed into perl, notably, the 'Apache' portion. To 'fix' this, cpan would like to install either mod_perl-1.29, or alternatively to install mod_perl-2.0.2. 1.29 doesn't seem smart, and 2.0.2 absolutely will not install over the

Hello List, I have a few intel centos 3.9 boxes with perl-5.8.0-94.EL3 installed. This seems like a very early version of 5.8 perl. centos 4.6 has 5.8.1. Would it be sensible to just upgrade to this rpm? I want a stable platform for cgi. I suppose I could just try it, but these boxes are under a form of change control and I think I should ask for advice before going that route. Many thanks for

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

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 IIUC. - If we're looking into a way to check if package APIs are

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

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 | saying "I'm using Rcpp interface 0.12.8". If Rcpp has a new version | with a compatible interface, it replies

Full_Name: Eric van Gyzen Version: 1.8.1 OS: FreeBSD 5.1-RELEASE Submission from: (NULL) (152.3.22.120) After updating perl from 5.6.1 to 5.8.2, R no longer builds. Also note that the build continued even after the failure. Is that a bug or a feature? ================================================================================ >>> Building/Updating help pages for package