iraf.net

when I tested an image for my nmisc package, I got the following errors:
anybody know why? thanks
[i:836d90e7da]
ecl> nmisc
ccdmask kpnofocus psfmeasure starfocus xregister
fixpix newimexamine specfocus text2mask nmisc> starf
ERROR: Cannot open connected subprocess (./x_nmisc.e)
nmisc> starfocus
ERROR: Cannot open connected subprocess (./x_nmisc.e)
nmisc> kpnofocus
List of focus images: ct*
Mark the top star (in unflipped display).
ERROR: Cannot open connected subprocess (./x_nmisc.e)
"iterations=iterations)"
line 40: nmisc$src/kpnofocus.cl
called as: `kpnofocus ()'[/i:836d90e7da]

The messages mean that either the binaries weren't installed/built, or they are in the wrong directory. If you installed pre-built binaries, be sure you have the right architecture and that they are in the proper nmisc$bin.<arch> directory, where you can determine what the proper <arch> value should be with "cl> show arch".If you built from source, be sure you reconfigured the package for the architecture before compiling, otherwise they might have ended up in the bin.generic directory which should be empty. If they're there, you can simply move them, otherwise be sure you compiled with, e.g.[code:1:e20de8da4a]
mkpkg -p nmisc redhat <-- reset architecture
mkpkg -p nmisc <--- build it
[/code:1:e20de8da4a]Errors during the build could be other problems, please reply with the type of machine/OS you're using or try using pre-built binaries.-Mike

Thanks for your reply, but I 'm confused, let me list the steps I used:
from ftp://iraf.noao.edu/iraf/extern-v212/nmisc020618/nmisc.readme , I created my nmisc directory in [i:46caab6b3b]/home/iraf/extern/nmisc[/i:46caab6b3b], then in [i:46caab6b3b]/home/iraf/iraf/unix/hlib[/i:46caab6b3b] I added the following lines in extern.pkg
[i:46caab6b3b]
reset nmisc = /iraf/extern/nmisc/task $nmisc.pkg = nmisc$nmisc.cl ,nmisc$lib/helpdb.mip\[/i:46caab6b3b]
downloaded nmisc.tar.z into /nmisc, then extract it here.on step 5 in the readme file:
[i:46caab6b3b][5] Check for a binary directory for the system you are building;
i.e. bin.sparc, bin.ssun, bin.linux, bin.alpha, etc.
If it is not there create it with (for example): cl> mkdir bin.dmip[/i:46caab6b3b]
I actually not quite understand the meaning, anyway I have the following directories so I just skipped this step:
[i:46caab6b3b]iraf@astronomy-desktop% cd nmisc
iraf@astronomy-desktop% ls
total 500
0 bin@ 4 bin.ssun/ 4 nmisc.hd 16 README
4 bin.generic/ 4 demos/ 4 nmisc.men 12 spool.redhat
4 bin.linux/ 4 lib/ 4 nmisc.par 12 spool.sparc
4 bin.redhat/ 4 mkpkg 12 nmisc.spool 12 spool.ssun
4 bin.sparc/ 4 nmisc.cl 384 nmisc.tar.Z 4 src/
[/i:46caab6b3b]
now for the last step 6, I guess I might make a mistake, I followed
[i:46caab6b3b]cl>mkpkg -p nmisc -p noao update >& nmisc.spool &[/i:46caab6b3b]
but I don;t understand :
[i:46caab6b3b]NOTE: On systems that concurrently support different architectures
(e.g., Suns, Convex), you must configure the system for the desired
architecture before issuing the above command. SUN/IRAF sites must
execute a pair of 'mkpkg' commands for each supported architecture type.
The Unix environment variable IRAFARCH must be set as well before
compiling. For example:
# Assuming IRAFARCH is set to ffpa
cl> mkpkg -p nmisc -p noao ffpa
cl> mkpkg -p nmisc -p noao update >& nmisc.ffpa &
cl> mkpkg -p nmisc -p noao f68881
# Now reset IRAFARCH to f68881 before continuing
cl> mkpkg -p nmisc -p noao update >& nmisc.f68881 &
[/i:46caab6b3b]
and just skipped this step, so any problems here? thanks[quote:46caab6b3b="fitz"]The messages mean that either the binaries weren't installed/built, or they are in the wrong directory. If you installed pre-built binaries, be sure you have the right architecture and that they are in the proper nmisc$bin.<arch> directory, where you can determine what the proper <arch> value should be with "cl> show arch".If you built from source, be sure you reconfigured the package for the architecture before compiling, otherwise they might have ended up in the bin.generic directory which should be empty. If they're there, you can simply move them, otherwise be sure you compiled with, e.g.[code:1:46caab6b3b]
mkpkg -p nmisc redhat <-- reset architecture
mkpkg -p nmisc <--- build it
[/code:1:46caab6b3b]Errors during the build could be other problems, please reply with the type of machine/OS you're using or try using pre-built binaries.-Mike[/quote:46caab6b3b]

I'm using ubuntu 9.04, and under[i:7b2a2cf450] /home/iraf/extern/nmisc[/i:7b2a2cf450] all bin.** directories are empty:
[i:7b2a2cf450]astronomy@astronomy-desktop:/home/iraf/extern/nmisc$ ls
bin bin.sparc mkpkg nmisc.par spool.redhat
bin.generic bin.ssun nmisc.cl nmisc.spool spool.sparc
bin.linux demos nmisc.hd nmisc.tar.Z spool.ssun
bin.redhat lib nmisc.men README src[/i:7b2a2cf450][quote:7b2a2cf450="fitz"]The messages mean that either the binaries weren't installed/built, or they are in the wrong directory. If you installed pre-built binaries, be sure you have the right architecture and that they are in the proper nmisc$bin.<arch> directory, where you can determine what the proper <arch> value should be with "cl> show arch".If you built from source, be sure you reconfigured the package for the architecture before compiling, otherwise they might have ended up in the bin.generic directory which should be empty. If they're there, you can simply move them, otherwise be sure you compiled with, e.g.[code:1:7b2a2cf450]
mkpkg -p nmisc redhat <-- reset architecture
mkpkg -p nmisc <--- build it
[/code:1:7b2a2cf450]Errors during the build could be other problems, please reply with the type of machine/OS you're using or try using pre-built binaries.-Mike[/quote:7b2a2cf450]

For Ubuntu the architecture is 'linux'. It sounds like you didn't reconfigure the package architecture and so the binary is in the bin.generic directory. You can simply download https://iraf.net/ftp/iraf/extern/nmisc-bin.linux.tar.gz and unpack it in the /iraf/extern/nmisc directory and it'll create the needed bin.linux directory.-Mike

thank you very much1, it works!but I still do not feel well about the following paragraph in readme file because I did not understand it and skipped it! Are u sure this is not a problem for me?[i:abdae1f9fc]NOTE: On systems that concurrently support different architectures
(e.g., Suns, Convex), you must configure the system for the desired
architecture before issuing the above command. SUN/IRAF sites must
execute a pair of 'mkpkg' commands for each supported architecture type.
The Unix environment variable IRAFARCH must be set as well before
compiling. For example:
# Assuming IRAFARCH is set to ffpa
cl> mkpkg -p nmisc -p noao ffpa
cl> mkpkg -p nmisc -p noao update >& nmisc.ffpa &
cl> mkpkg -p nmisc -p noao f68881
# Now reset IRAFARCH to f68881 before continuing
cl> mkpkg -p nmisc -p noao update >& nmisc.f68881 & [/i:abdae1f9fc]
[quote:abdae1f9fc="fitz"]For Ubuntu the architecture is 'linux'. It sounds like you didn't reconfigure the package architecture and so the binary is in the bin.generic directory. You can simply download https://iraf.net/ftp/iraf/extern/nmisc-bin.linux.tar.gz and unpack it in the /iraf/extern/nmisc directory and it'll create the needed bin.linux directory.-Mike[/quote:abdae1f9fc]

NMISC is an old package, and the README file is even older (from a time when Sun-3 systems had different floating-point architectures). The concept that an external package needs to be reconfigured for the particular architecture still holds, but I agree some (many?) of the readme files should be updated.Skipping that paragraph was fine, just remember for other packages that the first command you give (on Ubuntu) is[code:1:58ea7895b1]mkpkg -p <pkgname> linux[/code:1:58ea7895b1]-Mike