similar to: mac osx, g95 package port problem

Displaying 20 results from an estimated 300 matches similar to: "mac osx, g95 package port problem"

2005 Sep 28
3
gfortran Makefile for windows
Hi all, (Originally posted to r-help) I'm porting a package that I've worked on for OS X to Windows. The package is written in F95 so I need to compile it with gfortran and link it with gcc4. I've been trying to build an R with gcc4 without luck so far. If there is a binary of such a thing info would be appreciated. This package requires a Makefile. My question is, how can I find
2005 Sep 28
1
gfortran Makefile for cygwin
Hi all, I'm porting a package that I've worked on for OS X to Cygwin/Windows. This package requires a Makefile. My question is, how can I find out (or what is), the link command? Here is the OS X Makefile: RLIB_LOC=${R_HOME} F90_FILES=\ class_data_frame.f90 \ class_old_dbest.f90 \ class_cm_data.f90 \ class_cm.f90 \ class_bgw.f90 \ class_cm_mle.f90 \ cme.f90 FORTRAN_FILES=\ dgletc.f
2005 Oct 08
1
windows/g95 peculiarity
I'm not looking for an answer here, this is just a report of a peculiar event I've observed and can reproduce. I'm developing a g95 (20050129) compiled package on windows xp pro using R-2.1.1, and gcc-3.4.2 (mingw special). An older version of the F95 package compiled and ran without problems. The new version of the package includes extensive changes in the code. The package has a
2007 Jul 13
2
trouble compiling Hmisc package
Hi: We're trying to install the Hmisc package on a Solaris 9 machine. Here's what we get: R CMD INSTALL /usr/local/srctree/Hmisc_3.4-2.tar.gz * Installing to library '/usr/local/lib/R/library' * Installing *source* package 'Hmisc' ... ** libs g95 -fPIC -g -O2 -c cidxcn.f -o cidxcn.o g95 -fPIC -g -O2 -c cidxcp.f -o cidxcp.o g95 -fPIC -g -O2 -c hoeffd.f -o
2008 Jan 26
1
Capturing info from system calls in Windows
Colleagues, I am preparing scripts that will be used by others on both Windows and Linux/OSX platforms. The scripts call an existing Fortran application. The user may have any of a a variety of Fortran compilers - my goal is to determine whether or not the test command returns "no input files" or "command not found" (i.e., so that I can confirm which Fortran they
2009 Mar 11
1
libf95.a: could not read symbols?
I'm sorry for having to post this, but I've run out of ideas. I've been trying to build R-2.8.1 from source for installation on FreeBSD 6.4 (seems to be working fine on osx) and keep getting the same results, regardless of how I set ./configure $ ./configure --enable-R-shlib --with-x=no --with-blas FFLAGS="-fpic" R is now configured for x86_64-unknown-freebsd6.0 Source
2006 Aug 19
1
problem with Rcmd check and fortran95, makefile
Hi all, I have Win XP and R 2.3.1 on my notebook. I would like to write a package which includes some Fortran 95 code. Interestingly, if I compile and link the simple file test90.f90 directly with g95 -c test90.f90 g95 -shared -o test90.dll test90.o then PE Viewer ( a dll viewer) shows me the right functions in the export table, hence I can use the dll in R. But as it should become part of a
2009 May 22
2
Step by step: Making an R package with Fortran 95
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
2006 Sep 11
0
[LLVMdev] gfortran calling convention
Another option might be g95 instead of gfortran. I haven't used it for a while, but I seem to recall it working fine in gcc 4.0.1. On 9/11/06, Michael McCracken <michael.mccracken at gmail.com> wrote: > On 9/9/06, Michael McCracken <michael.mccracken at gmail.com> wrote: > > On 9/9/06, Steven Bosscher <stevenb.gcc at gmail.com> wrote: > > > On 9/9/06, Chris
2005 Mar 27
3
F90
Hello! Has anyone successfully compiled F90 sources in R-package? I found the same question on r-devel list from 2002 and I wonder if there is any progress. I heard that g95 and gfortran can be usable. And one more thing. I have a program written in F90 and lets suppose that compiler is not a problem. I've read manual 'Writing R Extensions' and successfully loaded one F77 subroutine
2005 Mar 27
3
F90
Hello! Has anyone successfully compiled F90 sources in R-package? I found the same question on r-devel list from 2002 and I wonder if there is any progress. I heard that g95 and gfortran can be usable. And one more thing. I have a program written in F90 and lets suppose that compiler is not a problem. I've read manual 'Writing R Extensions' and successfully loaded one F77 subroutine
2005 May 18
2
Fortran 95 in R ?
Is it possible to run Fortran 95 code from R? I don't think so, but hopefully someone can prove me wrong. Here is the test I tried: A little fortran 95 subroutine: subroutine allloc() real, dimension(:, :), allocatable :: a integer :: n n = 10 allocate(a(n,n+1)) end I then compiled: >g95 -c allloc.f >R CMD SHLIB allloc.o Here is what happens when I try to dyn.load it in R 2.1.0
2005 May 18
2
Fortran 95 in R ?
Is it possible to run Fortran 95 code from R? I don't think so, but hopefully someone can prove me wrong. Here is the test I tried: A little fortran 95 subroutine: subroutine allloc() real, dimension(:, :), allocatable :: a integer :: n n = 10 allocate(a(n,n+1)) end I then compiled: >g95 -c allloc.f >R CMD SHLIB allloc.o Here is what happens when I try to dyn.load it in R 2.1.0
2006 Mar 15
0
Samba + Cups -> PPD Options problem - 1 attachment
Hi, I have many printers installed under cups on a samba server, so the printers can be used and installed on Mac and PCs. My problem appeared with some new printers I bought and their PPDs. Under Cups, all the PPD options (Page Sizes, Trays, etc..) appear if I looked at them from the cups printer configuration page or if I use it from a Mac. But if I install the printers under windows
2005 Jun 06
1
segmentation fault - debugging
Hi all, I'm trying to debug some fortran 95 code that I'm bringing in with a dyn.load(). I'm compiling a number of files using g95 on intel linux w/ R 2.1.0. The .so file loads without complaint, but when I try to call it I get a seg fault. I was hoping I could get a core dump in order to get some more clues about what is going on, but no luck. I'm relatively new to fortran
2005 May 20
1
R 2.1 and gfortran
From the configure output of the latest devel snapshot: > checking for g77... no > checking for f77... no > checking for xlf... no > checking for frt... no > checking for pgf77... no > checking for fl32... no > checking for af77... no > checking for fort77... no > checking for f90... no > checking for xlf90... no > checking for pgf90... no > checking for
2011 Nov 10
1
assistance building R on RHEL5
I have gotten this error while attempting to build R-2.13.2 and R-2.14.0 using ./configure --with-x=no --enable-R-shlib, and ./configure --with-x=no Red Hat Enterprise Linux Server release 5.6 (Tikanga) ========================= Warning in solve.default(rgb) : unable to load shared object '/users/home/mked/R-2.13.2/modules//lapack.so': /users/home/mked/R-2.13.2/lib/libRlapack.so:
2001 Nov 12
1
Filled Contour.
Hi. I'm a big user of level plots. Because filled.contour() didn't do exactly what I wanted, I hacked at it a bit to add these options: (*) Even spacing in the key, even if the contours are not evenly spaced. (*) Horizontal key (*) options to not use layout() and to plot only the level plot _or_ only the key. This means you can use layout yourself to (e.g.) have several
2002 Jun 25
1
configure for R 1.5.x on Solaris (fwd)
Dear All, No-one seemed to know about this on r-help, so I'm trying here.... I'm having problems at the configure stage when trying to build R on Solaris 5.8. configure finds everything it needs but when it runs config.status to make all the Makefiles and headers, I get a huge slew of errors like this: config.status: creating src/extra/zlib/Makefile sed: -e expression #1, char 329:
2010 Jul 15
1
Error using the mi package
I'm trying to impute data using the mi package, but after running through almost the entire first round of imputations (which takes quite a while), it throws this error (I'll include the whole output prior to the error for context). Does anyone know what is causing it, or how I can fix it? More specifically, how can I tell what is throwing the error so I know what to fix? Is