IRAF 2.16 extern packages misplaced binaries?
npirzkal wrote on Mar 26, 2012
When using the IRAF extern system and installing fitsutil, all is well and the binaries are placed in bin.macintel.
However, both the TABLES and STSDAS package installs place the binaries in bin.macosx instead of bin.macintel.
Is this a known bug? It seems that the binaries that are distributed are identical to the ones distributed by STScI and I was able to keep pyraf happy by linking bin.macintel to bin.macosx but that seems wrong :-)
However, both the TABLES and STSDAS package installs place the binaries in bin.macosx instead of bin.macintel.
Is this a known bug? It seems that the binaries that are distributed are identical to the ones distributed by STScI and I was able to keep pyraf happy by linking bin.macintel to bin.macosx but that seems wrong :-)
Mike Fitzpatrick wrote on Mar 26, 2012
It's not a bug. STScI has no plans to upgrade STSDAS/TABLES to be 64-bit (see http://www.stsci.edu/institute/software_hardware/stsdas/iraf64) and so we just package whatever version they put out to work with the repository system for external packages.
For the CL this isn't a problem since it will fallback to use a different (older) architecture if the current arch binaries aren't available, so on a macintel system the macosx binaries will do. If PyRAF doesn't do this then making the symlink is probably the best that can be done, "wrong" or not. Note the same applies to other external packages that haven't been/won't be updated either.
For the CL this isn't a problem since it will fallback to use a different (older) architecture if the current arch binaries aren't available, so on a macintel system the macosx binaries will do. If PyRAF doesn't do this then making the symlink is probably the best that can be done, "wrong" or not. Note the same applies to other external packages that haven't been/won't be updated either.
Last post on Mar 26, 2012