similar to: explict sharing of symbols between packages

Displaying 20 results from an estimated 4000 matches similar to: "explict sharing of symbols between packages"

2001 Apr 04
1
Rprintf under windows?
Hi, I've been using Rprintf from a shared library compiled under various unix flavour for a while now. I get a warning about Rprintf being undefined when constructing the library, but everything works OK after loading. I've also been cross compiling the same library using the mingw32 tools for a while now, but the inclusion of Rprintf seems to be messing up this process. It can't
2004 Nov 16
1
Any success with RDCOMServer and R-2.0.0?
Hi Everyone, I'm experimenting with the RDCOMServer package under R-2.0.0. I'm not having much success yet - the methods im registering do show up in the registry but I'm not able to call the using RDCOMClient from another package. I'm still attempting to diagnose my problem in other ways, but though I should check to see if there are any problems have been observed by others
2001 May 28
1
argument names in generic print functions (PR#955)
Hello, I think this is a bug, although it is possible that I'm doind something silly. I want to be able to determine the argument name for variables passed to a generic print function suppose we have print.foo <- function(x, ...) { nm<-deparse(substitute(x)) cat("param name is ", nm, "\n") } d<-structure(1, class="foo") Under R-1.2.[2,3] >
2004 Nov 24
1
R-2.0.1 and Rggobi
Hi, I've had no luck with the combination of R-2.0.1 and Rggobi/gobi (1.1-1 and 1.0-1 beta). I've tried a default configuration of ggobi, as well as one with all the plugins enabled. I'm using RedHat 9 Linux. The problem I'm experiencing is a segmentation fault when library.dynam is called from .First.lib ggobi appears to work OK from the command line. I had an earlier
2002 Jan 02
1
Building R-1.4 on Tru64
Hello everyone, I've just attempted to build R-1.4 on Compaq Tru64 (I'll enclose the text from bug.report() from R-1.3.1 at the end.) The relevant part of the log is below. Any ideas? gcc -shared -o methods.so do_substitute_direct.o methods_list_dispatch.o method_meta_data.o slot.o -L/usr/local/lib /usr/ucb/ld: Warning: Unresolved: TYPEOF Rf_error Rf_protect Rf_substitute
2001 Jan 10
1
configure error on alpha (PR#806)
Hi, I've found that the default options of gcc and g77 on alpha produce an executable that suffers from floating exceptions. There seems to be a problem with the configure scripts that prevents the --with-f77 option working correctly. The configure script tests that f77 is running by attempting to compile and link a dummy program - the link step seems broken on the alpha (it doesn't like
2001 Mar 04
1
passing pointer types via .C calls
Hi, this relates to my earlier message about external references and finalizers. I was experimenting over the weekend and now suspect that the appropriate solution to my problem will be to have a special case in the code that handles the .C call so that external references are handled appropriately - I guess that a pointer to the reference should be passed to the C code. As I've never
2001 Jun 25
5
Trouble compiling R-1.3.0 under Tru64
Dear all, I have some difficulty getting R-1.3.0 to run on the alpha, with osf4.0e (Tru64, or whatever they call it... :-) ). configure reports the following configuration: R is now configured for alphaev6-dec-osf4.0e Source directory: . Installation directory: /astro/local C compiler: gcc -mieee -g -O2 C++ compiler: c++ -g -O2 FORTRAN
2001 Jun 25
5
Trouble compiling R-1.3.0 under Tru64
Dear all, I have some difficulty getting R-1.3.0 to run on the alpha, with osf4.0e (Tru64, or whatever they call it... :-) ). configure reports the following configuration: R is now configured for alphaev6-dec-osf4.0e Source directory: . Installation directory: /astro/local C compiler: gcc -mieee -g -O2 C++ compiler: c++ -g -O2 FORTRAN
2015 Mar 24
2
[LLVMdev] IR blocks for calling function pointers
Hello, I am trying to create IR block for making a call to function pointer. For creating the IR for a function call to "foo", with "foo" being defined as "void foo(int)", I can use the "getOrInsertFunction" call from Module class as follows: std::vector<Type*> FooArgs; FooArgs.push_back(IRB.getInt64Ty()); Value *FooFunction =
2001 Mar 01
0
Finalization and external pointer objects
Hi, I've been developing an image analysis package based on R for a while now and I've had problems relating to garbage collection, so it with great interest that I've noticed the work done by Luke Tierney in this area, and I'd like to discuss how best to fit it into my package. I'll start with how my package is structured - an image is represented by an integer with a class
1999 Aug 02
2
Advice interfacing to an imaging library
Hi All, I've done some work recently making some of our image analysis library callable from R and Splus. Most of the C image functions use an abstract data type, and R only sees a pointer to this. All memory allocation is done by the library. This leads to some interesting problems. I'm interested in your views about possible solutions. 1) assignment. something like a<-b, where a and
2018 Mar 20
1
[RFC] Function pointer alignment
Hello, all. Recently we noticed a problem with function pointer alignment in LLVM: the value tracking analysis (specifically the 'computeKnownBits' function) uses function alignment to infer that the least significant bits of function pointers are known to be zero. Unfortunately, this is not correct for ARM targets: the least significant bit of a function pointer stores the ARM/Thumb
2001 Dec 13
3
R-1.4.0: how to use getSymbolInfo()?
I have a package that solves systems of ordinary differential equations coded as an R function (odesolve, on CRAN). The function is passed to R code, and c and Fortran code called by it uses lang4() and eval() to evaluate the R function inside a compiled c function to use in a compiled ODE solver. This works quite well, but can be slow. I'd like to be able to supply the name of a compiled
2014 Mar 03
3
[LLVMdev] [cfe-dev] C++11 reverse iterators (was C++11 is here)
On Mar 3, 2014, at 12:04 AM, Chandler Carruth <chandlerc at google.com> wrote: >> I was actually going to check in this, but I can post it for review if folks are worried. >> >> My plan was to provide an implementation of std::iterator_range<T> and then provide 'F.arguments()' which returns it. > > Nice. What's the logic behind .arguments() vs
2001 Nov 09
1
One package calling C-code from another package.
Dear R people We have two packages, where the first package (geoR) is required by the second (geoRglmm). Both packages have functions calling C-code via .C(). We would like to call C-functions included in the first package from within the C-code in the second package. Is this possible? An appropriate header file was included in the src directory of the second package but this alone did not
2012 Jun 04
2
[LLVMdev] probleam about ThreadLocalImpl of llvm
Hi, everyone: I am very sorry to trouble you, but I need your help about my problem about ThreadLocalImpl in llvm of 2.8 version. I have compiled it in Windows xp with mingw, and have compiled skyeye(an open source project about simulator) as it uses llvm. But when I run a testcase ---- arm_hello, it came out segment fault. I used gdb.exe to trace it, it gave the following infomation: $
2008 Apr 30
2
openSUSE 11.0 - NUT
Stan, I'm very pleased to see you back to work with us on enhancing nut in that many areas ;-) 2008/4/30 Stanislav Brabec <sbrabec at suse.cz>: > Stanislav Brabec wrote: > > > Please note that 2.2.2-pre3 installs hald addons by default to / on > > openSUSE 11.0 beta 2 x86_64. Not a big problem. > > Here is a patch, which fixes openSUSE 11.0 beta 2 x86_64:
2008 May 02
1
nut: simplification of the automake stuff
Hallo. Here is a simplification of the automake stuff for nut 2.2.2. The idea is simple: libcommon.a contains stuff for the binaries libparseconf.la contains stuff for binaries and shared library Both are NOINST, automake understands perfectly our intentions. The rest is only a removal of the implicitly defined stuff. On top of the parallel build patch I got build success on all platforms
2007 Jan 12
2
Makefiles driving me NUTs
I want to use upsdebugx, upslogx in 'clients/upsclient.c', however this fails with the following error messages (I trimmed the path to the build directory to <path> in order to prevent line wrapping): <path>/clients/upsclient.c:941: undefined reference to `upsdebugx' <path>/clients/upsclient.c:910: undefined reference to `upslogx'