Welcome to iraf.net Friday, March 29 2024 @ 05:02 AM GMT


 Forum Index > Help Desk > Systems New Topic Post Reply
 Errors with new 2.16.1 patch release?
   
wu_qso
 10/24/2013 02:50AM (Read 5084 times)  
++---
Junior

Status: offline


Registered: 06/04/2007
Posts: 29
I have downloaded the new version and installed it. But when I tried to run 'ecl', there are some errors shown on the screen as:

/iraf/iraf//unix/hlib/irafarch.sh: line 151: [: too many arguments
ERROR: No /iraf/iraf//bin./vocl.e binary found.
ERROR: IRAFARCH set to '', should be 'linux64'

What's the problem?

 
Profile Email
 Quote
fitz
 10/24/2013 03:41AM  
AAAAA
Admin

Status: offline


Registered: 09/30/2005
Posts: 4040
The script is assuming there is an IRAFARCH variable defined in your environment. Normally this would be picked up from your .cshrc/.bashrc running the $HOME/.iraf/setup.[c]sh script but there are reasons this might not have happened. I've fixed the script, for the moment just define a IRAFARCH or soure the setup file.

 
Profile Email
 Quote
wu_qso
 10/24/2013 04:11AM  
++---
Junior

Status: offline


Registered: 06/04/2007
Posts: 29
Thanks for your reply. There isn't a ".iraf" file in my home directory, not to say the setup file. Also, there seems to be an extra "/" after "/iraf/iraf/" from the error message I posted.

 
Profile Email
 Quote
fitz
 10/24/2013 04:17AM  
AAAAA
Admin

Status: offline


Registered: 09/30/2005
Posts: 4040

Didi you run the install script as just "./install" from your user account, or did you use a different user account (or a system install using "./install --system")? The install script should create a '.iraf' directory in your login directory (specifically $HOME/.iraf so check the value of $HOME), were there any errors from this script? If there is a /usr/include/iraf.h symlink on your machine then you have a "system install", perhaps from an earlier version. Even if you updated your iraf from v2.16, you should still run the install script from v2.16.1 to create the $HOME/.iraf setup.

 
Profile Email
 Quote
wu_qso
 10/24/2013 04:26AM  
++---
Junior

Status: offline


Registered: 06/04/2007
Posts: 29
I have used the "./install --system" to do a fresh installation and the installation was completed without any error. I have not defined the variable $iraf (as "/iraf/iraf"). Does it matter?

There is indeed a iraf.h file in the /usr/include directory, linked to "/iraf/iraf/unix/hlib/libc/iraf.h". The /usr/include/iraf.h file was created on July 4th, so it must be produced in the last installation.

 
Profile Email
 Quote
fitz
 10/24/2013 04:46AM  
AAAAA
Admin

Status: offline


Registered: 09/30/2005
Posts: 4040
In a system install the /usr/include/iraf.h and 'cl' command are supposed to define the $iraf and $IRAFARCH that are used, however I just found a way to cause the install script to NOT set the architecture properly in a system install which I will fix. In the meantime, define $IRAFARCH and $iraf explicity before you run the install script again. If you have a C-shell installed then you can use the old command scripts with the "--csh" flag, e.g.

% setenv iraf /iraf/iraf/
% setenv IRAFARCH linux64
% cd /iraf/iraf
% ./install --system --csh

Hope this fixes it.

 
Profile Email
 Quote
wu_qso
 10/24/2013 05:05AM  
++---
Junior

Status: offline


Registered: 06/04/2007
Posts: 29
I have used the commands you suggested to do the system installation. After a 'mkiraf', I ran a "ecl", here is the output of the computer:


NOAO/IRAF PC-IRAF Revision 2.16.1 EXPORT Mon Oct 14 21:40:13 MST 2013
This is the EXPORT version of IRAF V2.16 supporting PC systems.


Welcome to IRAF. To list the available commands, type ? or ??. To get
detailed information about a command, type `help '. To run a
command or load a package, type its name. Type `bye' to exit a
package, or `logout' to get out of the CL. Type `news' to find out
what is new in the version of the system you are using.

Visit https://iraf.net if you have questions or to report problems.


