mkpkg relink
ygrange wrote on Mar 30, 2006
Hi there,
I have a question about phot. I would like to crank up the precision of the magnitude error (just for illustrative cases, I know this might be unnecessary for most cases). To get `better' precision I already found posts about editing the apphot package. For this the answer says that I should use:
cl> mkpkg relink
When I do this, I get:
checkout: Undefined variable.
what do I do wrong?
I have a question about phot. I would like to crank up the precision of the magnitude error (just for illustrative cases, I know this might be unnecessary for most cases). To get `better' precision I already found posts about editing the apphot package. For this the answer says that I should use:
cl> mkpkg relink
When I do this, I get:
checkout: Undefined variable.
what do I do wrong?
Mike Fitzpatrick wrote on Mar 30, 2006
Sounds like you're executing the 'mkpkg' file itself rather than the command. Since this is defined as a foreign task be sure that the mkpkg file is not executable and that your .cshrc/.bashrc file defines a path that picks up the mkpkg command first. This is installed in the same directory as the 'cl' command, do a "which mkpkg" or "cl> !which mkpkg" to find out where it is on your machine.
Also, I'm assuming you're doing this from the digiphot$phot directory? Be sure to include the "-p noao -p tables" flags to pick up the needed package environments, that you've defined a $iraf and $IRAFARCH in your .cshrc file, and that you've reset the NOAO package architecture first, e.g.
cl> cd noao$
cl> mkpkg -p noao redhat # reset architecture
cl> cd digiphot/apphot # go to package dir
cl> mkpkg -p noao -p tables update
The "relink" target doesn't exist in the phot$mkpkg file, you'll need to compile from the main apphot dir and use 'update' to install a new binary. Hope this helps.
Cheers,
-Mike
Also, I'm assuming you're doing this from the digiphot$phot directory? Be sure to include the "-p noao -p tables" flags to pick up the needed package environments, that you've defined a $iraf and $IRAFARCH in your .cshrc file, and that you've reset the NOAO package architecture first, e.g.
cl> cd noao$
cl> mkpkg -p noao redhat # reset architecture
cl> cd digiphot/apphot # go to package dir
cl> mkpkg -p noao -p tables update
The "relink" target doesn't exist in the phot$mkpkg file, you'll need to compile from the main apphot dir and use 'update' to install a new binary. Hope this helps.
Cheers,
-Mike
ygrange wrote on Mar 30, 2006
Hmm. I think this will not really work. I am not root and I can not run the mkpkg-task (no permissions). I tried to copy the mkpkg file to my homedir and run it but it just returns that I have bad placed ()'s.
Is there anything I could do to make this work, or should I just not bother to try any further?
Is there anything I could do to make this work, or should I just not bother to try any further?
Mike Fitzpatrick wrote on Mar 30, 2006
All users should be able to run the MKPKG command assuming the permissions on the file aren't restriciting it. The command is in the same directory as the 'cl' command so first find that directory and the 'mkpkg' symlink. The link will point t o $iraf/unix/bin.<arch>/mkpkg.e, if the link is wrong or the permissions on this file are restrictive you'll get an error message. Next is the matter of whether you can modify the iraf installation itself: I've been assuming you were doing this as 'iraf' or 'root' or whoever owns the iraf files. If not you should still be able to copy the entire directory tree and recompile it for personal use, but note the package will need to be redeclared to fiind your copy, e.g.
% cp -rp $iraf/noao/digiphot/apphot /tmp/apphot
% cd /tmp/apphot
% mkpkg -p noao -p tables relink
and once logged into the CL do
cl> task phot = /tmp/phot/xx_apphot.e
You should then be using the modified version.
-Mike
% cp -rp $iraf/noao/digiphot/apphot /tmp/apphot
% cd /tmp/apphot
% mkpkg -p noao -p tables relink
and once logged into the CL do
cl> task phot = /tmp/phot/xx_apphot.e
You should then be using the modified version.
-Mike
ygrange wrote on Mar 30, 2006
Hmm. The permissions of mkpkg are set 644, so I can not run it. Well' i'll just find a way to make my graph.
Last post on Mar 30, 2006