similar to: Problems encountered/fixed making CrossCompileBuild

Dear all, I expect that I am on thin ice trying to build this on freeBSD 4.10, however, after tweaking Makefile-rcb v11Oct04 /* MAKE=gmake; MINGW_CROSS = mingw-cross4 */, I encounter: mingw32-gcc -isystem ~/RCrossBuild/cross- tools/mingw32/include -O2 -Wall -pedantic -I../include -I. - DHAVE_CONFIG_H -DR_DLL_BUILD -c dynload.c -o dynload.o dynload.c: In function `R_loadLibrary':

Jun hi again! Sorry for bothering. Although I had no problem with building Windows package under Linux, I noticed that man pages are not processed as they should or maybe I have a problem with my setup. My package is called 'GeneticsPed'. Instead of HTML or text files I just got a GeneticsPed.Rd.gz in man directory of a package (this is within GeneticsPed_0.1.zip file!). The file

hi there, trying to follow the steps of Yan & Rossini 2003, I have two problems : first when I 'make CrossCompileBuild', I get : ****************************************************************************** make[1]: Entering directory `/home/ros/RWORK/CROSSSOMP/WinR/R-1.8.0/src/gnuwin32' make -f Makefile.docfiles make[2]: Entering directory

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

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

I'm trying to build a very large shared library (bundle) for PPC on Mac OS X 10.5. The build looks something like this, where mybundlebitcode.o is the large object llc -relocation-model=pic -o=mybundle.s mybundlebitcode.o gcc -arch ppc -c -x assembler -o mybundle.o mybundle.s g++ -o mybundle.bundle -bundle mybundle.o -lotherlibrary I get the following error: ld: 32-bit pic-base out of

On Mar 11, 2010, at 5:47 PM, Robb Kistler wrote: > I'm trying to build a very large shared library (bundle) for PPC on Mac OS X 10.5. The build looks something like this, where mybundlebitcode.o is the large object > > llc -relocation-model=pic -o=mybundle.s mybundlebitcode.o > gcc -arch ppc -c -x assembler -o mybundle.o mybundle.s > g++ -o mybundle.bundle -bundle mybundle.o

On Mar 11, 2010, at 6:07 PM, Chris Lattner wrote: > On Mar 11, 2010, at 5:47 PM, Robb Kistler wrote: > >> I'm trying to build a very large shared library (bundle) for PPC on >> Mac OS X 10.5. The build looks something like this, where >> mybundlebitcode.o is the large object >> >> llc -relocation-model=pic -o=mybundle.s mybundlebitcode.o >> gcc

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 :

Full_Name: Henrik Bengtsson Version: 1.3.0 OS: Windows Me Submission from: (NULL) (216.175.122.171) I realized that the title of packages in the library index when they are in a bundle is the title of the bundle and not the package. It looks like the TITLE file, which apparently is used for generating the library index, takes the value of the bundle's title and not the package's title.

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

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

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

Hello, When compiling R-2.0.0 for cross-compiling, I get the following error when calling 'make R' ---------- Making package base ------------ adding build stamp to DESCRIPTION /bin/sh: line 1: --vanilla: command not found make[5]: *** [frontmatter] Erro 127 make[4]: *** [all] Erro 2 make[3]: *** [pkg-base] Erro 2 make[2]: *** [rpackage] Erro 2 make[1]: *** [all] Erro 2 make[1]:

Hi, I'm cross compiling win R in a linux Ubuntu Edgy and I'm getting an error with the utils package. Sys.setenv exists on my R 2.5.0 ... I'm using the tools provided for R250 in http://www.stats.ox.ac.uk/pub/Rtools/i586-cross-tools.tar.bz2 Any ideas ? Regards EJ ---------- Making package utils ------------ adding build stamp to DESCRIPTION installing NAMESPACE file and

I tried to cross-compile the newest release 2.0.1 on a linux machine, but i always got an error at the following stage DHAVE_CONFIG_H -DR_DLL_BUILD -c dynload.c -o dynload.o dynload.c: In function `R_loadLibrary': dynload.c:94: warning: implicit declaration of function `_controlfp' dynload.c:94: error: `_MCW_IC' undeclared (first use in this function) dynload.c:94: error: (Each

Hi everyone, I am trying to cross-compile a package I wrote using the Yan and Rossini tutorial "Building Microsoft Windows versions of R and R packages using Intel Linux". I have got reasonably far with this but when doing the linking using the line: i586-mingw32-g++ -shared -s -o mylibrary.dll mylibrary.def mylibrary.o mylibrary_res.o

I'm using Ubuntu 8.10 (Intrepid Ibex) and R 2.7.1. I've built a package from source (a modified version of gbm) and it contains some C++ code. I now want to cross-compile it to get a Windows version. I installed R using sudo apt-get update sudo apt-get install r-base sudo apt-get install r-base-dev So far as I can tell, I've also followed all the instructions in the guide

Hello, there I've run into situation which looks like bug to me - attached is the source and the executable, wich triggers the buggy behaviour. The executable is compiled with mingw32 cross-copiler based on linux and targeted to Win32. The cross-compiler can be found at: http://members.telering.at/jessich/mingw/mingwcross/mingw_cross.html This is the output of the program being run with Wine

Well, I'm finally getting around to setting up a cross-compiler for Windows on my local Linux box. I'm using the Yan & Rossini's docuimentation and the latest 'http://cran.r-project.org/doc/contrib/Makefile-rcb' , which is working of the R-2.2.0 sources. After discovering that "cp -p" doesn't work on the filesystem I'm using and removing the