Welcome to iraf.net Wednesday, November 22 2017 @ 11:58 PM GMT


 Forum Index > Help Desk > Applications New Topic Post Reply
 Xgterm can't start up ds9 and cl commands
   
anthonyvun
 10/27/2017 03:14AM (Read 335 times)  
+----
Newbie

Status: offline


Registered: 10/26/2017
Posts: 10
Mac Sierra
Installed iraf in home, ds9 in Applications
At xgterm, entered "ds9 &" - it says : bash: ds9: command not found
and when entered cl - it says: task `cl' has no param file. Fatal startup error. CL dies.

Anyone have any idea?

 
Profile Email
 Quote
fitz
 10/27/2017 12:32PM  
AAAAA
Admin

Status: offline


Registered: 09/30/2005
Posts: 3988
DS9 must be installed separately from http://ds9.si.edu, but generally a 'command not found' either means the command wasn't installed, or was installed to a directory not in your default search path (e.g. /usr/local/bin). When this happens with the 'cl' command it usually either means the install script wasn't run or that you've defined a $iraf environment variable with the wrong path or incorrectly (e.g. with no trailing '/').

Since this is High Sierra, see also http://iraf.net/forum/viewtopic.php?showtopic=1469698 for a discussion of XQuartz differences in the event you didn't install the native DS9 package.

 
Profile Email
 Quote
anthonyvun
 10/28/2017 01:46AM  
+----
Newbie

Status: offline


Registered: 10/26/2017
Posts: 10
During installation these 2 procedures failed.

Checking for /iraf symlink ... [ OK ]
Checking /usr/include directory ... mkdir: /usr/include: Operation not permitted
[ FAIL ]
Creating symlink ... ln: /usr/include/iraf.h: No such file or directory
[ FAIL ]
Creating iraf command links in local bin dir ... [ OK ]
Marking system update time hlib$utime ... [ OK ]

When I checked /usr/include/. there is no iraf.h

So I thought maybe I can force include iraf.h in /usr/include/ - but even with sudo ln or sudo mkdir - these processes weren't allowed

Is there anyway around this?
Thank you very much

 
Profile Email
 Quote
fitz
 10/28/2017 02:11PM  
AAAAA
Admin

Status: offline


Registered: 09/30/2005
Posts: 3988
Sierra and later versions implement somthing called 'SIP' that prevents writing to system directories like /usr/include, You can Google for how to disable this but in the standard distribution it is only a problem when running "install --system", the default install script will write files only to your user directory (but that may mean you need to reload your .bashrc/.cshrc file to pick up the paths and environment variables). The /usr/local directory is normally still writable on Sierra, setting a $iraf environment variable yourself (e.g. "/iraf/iraf/", must have trailing '/') can be used when there is no file.

 
Profile Email
 Quote
anthonyvun
 10/30/2017 12:54AM  
+----
Newbie

Status: offline


Registered: 10/26/2017
Posts: 10
Okay, I have disabled the SIP on Mac.

Would you recommend me to
1. force the iraf.h symlink with "sudo ln /usr/include/iraf.h"

OR

2. Reinstall everything
- If I just re-run installation again, would that cause a duplication or it is okay to just overwrite the first one already installed
- Otherwise,I suppose I have to uninstall the iraf first to prevent duplication. In this case, whats the best way for uninstall

Because mainly I also forgot if I actually define "/iraf/iraf" or "/iraf/iraf/" (with the trailing "/" mentioned) - when I tried cd to both paths, they both link to the same directory and pwd defines it as "/iraf/iraf" - So im guessing maybe I did not define as "/iraf/iraf/" as suggested

Sorry for the bombarding questions because Im quite new to this and Thank you in advance!
Anthony

 
Profile Email
 Quote
fitz
 10/30/2017 03:08AM  
AAAAA
Admin

Status: offline


Registered: 09/30/2005
Posts: 3988
It is preferable to rerun the install script (as root or with sudo) than to try to create links manually, it is safe to do multiple times and required after a system update (that wipes e.g. /usr/include) or when you move the iraf tree (remember the trailing '/', it is used to construct other paths from the $iraf root).

 
Profile Email
 Quote
anthonyvun
 10/30/2017 10:07AM  
+----
Newbie

Status: offline


Registered: 10/26/2017
Posts: 10
Hello again - So I tried install iraf again and making sure it is "/iraf/iraf/" path - But what I don't understand is, no matter how hard I try to define it as "/iraf/iraf/" the pwd path is /iraf/iraf (without the trailing "/") . Theres no difference if I cd /iraf/iraf or /iraf/iraf/. Just curious whats the point of actually including the trailing "/" strongly specified

On Sierra. - For reference, I followed installation info here: http://www.iac.es/sieinvens/siepedia/pmwiki.php?n=HOWTOs.IrafMacOSX

Overall result:
- calling out "cl" in xgterm - command not found (compared to last time- cl has no param)
- This time iraf.h is in /usr/include
- Calling "ds9 &" on xgterm- command not found (I have successfully installed ds9 in Applications - but cannot be called upon)

During the installation, the errors are as follow (some I presume due to duplication of previously installed):
Editing iraf/imdir/cache paths into system files ... [ FAIL ]
*** File
Creating symlink ... ln: /usr/include/iraf.h: Operation not permitted
[ FAIL ]

Creating 'voclientd' symlink ... ln: /usr/local/bin/voclientd: File exists
[ FAIL ]

Creating 'voclient.jar' symlink ... ln: /usr/local/bin/voclient.jar: File exists
[ FAIL ]

Creating /usr/local/lib/imtoolrc link ... ln: /usr/local/lib/imtoolrc: File exists
[ FAIL ]



- What procedures should I proceed
- Also, in the cd ~//iraf, there is login.cl: Im curious if I actually need a username and password for the login? where do I get them and what is it for mainly?

Would really appreciate for your consistent support to help me solve this successfully - Stressing over completing the installation. Thanks a million!

 
Profile Email
 Quote
anthonyvun
 10/31/2017 12:06AM  
+----
Newbie

Status: offline


Registered: 10/26/2017
Posts: 10
Okay - I have retried it again. and this time it works. (But 1 issue left!) Frown

iraf.h is in /usr/include
- when call " eco" or "cl" in xgterm , it responds:

os.zgtenv: cannot open `/usr/include/iraf.h'
task `cl' has no param file
Fatal startup error. CL dies.


This time in xgterm, ds9 & worked and the rest seems fine. This time I installed everything by disabling the SIP

Can you kindly answer me why does this issue remains?

Thank you very much

 
Profile Email
 Quote
anthonyvun
 10/31/2017 02:17AM  
+----
Newbie

Status: offline


Registered: 10/26/2017
Posts: 10
Nevermind - I solved it finally!

I found the problem to be the previously force included iraf.h in /usr/include. as I realise that file cannot be open. Then I force erase it and re-run everything. The symlink worked this time and ecl worked! Woohoo! Big Grin

Thanks for the hints!

 
Profile Email
 Quote
   
Content generated in: 0.18 seconds
New Topic Post Reply

Normal Topic Normal Topic
Sticky Topic Sticky Topic
Locked Topic Locked Topic
New Post New Post
Sticky Topic W/ New Post Sticky Topic W/ New Post
Locked Topic W/ New Post Locked Topic W/ New Post
View Anonymous Posts 
Anonymous users can post 
Filtered HTML Allowed 
Censored Content 
dog allergies remedies cialis 20 mg chilblain remedies


Privacy Policy
Terms of Use

User Functions

Login