Duncan and Brian,
Thanks again for the help with this. As it turns out the suggestion of
setting the GFORTRAN_STDIN_UNIT=-1 has the library working for Mac,
Linux, and Windows, so it appears to be in a STDIN read somewhere. Of
the 1100 read statements in the code, none are from stdin, or unit 5.
Thanks Duncan for helping me along the way. I am working in OSX,
Linux, and Windows, and gdb is helping me trace it along to what
appears to be an endless processor intensive loop in sys-std.c .
Below, I have pasted the output. All files are closed as verified by
lsof. There is absolutely no stdio
You seem to have missed the force of the warning in 'Writing R
Extensions'.
If you include *any* Fortrann I/O in your package code, you are at
risk from it interfering with C I/O, whether or not that Fortran I/O
is called.
On some platforms with gfortran, merely loading such a package's
Howdy,
I am having a problem with a library compiled from some legacy fortran
code. I can call the library, it runs as it should, returns a list,
and gives a prompt, but then locks up the R session. Functions
typed in return nothing. ctrl-c results in a new prompt that is still
locked up, and R
On 24/03/2011 12:35 PM, Daniel Fuka wrote:
Howdy,
I am having a problem with a library compiled from some legacy fortran
code. I can call the library, it runs as it should, returns a list,
and gives a prompt, but then locks up the R session. Functions
typed in return nothing. ctrl-c results in