ERROR: Cannot open file (uparm$update)
called as: `cl ()'
called as: `cl ()'
called as: `cl ()'
"clbye()"
line 76: votools$votools.cl
called as: `votools ()'
called as: `cl ()'
"clbye()"
line 38: astcat$astcat.cl
called as: `astcat ()'
called as: `cl ()'
"clbye"
line 57: onedspec$onedspec.cl
called as: `onedspec ()'
called as: `cl ()'
called as: `cl ()'
called as: `cl ()'
called as: `cl ()'
"images # some of the preprocessors require hselect"
line 7: photcal$photcal.cl
called as: `photcal ()'
called as: `cl ()'
called as: `cl ()'
called as: `cl ()'
"dataio # rfits task required by aptest.cl script"
line 3: apphot$apphot.cl
called as: `apphot ()'
called as: `cl ()'
"clbye()"
line 15: digiphot$digiphot.cl
called as: `digiphot ()'
called as: `cl ()'
"clbye"
line 26: astutil$astutil.cl
called as: `astutil ()'
called as: `cl ()'
called as: `cl ()'
"images # for the script tasks findthresh, ndprep "
line 3: nproto$nproto.cl
called as: `nproto ()'
"nproto"
line 4: vo$vo.cl
called as: `vo ()'
called as: `cl ()'
called as: `cl ()'
called as: `cl ()'
"clbye()"
line 43: tv$tv.cl
called as: `tv ()'
called as: `cl ()'
called as: `cl ()'
called as: `cl ()'
"clbye()"
line 19: dataio$dataio.cl
called as: `dataio ()'
called as: `cl ()'
"clbye()"
line 41: plot$plot.cl
called as: `plot ()'
called as: `cl ()'
called as: `cl ()'
called as: `cl ()'
Error while reading login.cl file - may need to rebuild with mkiraf
Fatal startup error. CL dies.

An extra mkiraf did not fix the errors.

 
Profile Email
 Quote
fitz
 10/24/2013 05:09AM  
AAAAA
Admin

Status: offline


Registered: 09/30/2005
Posts: 4040

Do you have write permission on your uparm directory? The 'uparm' is defined as "home$uparm" in your login.cl, where the 'home$' is the directory where you ran the MKIRAF.

Does it matter whether you type 'ecl' versus 'cl'? If you run with "./install" to create a personal installation, does that make a difference (you can just delete $HOME/.iraf to undo this)?

 
Profile Email
 Quote
iancze
 10/25/2013 01:32AM  
+----
Newbie

Status: offline


Registered: 10/24/2013
Posts: 2
Hello,

I seem to run into the same problems when installing iraf.lnux.x86_64.tar.gz on my linux64 system.

I was able to get the package to install system-wide correctly by switching to cshell and by doing this:

PHP Formatted Code

% setenv iraf /iraf/iraf/
% setenv IRAFARCH linux64
% cd /iraf/iraf
% ./install --system --csh
 


However, when I log out of root and go back to my regular user, do `mkiraf` inside /home/ian/iraf/ and then try to start cl or ecl from an xgterm, I get the same

PHP Formatted Code

ERROR: Cannot open file (uparm$update)
called as: `cl ()'
called as: `cl ()'

called as: `cl ()'
"clbye()"
line 76: votools$votools.cl
called as: `votools ()'

called as: `cl ()'
"clbye()"
.....
Error while reading login.cl file - may need to rebuild with mkiraf
Fatal startup error.  CL dies.


error as wu_qso. I have tried a few things and they still give me the same error.

1) re-defining $iraf and $IRAFARCH for my user and also starting ecl or cl from cshell or bash, I still seem to get the same error.
2) alternatively, if I am running as root, make a /root/iraf directory, run mkiraf inside it, and then launch cl, the same error.
3) this same error also happens if I do a personal level install under my normal user as you suggested.

I checked the uparm directory and I have the following permissions:

PHP Formatted Code

-rw-r--r-- 1 ian users 5942 Oct 24 21:16 login.cl
drwxr-xr-x 2 ian users 4096 Oct 24 21:16 uparm
 


Do you have any further suggestions on what to try? Thank you for your help.

Also, I noticed that the checksums here ftp://iraf.noao.edu/iraf/v216/PCIX/CHECKSUMS do not seem to match the check sums I get when I download the file (both using `sum -r` and `sum - b`).

Thanks,

Ian


 
Profile Email
 Quote
fitz
 10/25/2013 01:50AM  
AAAAA
Admin

Status: offline


Registered: 09/30/2005
Posts: 4040
The code checking the update was using a "\$this->_split2($m[0])" comparison of the interval instead of "\$this->_split2($m[0])=" leading to madness. The quick fix is to comment out the call to 'chkupdate' in your login.cl file, I'll push out a new distro that fixes this. BTW, that might also be why the CHECKSUMS are different, i.e. that a new update was put in the archive compared to what you downloaded.

 
Profile Email
 Quote
iancze
 11/04/2013 03:58PM  
+----
Newbie

Status: offline


Registered: 10/24/2013
Posts: 2
Thank you for pushing out the new update! I was able to install this cleanly on linux64 using bash and without needing to set $iraf or $IRAFARCH.

 
Profile Email
 Quote
mo0713
 11/07/2013 02:12PM  
+----
Newbie

Status: offline


Registered: 05/13/2011
Posts: 6
Hi

Apparently, I have the same problem: after updating to the latest 2.16.1, I got error messages "ERROR: Cannot open file (uparm$update)" when I start IRAF, while I have never got such errors in previously 2.16.

I've also tried fresh install of the latest by using "iraf.macx.x86.tar.gz" and got the same result. (I'm using 32 bit IRAF on Mac OS X 10.8 and 10.9)

The version which was working without error is

NOAO/IRAF PC-IRAF Revision 2.16.1 EXPORT Mon Oct 14 21:40:13 MST 2013


After I ran "cd $iraf && make update", the version is still unchanged, but just got error.

PHP Formatted Code
$ cl
setting terminal type to 'xterm' ...

   NOAO/IRAF PC-IRAF Revision 2.16.1 EXPORT Mon Oct 14 21:40:13 MST 2013
      This is the EXPORT version of IRAF V2.16 supporting PC systems.


  Welcome to IRAF.  To list the available commands, type ? or ??.  To get
  detailed information about a command, type `help <command>'.  To run  a
  command  or  load  a  package,  type  its name.   Type  `bye'
to exit a
  package, or `logout' to get out  of the CL.    Type `news' to find  out
  what is new in the version of the system you are using.  

  Visit https://iraf.net if you have questions or to report problems.


