similar to: problem building MS-Windows package under linux

Hi, I tried to use the 'make' file discussed in the last R-news. The step 'make R' dies with: make[2]: Entering directory `/home/laurent/these/R/RCrossBuild/WinR/R-1.7.1/src/gnuwin32' sed -e s/@RVER@/`cut -d' ' -f1 ../../VERSION | sed -n 1p`/g -e s/@RWVER@/rw1071/g rw-FAQ.texi | \ makeinfo --no-headers --number-sections -o rw-FAQ makeinfo --no-split --html

I have the same problem, trying to cross-compile. I'm running Ubuntu Edgy, kernel 2.6.17-10-generic, on an IBM T60. I downloaded the Makefile from CRAN and ran make CrossCompileBuild with the following error messages (also ran each make one at the time and the problem occurs in make R): ../extra/pcre/libpcre.a(pcre_dfa_exec.o):pcre_dfa_exec.c:(.text+0x1703): undefined reference to

We could also simply extend the existing inrange mechanism to non-constantexpr GEPs.  It would remove an inconsistency in the semantics, be relatively straight forward, and solve the motivating example. (I didn't read the proposal in full, so there may be other examples it doesn't solve.) Philip On 7/22/19 10:01 AM, Peter Collingbourne via llvm-dev wrote: > The restrictions of

It's also very common in Fortran. -David Michael Ferguson via llvm-dev <llvm-dev at lists.llvm.org> writes: >> It seems that the main advantage of your proposal is that it would >> allow for non-constant strides (i.e. variable length arrays) in >> dimensions other than the first one. Do these appear frequently >> enough in the programs

> It seems that the main advantage of your proposal is that it would allow for non-constant strides (i.e. variable length arrays) in dimensions other than the first one. Do these appear frequently enough in the programs that you're interested in to be worth optimizing for? Yes - at least in Chapel (which is one of the motivating languages) these are very common. In other words, typical

Hi, I'm trying to cross compile R260 in a ubuntu 6.06 linux. I downloaded the Makefile for 251 and simply replaced the R version by 260. However I'm getting an error about mingw. ernesto at gandalf:~/ipimar/devel/R/ccompile260$ make R export

Dear List, I am (still) trying to use the makefile advertised in R-News (the Makefile is a wrapper around other tools). When I try to build a package using the (fairly recent) 'install.R' mecanism, the output leaves me not so confident about the the usability of the pack built for Windows (I am currently unable to verify it): ---------- Making package splicegear ------------ installing

Hello, We would like to begin discussions around a new set of intrinsics, to better express multi-dimensional array indexing within LLVM. The motivations and a possible design are sketched out below. Rendered RFC link here <https://github.com/bollu/llvm-multidim-array-indexing-proposal/blob/master/RFC.md> Raw markdown: # Introducing a new multidimensional array indexing intrinsic ## The

Intrinsics can return `llvm_any_ty` (Intrinsics.td). In that case the return type is added as a suffix to the intrinsic's name, i.e. the syntax in the RFC is not 100% the syntax for intrinsics. Same for the parameters which each must have their types explicitly mentioned. Michael Am Mo., 22. Juli 2019 um 19:08 Uhr schrieb Kaylor, Andrew <andrew.kaylor at intel.com>: > > Is it

Hi, I think I understand what the problem is. The return type will also be an untyped pointer, just like GEP. However, GEP needs to know what the size of one element is. Like it is now with overloadable intrinsics, we might derive it from the suffix. Another solution is that we pass the element and array sizes in bytes, instead of multiples of the element size. As a third options, we might change

Dear List, I have just compiled my first R library for submission to CRAN; however, I have a tiny problem with 'R CMD check' that is holding me back. I have read extensively the PDF document on Writing R Extensions and the 'Making R Packages Under Windows' tutorial by P. Rossi. All functions are given in R code (no C/C++/Fortran) with two very simple demonstration datasets. My

Hello, I am a newbie. I can run the following code stored in "test.txt" without error using my XP machine: x <- scan("C:\\Rwork\\A.txt") x10 = filter(x, rep(1/10,10), sides=1) x x10 for(i in 10:length(x)){ if (x[i] > x10[i]) diff[i]="b" else diff[i]="s" } However, if I run it in another PC that uses Windows 7, the following error occurs:

I was cross-building R-devel (1.7.0). The tail of the error message from running make on a machine with makeinfo (GNU texinfo 3.12) 1.68 is at the end of this email. The same procedure went fine on a machine with makeinfo (GNU texinfo) 4.1. My first guess is that the version of makeinfo is causing this. However, this didn't happen with R-1.6.2beta. Please advise. Jun ## tail of error

Dear All: I encountered and apparently overcame problems following Yan and Rossini?s procedure for "Building Microsoft Windows Versions of R and R packages under Intel Linux" (http://cran.r-project.org/doc/contrib/cross-build.pdf): I have successfully cross-compiled R packages for Windows on a FreeBSD 4.10 i386 system. My revisions to Makefile-rcb (http://cran.r-

This is a multipart message in MIME format. --=_alternative 00812CFCCA256D66_= Content-Type: text/plain; charset="us-ascii" Two points in respect to PR#2867. First, the trivial one: (1) In Lapack.c, on lines 806 and 812, there are calls of F77_CALL(dgeqp3). But the error messages on lines on lines 809 and 815 refer to "dqeqp3", i.e., they currently have a "q"

Hello, I've the following list n: > n [[1]] [1] "NEW" "OLD" "PRG" [[2]] [1] "04h" "24h" [[3]] [1] "000mM" "010mM" "025mM" "050mM" "100mM" where n <- dimnames(some.multidim.array) I'm trying to define a generic function that generates meaningful names from this list, e.g.

Dear all, i was working under R 1.6.2 but i wanted to install bioconductor under WinXP, and because R 1.7.1 contains the TclTk package and automatic installation of bioconductor packages, so i install it. Everything is fine except this message which appear after the installation of packages. "> local({a<- CRAN.packages(CRAN=getOption("BIOC")) +

All, I've encountered the same problem as others who have posted under the same subject. I've had R-1.8.1 installed and running since it was released. Yesterday morning when I tried to start Rgui.exe I got the subject error message. Since I live at the whim of the network administrators I can only assume it was a recent MS critical update. I tried installing R-1.9.0 but no joy. I

** High Priority ** I have been trying to read an SPSS file into R using read.spss ("C:/Documents and Settings/Roderick Harrison/My Documents/RWORK/ihisdat.sav", use.value.labels = TRUE, to.data.frame = FALSE, max.value.labels = 500, trim.factor.names = FALSE, trim_values = TRUE, reencode = NA, use.missings = to.data.frame) Each time (at least 5 or 6 by now) I get the following

Hello list, I would like to cross-compile R packages using R 2.4.0. I am working on Linux Debian and cross-compiled (windows binaries) without problems with older R version. I have used the doc of Yan and Rossini in the contributed section of the R documentation (same version of MinGW...). When I try to cross-compile R (make R), the procedure stopped and returns :