iraf on suse 10.1
iraf_user wrote on Aug 08, 2006
Hello,
I have installed iraf (v2.12)on my laptop that runs suse 10.1 The installation scripts run with no problems but when created an iraf directory in my home directory, this is what i get:
home/user/iraf> mkiraf
mkiraf: Command not found.
I also tried to run mkiraf this way:
/home/user/iraf> /bin/csh /iraf/iraf/unix/hlib/mkiraf.csh
-- creating a new uparm directory
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/user/iraf> /bin/csh /iraf/iraf/unix/hlib/cl.csh
os.zgtenv: cannot open `/usr/include/iraf.h'
task `cl' has no param file
Fatal startup error. CL dies.
Any ideas about what might be the problem?
Thank you!
I have installed iraf (v2.12)on my laptop that runs suse 10.1 The installation scripts run with no problems but when created an iraf directory in my home directory, this is what i get:
home/user/iraf> mkiraf
mkiraf: Command not found.
I also tried to run mkiraf this way:
/home/user/iraf> /bin/csh /iraf/iraf/unix/hlib/mkiraf.csh
-- creating a new uparm directory
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/user/iraf> /bin/csh /iraf/iraf/unix/hlib/cl.csh
os.zgtenv: cannot open `/usr/include/iraf.h'
task `cl' has no param file
Fatal startup error. CL dies.
Any ideas about what might be the problem?
Thank you!
Mike Fitzpatrick wrote on Aug 08, 2006
Be sure you ran the install script, and without the '-n'
flag. It sounds as it the commands weren't actually installed,
or the place they were installed isn't in your path, and that
the /usr/include/iraf.h link doesn't exist or is invalid (i.e. you
didn't run as root or specified the wrong $iraf that the install
script should have warned about).
-Mike
flag. It sounds as it the commands weren't actually installed,
or the place they were installed isn't in your path, and that
the /usr/include/iraf.h link doesn't exist or is invalid (i.e. you
didn't run as root or specified the wrong $iraf that the install
script should have warned about).
-Mike
iraf_user wrote on Aug 08, 2006
Thank you!
I run ./install without the -n and now it works fine!
Thank you again for the help!
I run ./install without the -n and now it works fine!
Thank you again for the help!
Last post on Aug 08, 2006