astorrs |
03/08/2007 07:02PM (Read 8055 times)
|
|
|
Status: offline
Registered: 03/07/2007
Posts: 7
|
Got the binaries downloaded and tar'd-- now Cygwin doesn't appear to know about "setenv" or "sudo". Are there alternatives to these commands in Cygwin? Do I need to install more than the basic package?Thanks!Alex Storrs
|
|
|
|
fitz |
03/08/2007 07:02PM
|
|
|
Status: offline
Registered: 09/30/2005
Posts: 4040
|
The 'setenv' is a C-shell thing, you can just type "csh" at your bash prompt to start a C-shell and then follow the installation guide that assumes a C-shell. The bash equivalent uses the 'set' and 'export' to define variables but the first option is easiest. You can ignore the 'sudo' parts of the installation, under Cygwin jsut execute the commands as yourself.-Mike
|
|
|
|
astorrs |
03/08/2007 07:02PM
|
|
|
Status: offline
Registered: 03/07/2007
Posts: 7
|
Apparently I don't have a c shell in Cygwin. I get "bash: csh: command not found". I went back to the Cygwin site and checked through all the stuff I could install and couldn't find anything like "csh". Any idea what I can do to install this stuff?Thanks!Alex Storrs
|
|
|
|
fitz |
03/08/2007 07:02PM
|
|
|
Status: offline
Registered: 09/30/2005
Posts: 4040
|
Go back to the Cygwin setup panel, under the the 'Shells' menu, select 'tcsh' for installation (tcsh and csh are the same thing as far as we're concerned).-Mike
|
|
|
|
astorrs |
03/08/2007 07:02PM
|
|
|
Status: offline
Registered: 03/07/2007
Posts: 7
|
Got tcsh downloaded and installed-- it runs o.k. but when I try to use the iraf environment variable (after doing the setenv) by changing the directory ("cd $iraf/unix/hlib") I get dumped back in my home directory-- the system doesn't appear to know about $iraf even though it didn't complain when I defined it. Any thoughts?Thanks!Alex
|
|
|
|
fitz |
03/08/2007 07:02PM
|
|
|
Status: offline
Registered: 09/30/2005
Posts: 4040
|
Where does "cd $iraf" take you? Is there a 'unix' subdirectory there? You can set any variable to be anything you like, including an invalid path. Normally $iraf is /iraf/iraf but this assumes you created a /iraf directory first, and then in there created another 'iraf' directory where you unpacked the as.pcix.gen file. For the binaries you need to have a /iraf/irafbin directory containing a 'bin.cygwin' and 'noao.bin.cygwin' directory for the IB and NB files respectively.-Mike
|
|
|
|
astorrs |
03/08/2007 07:02PM
|
|
|
Status: offline
Registered: 03/07/2007
Posts: 7
|
Thanks! I had installed in the "Program Files" subdirectory on my machine, and while I could setenv iraf "/cygdrive/c/Program Files/iraf/iraf" when I tried to use $iraf cygwin was treating the thing as two variables (/cygdrive/c/Program and Files/iraf/iraf/). Not knowing what to do with this (well, I wouldn't, either) it sent me back to my home directory.So now I'm set up with the iraf directory tree in a path that doesn't use spaces, and the iraf environment variable properly set, and when I go to $iraf/unix/hlib and type ./install I get an error complaining about the permissions in the path. I'm not worried about permissions, I'm the only one who will be using this installation. Can I get around this in some elegant manner?Thanks again!Alex Storrs
|
|
|
|
fitz |
03/08/2007 07:02PM
|
|
|
Status: offline
Registered: 09/30/2005
Posts: 4040
|
If you're doing the install from the Cygwin shell window just think in terms of '/' as
the root directory, even if this is stored in /cygdrive/.... as far as Windows is concerned. The permission check is done for multi-user systems where the default permission mask used by the person doing the install might keep others on the machine from being able to read the iraf tree, this should probably be relaxed for Cygwin systems. Until then, you can issue a command like[code:1:94df29e56c]chmod 755 $iraf [/code:1:94df29e56c]Then try running the install script again.-Mike
|
|
|
|
astorrs |
03/08/2007 07:02PM
|
|
|
Status: offline
Registered: 03/07/2007
Posts: 7
|
Thanks again, that did the trick. I had to go to each level individually to set the proper protection (chmod 755 $iraf didn't do it, for some reason) but now the installation appears to have worked o.k. Might want to revise some docs. on installation on Windows systems, if you haven't already. Or am I the only IRAF/Windoze user?Cheers,Alex
|
|
|
|