Problems running Dec Fortran binaries on Dec Alpha 433a

Problems running Dec Fortran binaries on Dec Alpha 433a

Post by Timothy Riehl » Sat, 26 Sep 1998 04:00:00



I just installed RedHat 5.0 (2.0.30 Miata kernel) on my Digital Personal
Workstation 433a.  When I try to run binaries compiled under Digital Unix
with Digital FORTRAN I get the error:

forrtl: info: Fortran error message number is 64.
forrtl: warning: Could not open message catalog: for_msg.cat.
forrtl: info: Check environment variable NLSPATH and protection of
/usr/lib/nls/msg/en_US.ISO8859-1/for_msg.cat.
forrtl: severe (64): Message not found

No problem, I ran into this when I loaded Linux on other alpha machines -
the NLSPATH environment variable now points to a valid fortran message
catalog. Now the program crashes at the same point, but gives the
message:

forrtl: severe (64): input conversion error, unit -5, file Internal
Formatted Read

Indicating that an invalid character was detected during a formatted read.
I've tried copying the for_msg.cat file from other machines to solve the
problem - no luck. FYI this binary runs fine on my PC164 machines. I'm not
sure if the problem is with reading the message catalog, or with the
binary itself.

Does anyone have any idea on how to fix this problem? Any help would be
greatly appreciated.

Thanks,

Tim Riehle
University of Minnesota

 
 
 

Problems running Dec Fortran binaries on Dec Alpha 433a

Post by Timothy Riehl » Wed, 07 Oct 1998 04:00:00


For what it's worth,

I finally got around to tracking down the problem  - it seems there
was a Y2K bug in a local library and the system clock had come up
as 2018 and gone unnoticed.

Thanks to the one person who responded,

Tim


> catalog. Now the program crashes at the same point, but gives the
> message:

> forrtl: severe (64): input conversion error, unit -5, file Internal
> Formatted Read

> Indicating that an invalid character was detected during a formatted read.
> I've tried copying the for_msg.cat file from other machines to solve the
> problem - no luck. FYI this binary runs fine on my PC164 machines. I'm not
> sure if the problem is with reading the message catalog, or with the
> binary itself.

> Does anyone have any idea on how to fix this problem? Any help would be
> greatly appreciated.

> Thanks,

> Tim Riehle
> University of Minnesota