iraf.net

>From friedel@wise1.tau.ac.il Mon Jan 27 23:10:28 1997
Subject: Re: installing ctio in Linux
To: fitz@noao.edu (Mike Fitzpatrick)Hi, Mike.I forgot to mention that I did use 'ctio-bin.linux.gz' from your anonymous
ftp. Should I leave the link 'bin' to bin.generic, or change it to 'bin.linux'?I also tried: mkpkg -p ctio linux, and got following error-message:
ct> mkpkg -p ctio linux
Warning, mkpkg line 76: could not find mkpkg module or label `linux'
Warning, mkpkg line 76: no entry in mkpkg file for `linux'Friedel>From fitz Mon Jan 27 23:12:44 1997
To: friedel@wise1.tau.ac.il
Subject: Re: installing ctio in LinuxFriedel,
In that case, all you need to do is create a "bin.linux" directory and
unpack the tar file in there. Any mkpkg command will try to build from sources
or reconfigure the architecture (which also won't work). Once the binaries
are installed just declare the package in hlib$extern.pkg and it should work.
Let me know if you still have problems.Cheers,
-Mike>From friedel@wise1.tau.ac.il Mon Jan 27 23:16:41 1997
Subject: Re: installing ctio in Linux
To: fitz@noao.edu (Mike Fitzpatrick)Hi, Mike.But this is exactly what I did. I created a "bin.linux" sub-directory, unpacked
the ctio-binaries for linux, and after declaring the packing in extern.pkg,
I typed:ctio
cd ctio
mkpkg -p ctio update >& spoolFriedel>From fitz Mon Jan 27 23:18:20 1997
To: friedel@wise1.tau.ac.il
Subject: Re: installing ctio in Linux> the ctio-binaries for linux, and after declaring the packing in extern.pkg,
At this point you're done, no need for a mkpkg after this. Can you
access the tasks now?-Mike>From friedel@wise1.tau.ac.il Tue Jan 28 00:25:52 1997
Subject: Re: installing ctio in Linux
To: fitz@noao.edu (Mike Fitzpatrick)Hi, Mike.Oh, I did'nt know that it was so simple. I looked at the cito.readme - file,
where I found the instruction about running mkpkg, but it is not clear
from the readme-file, that if one has already the binaries, it is unnecessary
to build the package with mkpkg. Seems to be so obvious, that is'nt
worthwhile to mention.... If in the future, if there will be a patch for one of the tasks, then how can
I rebuild the package?About a week ago, I also reported about error-messages when I tried to
compile the TABLES package. By the way, it happens for Linux 2.0.0, and not for
Linux 1.2.13. Anyhow, Ray from STSDAS helped me with the compilation.
But now I understand that I should'nt have to bother running mkpkg at all,
if I use the pre-compiled binaries: tables134-bin.linux.gz and for STSDAS
stsdas135-bin.linux.gz.
I also found at your anonymous ftp: stsdas_linux_patch.readme.
Do tables134-bin.linux.gz and stsdas135-bin.linux.gz already contain
the patch? If not, one has to run mkpkg in any case.Thank you very much for your help and quick response.Friedel>From fitz Tue Jan 28 00:49:33 1997
To: friedel@wise1.tau.ac.il
Subject: Re: installing ctio in LinuxFriedel,
Patches for external packages are handled on a case-by-case basis.
For STSDAS/TABLES we did the source patch so you could build from source
(because downloading binaries to a PC might take a while, the patch was
faster); in that case you'd unpack the source from ST and untar the patch
file, the package should then compile with a normal mkpkg command as per
the instructions. Most packages where you see a <pkg>-bin.linux file
available all you need is to untar the binaries and not bother w/ recompilation.
For packages we control build errors on Linux are usually fixed quickly and
we regenerate the package, for CTIO/STSDAS/TABLES etc the best we can do
is provide binaries and alert the responsible group about the code changes
needed. To answer your question, yes the STSDAS/TABLES binaries we provide
do contain the patches and all binaries you'd normally get.
I suppose we need to review all the *.readme files to bring them up
to date, but there's too much else to do at the moment! Cheers,
-Mike