links in IRAF 2.14

Robert Janusz wrote on Jan 26, 2008

I installed IRAF 2.14 on Linux/Debian and it works fine. But I have noticed that
there are unresolved links in:
(1) iraf/iraf/lib - some can be corrected by changing
iraf/iraf/bin -> bin.linux (not to bin.generic)
(2) simirar - unresolved links in:
iraf/iraf/noao/lib
iraf/iraf/unix
iraf/iraf/unix/hlib - some can be corrected by adding in iraf/iraf/unix:
as.generic -> as.linux
bin.generic -> bin.linux

I wold like to know why there are such unresolved links? Thank you.

---

Mike Fitzpatrick wrote on Jan 26, 2008

The links are resolved when the system is configured for development (i.e. a "mkpkg linux" that resets the 'bin' link to point to 'bin.linux'). Most packages are declared to install any libraries in a 'lib' directory, but there is also a search path of sort that finds them in 'bin.<arch>' directories. The unresolved links are normal for a generic system.

-Mike

---

Jason Quinn wrote on Jan 26, 2008

I just downloaded and installed IRAF 2.14 from the frontpage of iraf.net. The info that comes up when IRAF is says "NOAO/IRAFNET PC-IRAF Revision 2.14 Fri Nov 30 15:27:05 MST 2007". The date there concerns me. Does this version include the fixes for the IMIO interface routine?

I also had trouble with libtermcap.so.2 again. The fix was to create a link to libtermcap.so.

---

Last post on Jan 26, 2008