View on GitHub

IRAF Community Distribution

IRAF maintained by the community

Home | Installation | Packages | X11IRAF | PyRAF | Forum ↗

iraf-v216 · Code · Issues (50) · Pull requests (81)

iraf.net Issue #114

[MacOS] /usr/bin/ftp not found on MacOS High Sierra

closed closed olebole opened this issue on 2017-11-17


olebole commented on 2017-11-17

This is taken from the Forum (@evertonbt?)

I cannot download any packages from http://iraf.noao.edu using Safari (I can do it using another web browser). But this is an easy issue to avoid.

The installation for user sounds working nicely - Iraf seems to be working too, but it hasn’t the external packages installed for default. So I tried to follow the instructions, using the ./configure into the extern directory, to work with the packages I need, and the results are always:

sudo ./configure  
Password:  
Initializing repository data ....  
Cannot download repository manifest file, quitting.  
Creating system makefile ....  
Setup Complete.  
cat: .repo_pkgs: No such file or directory  
 
 
   To install packages, use 'ls' to list the currently available  
   packages from the IRAF repository.  For each package you wish  
   to install, use the command:  
 
     make <pkg>  
 
   The package will be loaded dynamically the next time you start  
   the CL session.  
 
   Use the commmands:  
 
     make update       # to update pkgs to the latest repository version  
     make check        # to list available updates  
     make clean        # to delete installed all packages  
     make init         # restore to pre-configure state  
     make <pkg>        # to force a re-install of named <pkg>  

For some reason, i couldn’t find, it cannot connect to the repositories, like Safari couldn’t. May be it is a correlated issue.
Another thing is that the repositories seems to be working too.
It started since may computer updated to High Sierra.

Someone has any idea how I could solve this.

Thanks,

Everton

The problem is a missing binary /usr/bin/ftp in High Sierra.

This issue is to ensure it will be fixed in the code.


Fixed in #115


Last updated on 2017-11-17