similar to: [LLVMdev] MinGW LLVM-GCC usage issues

This is my first attempt to call a C function from R. I have installed Rtools,MinGW and Perl and I have included them in my system path. I am trying to compile a toy function that can be called in R but when I type "RCMD SHLIB foo.c" I receive the following message in my Command prompt: making foo.d from foo.c make: [foo.d] Error 255 (ignored) cat: foo.d: No such file or directory make:

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

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

This is not a bug, it's a feature. It stops me from distributing versions with unintentional uncommitted changes. Duncan Murdoch On 29/04/2008 2:30 PM, bill at insightful.com wrote: > 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

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

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

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

On Tue, 29 Apr 2008, Duncan Murdoch wrote: > This is not a bug, it's a feature. > > It stops me from distributing versions with unintentional uncommitted > changes. It does have that effect, but the error messages are pretty obscure: c:\Rtools\MinGW\bin\windres.exe: rcico.rc:9: syntax error and Error on line 12 in e:\R\R-svn\r-devel\src\gnuwin32\installer\R.iss: Value

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

Building a package using R.2.8.0 on Windows XP gives problems when compiling C code: Trying to run 'rcmd build' on R.2.8.0 on Windows XP gives ... ---------- Making package gRbase ------------ adding build stamp to DESCRIPTION making DLL ... gcc -std=gnu99 -Ic:/Programs/R/current/include ------------------------------------ gcc.exe: no input files make[3]: *** [setops.o] Error 1

Dear All, I think I have followed everything for building my first R package (Downloading Rtools, necessary files in necessary locations, no space in path and...). But when in command Prompt I write "Rcmd check mypackage" the first few steps are "OK" but then it gives the following error: checking whether package roots can be installed.....ERROR installation failed see

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

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

When attempting to compile this simple testing tool http://github.com/oneclick/rubyinstaller/blob/fake/resources/tools/fakeruby.c I get the following: C:\Users\Jon\Documents\CDev\sandbox>llvm-gcc -Wall -o fakeruby.exe fakeruby.c Warning: resolving _GetModuleHandleA by linking to _GetModuleHandleA at 4 Use --enable-stdcall-fixup to disable these warnings Use --disable-stdcall-fixup to disable

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

The problem is a bitcode implementation that has a stdcall function that's used from native code. 1 side has _elements_exception_handler, compiled that would be __elements_exception_handler at 20 due to stdcall. The native bit has the mangled name and the linker can't find it as the bitcode indexes have it without mangling. I'll try to prepare a testcase when I get back in the office.

Clang may be avoiding this problem because it will always emit "\01__elements_exception_handler at 20" as the function name. It probably does that for precisely this reason. On Fri, Mar 30, 2018 at 11:55 AM Carlo Kok via llvm-dev < llvm-dev at lists.llvm.org> wrote: > The problem is a bitcode implementation that has a stdcall function that's > used from native code. 1

I tried the version you used, too. the resulting executable was still broken. I guess the reason is due to fastcall on function pointers, which Clang does not recognize. Consider the following snippet. #include <stdio.h> void __attribute__((fastcall)) f(int i) { printf("%d\n", i); } typedef void (*__attribute__((fastcall)) f_t)(int i); //typedef void

Hi! When I set the calling convention of a function to stdcall this has no effect. When I set stdcall to all call instructions then it works. So I wonder what is the use of the calling convention of a function? -Jochen