similar to: Compile dll in Windows XP

Hi, I need to create a Makefile.win for a given package so as to fiddle slightly with the compilation process. My Makefile works fine in Linux but I am having trouble creating Makefile.win for MinGW. I first looked at the commands that Rcmd SHLIB appeared to be running and copied those onto the Makefile. But one step seems to be missing, the creation of the _res.rc file needed by windres

Full_Name: Bill Dunlap Version: 2.8.0dev OS: Windows XP Submission from: (NULL) (70.98.76.47) I tried for the first time to build R from source on Windows, where I got the source code via svn. Per the Installation and Administration manual, I altered src\gnuwin32\MkRules so it had the the locally correct paths to HTML Help Workshop and Inno Setup 5. I also set USE_SVNVERSION=yes, as suggested

This is also on Stack Overflow… It’s odd, because sometimes it seems to wrk, and sometimes not??? error.log [2019-01-01 13:08:31] INFO admin/admin_handle_request Bad or missing password on admin command request (command: stats.xml) [2019-01-01 13:08:31] INFO admin/admin_handle_request Bad or missing password on admin command request (command: stats.xml) [2019-01-01 13:08:31] INFO

Hi All, I am trying to make R package using R 2.6.2 And I am getting following error. When I give R CMD check t1\ ---------- Making package t1 ------------ adding build stamp to DESCRIPTION making DLL ... making CGHseg_rewrite.d from CGHseg_rewrite.c making rowMedians.d from rowMedians.c making runavg.d from runavg.c gcc-sjlj -std=gnu99 -Ic:/R/R-2.6.2/include -O3 -Wall -c

Hello R Developers, This is my first foray into using c-code with R, so please forgive my foolishness. I had a look at the archives and did not find anything on this, so hopefully I am not doubling up. I have tried to use R cmd to create an object file from the odesolve dynload example. I am using windows and have just installed rtools, and have the latest version of stable R (2..7.2). This is

Dear all, We are experiencing some trouble when compiling R packages using R 2.6.0 and the new Rtools installer under Windows XP. (1) First, compiling any package using the new setup stops with an errorrelated to some "/" issue on the inst folder. This folder only contains a CITATION file ---------- Making package FLCore ------------ adding build stamp to DESCRIPTION installing

I tried for the first time to build R from source on Windows, where I got the source code via svn. Per the Installation and Administration manual, I altered src\gnuwin32\MkRules so it had the the locally correct paths to HTML Help Workshop and Inno Setup 5. I also set USE_SVNVERSION=yes, as suggested in MkRules itself. Then, while in the directory src/gnuwin32 I ran 'make all

To all. I need your help. The big question is: How do I make an R library with Fortran 95 files? You may assume that I am a pretty decent programmer in both R and Fortran. I lay out a scenario and need your help! I know how to make an ordinary R package and have dabbled with R + Fortran 95 *.dll linking. I do not have a great handle on the whole Makevars file and whatever else I might need

Dear All, I am having trouble getting an R package to build and install correctly under Windows. In this package, which builds and checks OK under Linux, I use zlib (among other functions, gzprintf). As mentioned by Prof. Ripley a while back, the file "CHANGES" under src/gnuwin32 says explains that to, to use zlib, one has to set $(ZLIB_LIBS) in PKG_LIBS. I have a Makefile.win with

Hi, I'm trying to compile the package biglm, but when I build it with R CMD build biglm, it failed : C:\LOCAL\c-dutang\code\R\biglm2>R CMD build biglm * checking for file 'biglm/DESCRIPTION' ... OK * preparing 'biglm': * checking DESCRIPTION meta-information ...C:/DOCUME~1/c-dutang/Local: Can't op n C:/DOCUME~1/c-dutang/Local: No such file or directory

Hi, my name is Paula. Im trying to learn how to build an R package in Windows XP using a simple example which includes a C source code. The foo.c file is located in mypkg/src/foo.c. I used the command Rcmd build --force --binary [pkgpath]. The problem is when I install the zip file in R the function foo doesn?t exist. The result a recieved during the building process is copied below. I really

Hi, I am still new to LLVM and also GNU softwares. I am doing a project using LLVM. I was building cfrontend on my windows cygwin, however I encountered this problem, may I now what is the cause? ******************************** my configuration output is: bash-2.05b$ ../src/configure --prefix=$CFEINSTALL --disable-threads --disable-n ls --disable-shared --enable-languages=c,c++ loading

Hi Ted, yes this was the problem. Thank you very much. best idaios On Wed, Jan 9, 2013 at 4:51 PM, Ted Harding <Ted.Harding@wlandres.net>wrote: > Ah! You have aqssigned a parameter "equal.var=TRUE", and "equal.var" > is not a listed paramater for t.test() -- see ?t.test : > > t.test(x, y = NULL, > alternative = c("two.sided",

I have a problem compiling Wine with Freetype. Not sure what to do: dpkg -i wine*.deb Code: checking for freetype-config... freetype-config checking for -lfreetype... not found configure: error: FreeType development files not found. Fonts will not be built. Dialog text may be invisible or unaligned. Use the --without-freetype option if you really want this. make: *** [config.status] Error 1

>This mean that the specs file of Cygnus gcc is different from the >mingw32 one. OK thanks (I added main() {} as per FAQ and I got the dynload to build a dll ok) I am also interested in building the R sources as per your descriptions. To simplify things, I have removed b18 cygwin and have now installed egcs-mingw32 with your djtools as recommended. Everything seems to work OK; tools that

The very first time you build GCC, you should do "make bootstrap". After that, you can use "make" and "make install" Reid. On Fri, 2005-05-20 at 00:15 +0800, thean kiat sew wrote: > Hi, I am still new to LLVM and also GNU softwares. > > I am doing a project using LLVM. > > I was building cfrontend on my windows cygwin, however I encountered >

I need to build libLLVM (individual static libraries are fine at the moment) using mingw-w64 cross compilers, i686-w64-mingw32-gcc and (separately) x86_64-w64-mingw32-gcc. I'd like this to work from both Linux and Cygwin build environments. With autotools, this worked fine: ../configure --host=i686-w64-mingw32 and that's it (with mingw32-gcc-c++ installed on Fedora 23, also works fine on

--- On Thu, 3/9/09, Vinh Nguyen <vinhdizzo at gmail.com> wrote: > hi hin-tak, > > i'm trying to build r packages for windows on a > mac/linux. i guess > this used to possible and supported, but is no longer > supported. i > ran into this post of yours, > https://stat.ethz.ch/pipermail/r-devel/2009-July/053971.html, > and hope > u don't mind me

Sorry again, my bad. I actually was using --enable-pics instead of --enable-pic. Now LLVM is being compiled. Hope the last phase llvm-gcc compilation would be a success. Thanks a lot. Akramul --- On Sun, 2/1/11, akramul azim <bijoy123_8 at yahoo.com> wrote: From: akramul azim <bijoy123_8 at yahoo.com> Subject: Re: [LLVMdev] LLVM for ARM target To: "Bill Wendling"

Hello, I am trying to build an R package for Windows from an R package for Linux. There seems to be a "windres" problem somewhere. Here's what I get. C:\Temp>Rcmd build --binary VGAM > mm make[2]: windres: Command not found make[2]: *** [VGAM_res.o] Error 127 make[1]: *** [src/VGAM.dll] Error 2 make: *** [pkg-VGAM] Error 2 In more details, it goes like the following.