Fortran - Problem running IFC on Debian

Author

Problem running IFC on Debian

Madhusudan Singh

2004-05-12, 9:09 pm

Hi

I alien'ed the ifc rpms (newest version) and installed these on my new
Debian Sarge system.

Now, when I compile an executable and try running it, I get :

forrtl: info: Fortran error message number is 64.
forrtl: warning: Could not open message catalog: ifcore_msg.cat.
forrtl: info: Check environment variable NLSPATH and protection of
/usr/lib/ifcore_msg.cat.

I installed IFC in /usr/local/fortran.

What does this mean ?
How do I fix it ?

Thanks,

MS

Tim Prince

2004-05-12, 9:09 pm

"Madhusudan Singh" <spammers-go-here@yahoo.com> wrote in message
news:2g5aifF4de2qU1@uni-berlin.de...
> Hi
>
> I alien'ed the ifc rpms (newest version) and installed these on my
new
> Debian Sarge system.
>
> Now, when I compile an executable and try running it, I get :
>
> forrtl: info: Fortran error message number is 64.
> forrtl: warning: Could not open message catalog: ifcore_msg.cat.
> forrtl: info: Check environment variable NLSPATH and protection of
> /usr/lib/ifcore_msg.cat.
>
> I installed IFC in /usr/local/fortran.
>
> What does this mean ?
> How do I fix it ?
>
If you Google, or even look at your installation, you should be better
enlightened. Assuming that you have installed all the files which come with
ifc, you are missing a sym-link or permissions which would make that file
show up readable in /usr/lib. I think that's close to what the message says,
given that an NLSPATH environment setting might do the job. The installation
script would have done one or both of those for you on supported
environments, so that's one of the chores you take on for yourself on
Debian.

The newest versions of Intel Fortran prefer to be called ifort.

Gerry Thomas

2004-05-12, 9:09 pm

"Tim Prince" <tprince@computer.org> wrote in message
news:u0fnc.46371$s75.18676@newssvr29.news.prodigy.com...

[...]

> If you Google, or even look at your installation, you should be better
> enlightened.

Why would an obdurate freeloader bother when there are so many willing
handmaidens at his beck and call here at c.l.f.?

--
E&OE

Ciao,
Gerry T.
______
"There's man all over for you, blaming on his boots the fault of his
feet." -- Samuel Beckett.

flubie

2004-05-12, 9:09 pm

From the intel fortran user guide:

========================================
========================================
=
64 severe (64): Input conversion error
FOR$IOS_INPCONERR. During a formatted input operation, an invalid character
was detected in an input field, or the input overflowed the range
representable in the input variable. The value of the variable was set to
zero.
========================================
========================================
=

The problem could be in your code and unrelated to debian.

Madhusudan Singh wrote:

> Hi
>
> I alien'ed the ifc rpms (newest version) and installed these on my
> new
> Debian Sarge system.
>
> Now, when I compile an executable and try running it, I get :
>
> forrtl: info: Fortran error message number is 64.
> forrtl: warning: Could not open message catalog: ifcore_msg.cat.
> forrtl: info: Check environment variable NLSPATH and protection of
> /usr/lib/ifcore_msg.cat.
>
> I installed IFC in /usr/local/fortran.
>
> What does this mean ?
> How do I fix it ?
>
> Thanks,
>
> MS

andy2o

2004-05-12, 9:09 pm

flubie <fluberman72@REMOVE.THIS.wanadoo.nl> wrote in message news:<409dda3a$0$60790$cd19a363@news.wanadoo.nl>...[color=darkred]
> From the intel fortran user guide:
>
> ========================================
========================================
=
> 64 severe (64): Input conversion error
> FOR$IOS_INPCONERR. During a formatted input operation, an invalid character
> was detected in an input field, or the input overflowed the range
> representable in the input variable. The value of the variable was set to
> zero.
> ========================================
========================================
=
>
> The problem could be in your code and unrelated to debian.
>
>
>
>
>
> Madhusudan Singh wrote:
>

