View on GitHub

IRAF Community Distribution

IRAF maintained by the community

Home | Installation | Packages | X11IRAF | PyRAF | Forum

ecl or cl failure

Hong Bae Ann wrote on Nov 24, 2009

Recently installed irafv2.14 but failed to login into
IRAF when I execute ecl or cl. Following is the error message returned,

Initialize uparm? (y|n): y
-- initializing uparm
Terminal types: xgterm,xterm,gterm,vt640,vt100,etc.
Enter terminal type: xgterm &
A new LOGIN.CL file has been created in the current directory.
You may wish to review and edit this file to change the defaults.
/home/hbann% ecl
setting terminal type to xgterm U_TERM...
Warning: No entry in device capabilities file for device (U)
ERROR: Cannot open connected subprocess (./x_system.e)
called as: `prcache (directory)'
called as: `cl ()'
called as: `cl ()'
Error while reading login.cl file - may need to rebuild with mkiraf
Fatal startup error. CL dies.
[img]http://webmail.pusan.ac.kr/cgi-bin/setconfirm.cgi?k=125902776241873521090&u=hbann&d=pusan.ac.kr[/img]
Post generated using Mail2Forum (http://www.mail2forum.com)

Mike Fitzpatrick wrote on Nov 24, 2009

The U_TERM is a placeholder in the default login.cl file that should be replaced by 'xgterm' or whatever you replied when you first did the MKIRAF command. I don't understand how you ended up with an "stty xgterm U_TERM" command in the file. There are similar variable like U_USER also meant to be replaced so I'd try the MKIRAF again and then check the login.cl file to see that it was edited correctly.

The message about not finding x_system.e indicates either a wrong setting of $iraf in your environment or something wrong with the installation. This may be related to the above problem. You can try rerunning the iraf install script and look for any error messages it finds about improper structures/files, you'll need to correct these until the install script runs without errors. If you're not sure what the messages mean, just post them.

-Mike

Last post on Nov 24, 2009