search for: mylib

I am using the .Call interface to call c++ code from R. For that, I am trying to create a dynamic library (mylib.so) using "R CMD SHLIB" by linking my own c++ code and an external c++ library (blitz++). The makefile works fine on my Mac, produces mylib.so and I am able to call .Call() from R, but on a linux server (I think Debian), I got the following error: ---------- /usr/bin/ld: /somepath/bli...

I am using the .Call interface to call c++ code from R. For that, I am trying to create a dynamic library (mylib.so) using "R CMD SHLIB" by linking my own c++ code and an external c++ library (blitz++). The makefile works fine on my Mac, produces mylib.so and I am able to call .Call() from R, but on a linux server (I think Debian), I got the following error: ---------- /usr/bin/ld: /somepath/bli...

Hello, I 'd like to use some functions in myLib. So I do: library(myLib) Then I get this message: Error: package 'myLib' is not installed for 'arch=i386' > sessionInfo() R version 2.13.2 (2011-09-30) Platform: i386-pc-mingw32/i386 (32-bit) locale: [1] LC_COLLATE=French_France.1252 LC_CTYPE=French_France.1252 LC_MONETARY...

Hi, This is Crystal. I have some questions about llvm-gcc. Could you please give me some advice? Thanks in advance. Problem description: Env: llvm-gcc (GCC) 4.2.1 gcc (GCC) 4.1.2 OS:fedora7 I tried to compile a C programme test.c with llvm-gcc by task: [root at localhost mylib]# llvm-gcc -emit-llvm test.c -Llibmylib.a -c -o test.bc [root at localhost mylib]# lli test.bc after running the command "lli test.bc",print the error info as follows: ERROR: Program used external function 'gt' which could not be resolved! lli[0x85c245f] /lib/libc.so.6(abort+0x10...

Hi, I have built a library that consists of a piece of C code and some R functions. To build it into a library that I can load using library() command, I have followed "Writing R Extensions" and made sub-directories such as mylib/R and mylib/src. But when I run R CMD INSTALL mylib, nothing seems to be happening with src directory, i.e., no C compiling. I have probably missed some key steps. But after reading very carefully "Writing R Extension", I conclude that I don't need to write my own Makefile in src sinc...

Hi, I have built a library that consists of a piece of C code and some R functions. To build it into a library that I can load using library() command, I have followed "Writing R Extensions" and made sub-directories such as mylib/R and mylib/src. But when I run R CMD INSTALL mylib, nothing seems to be happening with src directory, i.e., no C compiling. I have probably missed some key steps. But after reading very carefully "Writing R Extension", I conclude that I don't need to write my own Makefile in src sinc...

Dear R users, we are trying to build a R package that includes a precompiled shared library, let's say mylib.so. We created the skeleton of the package and we moved the mylib.so file into the libs folder that we created at the same level of the folders man and R. Moreover we created the file NAMESPACE and we added the line useDynLib(mylib, .registration=TRUE). The building step seems to work correctly but...

