From spencer.graves at pdf.com  Sun May 18 03:30:23 2008
From: spencer.graves at pdf.com (Spencer Graves)
Date: Sat, 17 May 2008 18:30:23 -0700
Subject: [Rd] gfortran: Command not found
In-Reply-To: <20080517204715.GA16410@master.debian.org>
References: <481FA853.7070707@pdf.com>
	<alpine.LFD.1.10.0805060533020.4020@gannet.stats.ox.ac.uk>
	<482F3A33.8010607@pdf.com>
	<20080517204715.GA16410@master.debian.org>
Message-ID: <482F86AF.30900@pdf.com>

Dear Dirk: 

      Thanks very much.  It helps to rtfm -- and it helps even more to 
know which fm2r. 

      Best Wishes,
      Spencer

Dirk Eddelbuettel wrote:
> On Sat, May 17, 2008 at 01:04:03PM -0700, Spencer Graves wrote:
>   
>> Dear Professors Ripley and Murdoch: 
>>
>>      Thanks very much for the suggestion to upgrade my Rtools.  That 
>> fixed the problem. 
>>
>>      Another question:  How do people typically debug problems linking 
>> to legacy Fortran?  For example, is there a reasonable (open source) 
>> debugger for gfortran?  In the DierckxSpline package, Sundar Dorai-Raj 
>> and I link R to Fortran written by Paul Dierckx in 1979, last updated in 
>> 1987.  We've encountered segmentation errors killing R, which are 
>> difficult to diagnose. 
>>     
>
> Look at valgrind, which is also documented in the R Extensions manual.
>
> Dirk
>   
>>>> making DLL ...
>>>>         
>
>



[Rd] gfortran: Command not found
Spencer Graves