I fairly often (but not always) get error messages like

"forrtl: warning: Could not open message catalog: ifcore_msg.cat.
orrtl: info: Check environment variable NLSPATH and protection of..."

from ifort when my code reaches a STOP command, or I manually
interrupt a code with Ctrl^C, or I hit a run-time error. It's just
sudden halts to a running code that cause this warning. The rest of
the time ifort works perfectly fine, and to be honest I just haven't
had to bother fixing the NLSPATH warning.

So I suggest this may actually be a run-time error due to a bug in
your code or input files. Try running a simple "Hello World" code. I
think you'll find the compiler will work OK.

(BTW: I'm using ifort on RH8, in the default install directory
though...)

Best wishes,
Andy.

Madhusudan Singh

2004-05-12, 9:09 pm

On Sunday 09 May 2004 03:13, flubie (fluberman72@REMOVE.THIS.wanadoo.nl)
held forth in comp.lang.fortran
(<409dda3a$0$60790$cd19a363@news.wanadoo.nl> ):

>
> From the intel fortran user guide:
>
>
========================================
========================================
=
> 64 severe (64): Input conversion error
> FOR$IOS_INPCONERR. During a formatted input operation, an invalid
> character was detected in an input field, or the input overflowed the
> range representable in the input variable. The value of the variable was
> set to zero.
>
========================================
========================================
=
>
> The problem could be in your code and unrelated to debian.
>
>
>

No, it isn't. This code has worked on IFC (Redhat), Sun f90, Absoft
(Windows), etc.

I just ported IFC to Debian after alien'ing them, and some of the
configuration variables were overlooked.

John-Paul Stewart

2004-05-12, 9:09 pm

Madhusudan Singh wrote:
> Hi
>
> I alien'ed the ifc rpms (newest version) and installed these on my new
> Debian Sarge system.
>
> Now, when I compile an executable and try running it, I get :
>
> forrtl: info: Fortran error message number is 64.
> forrtl: warning: Could not open message catalog: ifcore_msg.cat.
> forrtl: info: Check environment variable NLSPATH and protection of
> /usr/lib/ifcore_msg.cat.
>
> I installed IFC in /usr/local/fortran.

I've never used their Fortran compiler, but with the Intel C Compiler,
there's a shell script installed in the bin/ subdirectory called
"iccvars.sh" (or "iccvars.csh" for csh users) that sets up the necessary
environment variables before you can use the compiler or programs
generated by it. If there's a similar "ifcvars.sh" try sourcing it:

.. /usr/local/fortran/bin/ifcvars.sh

or somesuch might do the trick. (I'll say again, this is just a guess
based on my experience with icc on Sarge. I may be way off base here.)

Dr. Richard E. Hawkins

2004-05-20, 6:32 pm

In article <u0fnc.46371$s75.18676@newssvr29.news.prodigy.com>,
Tim Prince <tprince@computer.org> wrote:

>"Madhusudan Singh" <spammers-go-here@yahoo.com> wrote in message
>news:2g5aifF4de2qU1@uni-berlin.de...

[color=darkred]
>If you Google, or even look at your installation, you should be better
>enlightened. Assuming that you have installed all the files which come with
>ifc, you are missing a sym-link or permissions which would make that file
>show up readable in /usr/lib. I think that's close to what the message says,
>given that an NLSPATH environment setting might do the job. The installation
>script would have done one or both of those for you on supported
>environments, so that's one of the chores you take on for yourself on
>Debian.

And when you solve it, you may get to move on to corruption issues on
that file like we get on FreeBSD :)

hawk
--
Richard E. Hawkins, Asst. Prof. of Economics /"\ ASCII ribbon campaign
dochawk@psu.edu 111 Hiller (814) 375-4846 \ / against HTML mail
These opinions will not be those of X and postings.
Penn State until it pays my retainer. / \

Sponsored Links