...ecify these locations (and set these via `--configure-vars'). One can also bypass the configure mechanism using the option `--no-configure'. No doubt because of my inexperience, I can't quite figure out how this works. For example, if I want to set the variable LIBS to '/mylibs', how would I do this? I have tried various versions of R CMD INSTALL --configure-vars='LIBS=/mylibs' mypackage R CMD INSTALL --configure-vars 'LIBS=/mylibs' mypackage R CMD INSTALL --configure-vars LIBS=/mylibs mypackage all to no effect. (Although it is quite possible that...

...via the R command prompt using the dyn.load(...) and dyn.unload(...) functions. consider the following scenario: two libraries of the same functions (different implementations) exist at a user-level directory (we don't have system /lib or /usr/lib access). these two files reside here: ~/lib/mylib.v1.so and ~/lib/mylib.v2.so mylib.so is a copy (or link) to mylib.v1.so start R, load the library via 'dyn.load("~/lib/mylib.so")' execute R function that uses .Call(...) to a compiled function. unload the library via 'dyn.unload("~/lib/mylib.so")' copy mylib.v2....

hi, i'm having some trouble getting a package to load a shared library object in .onLoad(...) i have a shared object file, say "mylib.so". if i start an R session, and via the CLI specify the actual library via: > dyn.load("mylib.so") everything works quite well (i.e. i can then follow with some .Call (...) methods) now, i'd like to include this shared library in my package. assume that the .c file has alr...

...-dirs", dir), + intern = TRUE), 3) + ## return name of tar file built + dir('.', pattern = patt) + } > build.pkg("myTst") [1] "myTst_1.0.tar.gz" > ## clean up any previous attempt (which might have left a 00LOCK) > unlink("myLib", recursive = TRUE) > dir.create("myLib") > install.packages("myTst", lib = "myLib", repos=NULL, type = "source") # with warnings * installing *source* package 'myTst' ... ** R ** preparing package for lazy loading ** help Warning: /home/cs...

...ng code in '../../R-2.13-src/tests/reg-packages.R' ...make[3]: *** [reg-packages.Rout] Error 1 make[2]: *** [test-Reg] Error 2 make[1]: *** [test-all-basics] Error 1 make: *** [check] Error 2 locating tests/reg-packages.Rout.fail I find > stopifnot(require("myTst",lib = "myLib")) Loading required package: myTst > sm <- findMethods(show, where= as.environment("package:myTst")) > stopifnot(names(sm at names) == "foo") > unlink("myTst_*") > > ## More building & installing packages > ## NB: tests were added here for...

Hi, Standard approach to profiling dynamically loaded libraries with gprof doesn't seem to work with LLVM: export LD_PROFILE=Mylib.so export LD_PROFILE_OUTPUT=. make ENABLE_PROFILING=1 // compiling my project opt -load Profile/Mylib.so -options... but no Mylib.so.profile (or gmon.out) is produced. Profiling libc.so.6 usage by "ls -l", however, works fine. Could anyone explain me what am I doing wrong? Thx....

...my C functions perfectly. now i want to build the package so i can install it easily on my colleagues' machines. so i use the normal R build mechanism (R CMD build), but first create a Makevars file that looks like so: PKG_CPPFLAGS = -I../depPkg/include PKG_LIBS = ../depPkg/lib .PHONY: all mylibs all: $(SHLIB) $(SHLIB): mylibs mylibs: (cd ..; gunzip depPgk.tar.gz; tar -xf depPkg.tar; cd depPkg; ./ configure --prefix=./lib --with-pic --disable-shared; make; make install) finally, when i try R CMD INSTALL, i know it sees the Makevars file, because the first build step shows the...

...01 01 00 andeq r0, r1, pc, lsr #2 llvm-objdump: warning: invalid instruction encoding 1a83: e3 13 ff 2f svchs #16716771 llvm-objdump: warning: invalid instruction encoding The binaries I try to read are c++ dynamic libraries for Android. I have used the following parameters: -llvm-objcdump mylib.so -d -arch=arm -llvm-objcdump mylib.so -d -arch=armv7 -llvm-objcdump mylib.so -d -arch=thumb or with the following triples: armv7-none-linux-android thumbv7-none-linux-android Does anyone know why I have this error? Am I missing some input parameters? This is strange because it works great on...

Hi all, I'm having some problems in loading libraries. I wonder if anyone can help me with this. I have created two libraries with the same name at different locations. I want to use both of them, one at a time. So I do: library(mylib,lib.loc1) (....) detach('package:mylib') library(mylib,lib.loc2) The problem is that, after this, the used library is still the one first loaded. Isn't detach command enough? Thanks in advance, Rita -- Rita Ribeiro <rita at liacc.up.pt>

...tall.packages is really convenient --- if you are installing to your system's main package directory. However, I observe the following problem: I want package X but it requires package Y. Further, I have neither package right now. And, I want to install both of them to my homedir (say at ~/mylib) rather than the main R package directory. What I would want to do then is: > install.packages('X',lib='~/mylib',dependencies=TRUE) However, this doesn't work. It does notice that X depends on Y and so it downloads Y first, but it downloads Y to the wrong directory!! It s...

...library and dyn.load them. Of course the new functions mySave/Load will use some of the internal R functions used by save/load, for example "MarkSave" (to be found in .../src/main/saveload.c). I declared them as external void MarkSave(SEXP s); .... in my code. When I do dyn.load("myLib.so") I get the error Error in dyn.load(x, as.logical(local), as.logical(now)): unable to load shared library "myLib.so": myLib.so: undefined symbol: MarkSave Can't I use R internals other than those visible in $R_HOME/include? Thanks for some clarifying hints -- Dr. Joer...

...at 9:03 AM, Steven Stewart-Gallus via cfe-dev <cfe-dev at lists.llvm.org> wrote: > Hello, > > Can I ask for some clarification? > > Apparently, C++ doesn't allow to static class methods? > > While in C one might write inside a header file: > > static inline void mylib_foo_do_method(struct mylib_foo *foo) { > // implementation here > } > > In C++ the typical style would be to write something like: > > namespace mylib { > > void foo::do_method(void) > { > // implementation here > } > } > > Unfortunately, the C++ case...

...graphics' in package 'exNSS4' ** help No man pages found in package 'exNSS4' *** installing help indices ** building package indices ** testing if installed package can be loaded * DONE (exNSS4) Loading required package: exNSS4 > (res <- installed.packages(lib.loc = "myLib", priority = "NA")) Package LibPath Version Priority Depends Imports LinkingTo Suggests myTst "myTst" "myLib" "1.0" NA "methods" NA NA NA Enhances License License_is_FOSS myTst NA...