ERROR: Cannot open file (uparm$update)
    cl ()
    cl ()
    cl ()
    votools ()
    cl ()
    astcat ()
    cl ()
    onedspec ()
    cl ()
    cl ()
    cl ()
    cl ()
    photcal ()
    cl ()
    cl ()
    cl ()
    apphot ()
    cl ()
    digiphot ()
    cl ()
    astutil ()
    cl ()
    cl ()
    nproto ()
    vo ()
    cl ()
    cl ()
    cl ()
    tv ()
    cl ()
    cl ()
    cl ()
    dataio ()
    cl ()
    plot ()
    cl ()
    cl ()
    cl ()

PANIC in `/usr/local/iraf/iraf/bin.macosx/cl.e': segmentation violation

 
Profile Email
 Quote
fitz
 11/07/2013 06:11PM  
AAAAA
Admin

Status: offline


Registered: 09/30/2005
Posts: 4040
A "make update" will recompile the system to update any source code changes, what you want to do instead is

PHP Formatted Code

    % cd /path/iraf
    % make latest
 


This will download a source patch (what you need to correct the bug in the task so a 'make update' would have worked) as well as the latest binaries that will fix the problem (i.e. afterward a 'make update' is no longer required).

It wasn't clear whether the iraf.macx.x86.tar.gz file you unpacked was downloaded recently (in the last few days) and so contains the fix, or if it was somewhat older. A 'make latest' should always be safe to do, the new login procedures are meant to alert you to when a new release is available so you don't have to continually check.

That said, I checked that the latest 32-bit OSX distro contains the source patch, however the binary does indeed fail. It appears the library contains two versions of the .o file, one fixed and one not, and apparently linked against the old one. I've fixed this and have updated the distro file with the fix so a "make latest" should actually fix it.

 
Profile Email
 Quote
mo0713
 11/07/2013 06:29PM  
+----
Newbie

Status: offline


Registered: 05/13/2011
Posts: 6
Thanks for the fix. The previous binary package which made an error was downloaded today (several hour ago), and the latest one applied by 'make latest' worked! (in the previous post, I made a typo 'make update' --\$this->_split2($m[0]) 'make latest', sorry)

Another small thing: The line 19 of Makefile in extern directory gives an error when I typed 'make check'. Apparently, it's indented with space instead of tab.

 
Profile Email
 Quote
fitz
 11/07/2013 06:38PM  
AAAAA
Admin

Status: offline


Registered: 09/30/2005
Posts: 4040
Another small thing: The line 19 of Makefile in extern directory gives an error when I typed 'make check'. Apparently, it's indented with space instead of tab.[/p]


Thanks, being fixed now (dangers of cut-n-paste Smile

 
Profile Email
 Quote
   
Content generated in: 0.59 seconds
New Topic Post Reply

Normal Topic Normal Topic
Sticky Topic Sticky Topic
Locked Topic Locked Topic
New Post New Post
Sticky Topic W/ New Post Sticky Topic W/ New Post
Locked Topic W/ New Post Locked Topic W/ New Post
View Anonymous Posts 
Anonymous users can post 
Filtered HTML Allowed 
Censored Content 
dog allergies remedies cialis 20 mg chilblain remedies


Privacy Policy
Terms of Use

User Functions

Login