similar to: External call to Watcom F77 version 11

The attached set of patches adds support for OS/2 using Watcom compiler (tested with Open Watcom 1.9). My only interest was building a working dll (the last patch in the set adds a makefile for it), therefore I did not touch other places: If there is interest, I can do so. Regards. -- O.S. -------------- next part -------------- A non-text attachment was scrubbed... Name:

Hello. I am trying to use a FORTRAN subroutine from within R (Windows version). This fortran subroutine is compiled using the Open Watcom Fortran compiler and the compiled object file is called ritscale.obj. Following the explanation on pages 193-194 of "The New S language" I use the dyn.load command: > dyn.load("f:/maxent/ritscale.obj") Error in dyn.load(x,

On 1/22/17, Dave Yeo <dave.r.yeo at gmail.com> wrote: > On 01/22/17 09:57 AM, Ozkan Sezer wrote: >> On 1/22/17, Dave Yeo <dave.r.yeo at gmail.com> wrote: >>> On 01/22/17 05:35 AM, Ozkan Sezer wrote: >>>> The attached set of patches adds support for OS/2 using Watcom compiler >>>> (tested with Open Watcom 1.9). My only interest was building a

On 01/22/17 05:35 AM, Ozkan Sezer wrote: > The attached set of patches adds support for OS/2 using Watcom compiler > (tested with Open Watcom 1.9). My only interest was building a working > dll (the last patch in the set adds a makefile for it), therefore I did > not touch other places: If there is interest, I can do so. Most of the patches can have s/__EMX__/__OS2__/ excepting the

Hi, I'm trying to load a dynamic link library and it seems to work (is.loaded -> TRUE). When I run the function, which calls the .Fortran subroutine, R crashes! I'v tried the same in S-Plus 2000 and it worked. Therefore I suppose that the dll has been compiled with the stdcall calling convention (and not cdecl). But the problem is that I don't have access to the source code,

Hello, as usual for me with precompiled libraries, the ones of the vorbis- sdk didn't work for me in WATCOM/Win32, so i compiled them on my own (vorbis_static.lib / vorbisfile_static.lib - it was possible after some slight changes like slightly modifiyng the typedef types that Watcom didn't know) The libraries work fine so far (like getting the file info), but when calling ov_read

Has anyone ever successfully used Fortran character strings with R? ?Foreign says R C Fortran integer int * integer .... character char ** [compiler dependent] Character strings are passed as C arrays of character strings to Fortran: the first string may be usable if its length is passed

Hello again R People: I'm still stuck on my packages and FORTRAN problem. I made a directory called erin, (in the library tree) I created a sub-directory called R, in which I put my R source code. I created a sub-directory called libs, in which I put my FORTRAN program, (compiled and made into a DLL). Here is my output > library(erin) Warning there is no R source code in erin I also

I am trying to write a dynamic linked library for R, in Pascal. (This is to speed up the execution of a simulation that I am running in R.) I know Pascal might not be the perfect language for this (C or Fortran being more natural), but from what I have read I think it should work. Though I should point out that I am a neophyte when it comes to DLLs. From R I want to hand a function in

Hi folks, I tried to use Mirosoft Fortran Powerstation 4.0 to create a dll file. However, when I used the command dyn.load(“test.dll”), I got the following message: NULL Warning message: DLL attempted to change FPU control word from 9001f to 90003 I read the instruction on Duncan Murdoch’s website about preserving registers, but I still don’t understand it. For example, 1. On first entry

Everything builds fine on sparc. The configure script needs to be fixed though (see previous email). Sparc testing results: make check: # of expected passes 1189 # of expected failures 34 Regressions Single Source: None New Failures Single Source (new tests): 2005-05-12-Int64ToFP: llc,jit Regressions MultiSource: Applications/d/make_dparser: llc, cbe, jit

This was addressed to the wrong place ... ------- start of forwarded message ------- From: Annette Molinaro-Clark <annette@pacific.llnl.gov> To: maechler@R-project.org Subject: R-Installation Date: Thu, 15 Mar 2001 12:10:19 -0800 (PST) Hi - I'm trying to install R to a supercomputer which has a Fortran 77 compiler; however, when i do ./configure I receive this error . . . checking

On 01/23/17 01:01 AM, Erik de Castro Lopo wrote: > Dave Yeo wrote: > >> >GCC supports __declspec(dllexport) though it still needs a def file, >> >with no exports. Libtool doesn't currently and as flac uses libtool... > So you're happy with this patch? > > http://lists.xiph.org/pipermail/flac-dev/2017-January/006170.html > No. Lots of errors such

OK: despite Dirk's very kind help, I decided that trying to deal with R configuration and Debian configuration simultaneously was too difficult. I did manage to solve my problem by reconfiguring/making/ installing all of 2.3.1 from source: ./configure F77=/usr/bin/g77 make make install A few questions inspired by this experience: (1) it seems a bit odd that R sets F77=gfortran by

After a long processing, I was able to create a version of a small C# class that was able to emulate the rproxy by P/Invoke. This is mostly to find a workaround a performance problem of the StatConnector. It's almost work but ... I have strange memory exception when I call the print function. The variable seems to not survive from one call to the other. As there is no debug symbol for

Tanya Lattner wrote: > > Everything builds fine on sparc. The configure script needs to be fixed > though (see previous email). I'm not getting the error with the configure script (on Kain, anyway). I've tried it with --with-f2c and with f96 (NAG Fortran compiler) in and out of my $PATH. Can you verify that the configure script works for you without the --with-f2c option?

This adds checks for Watcom C DOS cross-compiler in a manner analogous to mingw compiler for Windows. The compiler is not commonly present in Linux distributions due to a non-free license. Signed-off-by: Lubomir Rintel <lkundrak at v3.sk> --- dosutil/Makefile | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/dosutil/Makefile b/dosutil/Makefile index 9dc88d1..69fc58a 100644 ---

Dear R-help, I've managed to crash R on Irix when I called a Fortran subroutine that calls R's random number generator, as described in Section 5.6 of the R-exts manual. (It does say in that section that this is not guaranteed to be portable...) (Well, R doesn't crash when calling the RNG. It crashed when the random number generated isn't inside the unit interval.) Can anyone

Hi, I am having problems calling a fortran routine from within R. When the routine is called, R exits with an application error: "The instruction at 0x004a8b7d referenced memory at 0x200000015. The memory could not be written". The R code used to call the routine is: .Fortran("GTEST",a=as.integer(1),b=as.integer(3),c=as.integer(-10),d=as.inte ger(0),e=as.integer(0)) The

Hello all, I am a beginner of LLVM and I want to add a new backend into LLVM. The calling convention of the target I ported is CDECL. I am wondering to know whether there is already CDECL calling convention implemented in LLVM?? Which CallingConv.td file should I copy and modify for my target?? thanks a lot Mitnick -------------- next part -------------- An HTML attachment was scrubbed... URL: