similar to: gomp library with Rtools212

Hello, I am stuck trying to build 64-bit R 2.12.1 on Windows 7, hopefully the problem is obvious and someone can point out what I'm missing. Well into the "make all recommended" process, I get an error: make[4]: *** [Rzlib.dll] Error 4 (A longer report on the error in the build print is below - there is also help output from sed that I have included but don't know if it is

Hi, Currently I testing the packets that contain built-in features for classification. Actually I looked packages such as: e1071, Klar, Caret, CORElearn. However, from what I noticed when building a naive Bayesian classifier, that they package use of the finite mixture model to estimate P (x | C) and using a normal distribution. In my research I use binary data and I want modeled P (x | C), eg the

Hi, Apologies if this is the wrong list to be sending this question to. I am trying to install a copy of the R tools required to create / compile packages on windows. After downloading Rtools from http://www.murdoch-sutherland.com/Rtools/ windows keeps complaining that "The setup files are corrupted". This has happened with both the Rtools213.exe and the Rtools212.exe downloads, and

Hi all, I just built R from src on Windows 7 using Rtools212.exe. The build went as usual (R, bitmaps, and manuals all OK) but make check-all failed when running the examples for package 'tcltk': ... running code in 'demos2.R' ... OK running tests of primitives running code in 'primitives.R' ... OK make[2]: vfork: Resource temporarily unavailable make[1]: ***

Dear all, Since version R-2.12.0, I've got problems building an add-on package for R ("imglib" here) for 32-bit Windows. The following command is called: C:\Program Files\R\R-2.12.0\bin\i386\Rcmd build --binary imglib And here is an error I am getting in the end of processing: ** testing if installed package can be loaded Error : package 'imglib' is not installed for

Hello: 1. How can I tell when the development version of Rtools has changed? For the past few years, I've installed the development version of R tools with each new release of R. I encountered problems with this a few days ago, so I rolled back to Rtools212.exe. Unfortunately, I seem to have more problems with that version. My latest install was under Windows 7 Home Edition.

Hi All, I am trying to compile R 2.13.0 r53834 on 64-bit Windows 7 (home premium) using Rtools212.exe from Duncan Murdoch's site. I (think) I followed the installation guide for Windows. When installing Rtools, made sure I was installing 64-bit tools (including tcltk), etc. I created a copy of MkRules.local where I selected 64 bit instead of 32 architecture. When I run:

FYI, I'm sure the following is a temporary issue, but in case it slips through, I want to raise it here. On Windows 7 64-bit, running Rcmd check on R devel gives: * using R version 2.13.0 Under development (unstable) (2011-02-11 r54330) * using platform: x86_64-pc-mingw32 (64-bit) * using session charset: ISO8859-1 * checking for file 'aroma.core/DESCRIPTION' ... OK * this is

Hello: What do I need to do to compile R packages (especially RMySQL) for the 64-bit version of R 2.12.0 under Vista_x64? I upgraded to "Rtools212.exe" yesterday but immediately got errors from "R CMD check RMySQL_0.7-5.tar.gz". After the first error, I installed it a second time, then got "undefined reference to" roughly 50 different names beginning

A question, please about development of R packages: Are there any guidelines or best practices for deciding when and why to implement an operation in R, vs. implementing it in C? The "Writing R Extensions" recommends "working in interpreted R code . . . this is normally the best option." But we do write C-functions and access them in R - the question is, when/why is this

recently I used gcc 4.9.1 (http://sourceforge.net/projects/mingw-w64/files/Toolchains targetting Win64/Personal Builds/mingw-builds/)on windows to build R,but failed when link R.dll ,it report linker status 5.  after some digging, I found when use gcc 4.9.1 64 bit on windows there are lots of .refptr.*(* is r function name) in R.def, which lead build fail.so I add a simple path to

Dear all, I'm trying to create my own package by following for instance http://epub.ub.uni-muenchen.de/6175/2/tr036.pdf In step 6 (page 19) it says that the command 'R CMD build <mypackage>' should result in a tar.gz file. However, after running the command I end up with a tar file only (no gz extension). I also get the following warnings in the command prompt C:\Program

I originally posted on this topic on a different thread: https://stat.ethz.ch/pipermail/r-devel/2016-August/072938.html These sources suggested that a safe practice might be to put double quotes around symbol names in EXPORTS in case the symbol name is the same as a linker keyword: - https://sourceware.org/binutils/docs/ld/Symbols.html#Symbols -

List gurus, I'm trying to code a Gompertz growth curve function as part of a larger project and have run across a problem due to my ignorance of environments. Some sample data and the function are as follows: growth <- data.frame(age = c(1.92, 3, 5.83, 3.17, 15.5, 1.17, 5.58, 13.33, 14.29, 5.83, 13.79, 6.33, 13.75, 16.83, 13, 11.67, 0.25, 1.73, 9.46, 5.67), length = c(157, 165, 179,

Under Windows the make include share/make/winshlib.mk uses nm to grab symbols from object files to insert into a module definition file tmp.def that is used to create a package DLL. This works fine provided the DLL is only used via exported function entry points, which is the case currently, I suspect. But the pattern SYMPAT (defined in Makeconf) used to capture symbols includes non-function

Hello R-gurus, I'm trying to adjust different growth curves to a rather extensive dataset. I wrote up a function to go through all of them, but am encountering a problem : among the more than 1000 curves I have, obviously for some of them I encounter conversion problems. I'd like for my function to keep going to the next curve and store the fact that for curve number X I had a convergence

Hi Duncan Sands, As I have understood, GOMP and OpenMP provides support for parallelizing program at source program level. But I am at the IR level. That is I am trying to parallelize the IR code. This is the case of automatic parallelization. The programmer writing the code does not have any idea of parallelization going behind the hood. So my question is instead of support at the source

On Feb 6, 2008, at 5:18 AM, Duncan Sands wrote: > Hi, > >> if /bin/sh ./libtool --mode=compile /s/llvm/obj.gcc42/./gcc/xgcc -B/ >> s/llvm/obj.gcc42/./gcc/ -B/usr/local/i686-pc-linux-gnu/bin/ -B/usr/ >> local/i686-pc-linux-gnu/lib/ -isystem /usr/local/i686-pc-linux-gnu/ >> include -isystem /usr/local/i686-pc-linux-gnu/sys-include - >> DHAVE_CONFIG_H -I.

Hi, I want to execute the iterations of a loop in parallel, by inserting calls either to pthreads or to the gomp library at the LLVM IR level. As a first step, I inserted an omp pragma in a C file and compiled it with llvm-gcc to check the generated LLVM code. If I understand correctly, to parallelize the loop in LLVM IR, I have to separate the loop in a new function, put all required parameters

On Tue, Mar 22, 2011 at 1:36 PM, Gokul Ramaswamy <gokulhcramaswamy at gmail.com > wrote: > Hi Duncan Sands, > > As I have understood, GOMP and OpenMP provides support for > parallelizing program at source program level. But I am at the IR level. > That is I am trying to parallelize the IR code. This is the case of > automatic parallelization. The programmer writing the