[daip] AIPS compilation problem

Eric Greisen egreisen at nrao.edu
Fri Apr 8 15:27:02 EDT 2011


Philip Lah wrote:
> Hello Eric,
> 
>   when I try and run the AIPS binary installation I eventually reach 
> this point:
> 
> 
> 
> Data disk assignments:
> DADEVS.PL: This program is untested under Perl version 5.012
>   (Using global default file /home/AIPS/AIPS/DA00/DADEVS.LIST for 
> DADEVS.PL)
> DADEVS.PL error - no disks selected at all
> This is a FATAL error and nothing in AIPS will work.
> 
> *********************************************************
> HELP!  No Defined data areas!  You can proceed now to run
> program FILAIP, but you may see LOTS of complaints about
> not being able to access the message file.  If you think
> there should have been some data areas defined, please
> check DADEVS.LIST or .dadevs files, or AIPSASSN.\*
> *********************************************************
> If you want to proceed, enter YES (uppercase) now:
> YES
> Starting up FILAIP (RELEASE OF 31DEC11)
>  ----------------------------------------------------------------------
>     Copyright (C) 1995-2011
>    Associated Universities, Inc. Washington DC, USA.
> 
>    This program is free software; you can redistribute it and/or
>    modify it under the terms of the GNU General Public License as
>    published by the Free Software Foundation; either version 2 of
>    the License, or (at your option) any later version.
> 
>    This program is distributed in the hope that it will be useful,
>    but WITHOUT ANY WARRANTY; without even the implied warranty of
>    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
>    GNU General Public License for more details.
> 
>    You should have received a copy of the GNU General Public
>    License along with this program; if not, write to the Free
>    Software Foundation, Inc., 675 Massachusetts Ave, Cambridge,
>    MA 02139, USA.
> 
>    Correspondence concerning AIPS should be addressed as follows:
>           Internet email: aipsmail at nrao.edu.
>           Postal address: AIPS Project Office
>                           National Radio Astronomy Observatory
>                           520 Edgemont Road
>                           Charlottesville, VA 22903-2475 USA
>  ----------------------------------------------------------------------
> Password:
> # interactive AIPS, # batch queues (2 I)
> 2
> ****  MORE VALUES PLEASE :
> 8
>  ZMSGOP: VOLUME  1 FOR FILE DA01:MSD001000.001;      NOT FOUND
> MSGWRT ERROR      3 AT OPEN
> FILAI1: ZCREAT: FILE DA00:BQD000000; ALREADY EXISTS
>  ZMSGOP: VOLUME  1 FOR FILE DA01:MSD001000.001;      NOT FOUND
> MSGWRT ERROR      3 AT OPEN
> FILAI1: ZFIO: OPER = WRIT LUN = 15 NREC =        3
>  ZMSGOP: VOLUME  1 FOR FILE DA01:MSD001000.001;      NOT FOUND
> MSGWRT ERROR      3 AT OPEN
> FILAI1: ZFI2: REQUEST FOR BYTES 2049 THRU = 3072 BEYOND EOF = 2048
>  ZMSGOP: VOLUME  1 FOR FILE DA01:MSD001000.001;      NOT FOUND
> MSGWRT ERROR      3 AT OPEN
> FILAI1: ZERROR: IN ZFI2   ERRNO = 22 (Invalid argument)
>  ZMSGOP: VOLUME  1 FOR FILE DA01:MSD001000.001;      NOT FOUND
> MSGWRT ERROR      3 AT OPEN
> FILAI1: FILE TYPE BQ WRITE ERROR      3      3
>  ZMSGOP: VOLUME  1 FOR FILE DA01:MSD001000.001;      NOT FOUND
> MSGWRT ERROR      3 AT OPEN
> FILAI1: ZCREAT: FILE DA00:BAD001001; ALREADY EXISTS
>  ZMSGOP: VOLUME  1 FOR FILE DA01:MSD001000.001;      NOT FOUND
> MSGWRT ERROR      3 AT OPEN
> FILAI1: ZCREAT: FILE DA00:BAD002001; ALREADY EXISTS
>  ZMSGOP: VOLUME  1 FOR FILE DA01:MSD001000.001;      NOT FOUND
> MSGWRT ERROR      3 AT OPEN
> FILAI1: ZCREAT: FILE DA00:BAD001002; ALREADY EXISTS
>  ZMSGOP: VOLUME  1 FOR FILE DA01:MSD001000.001;      NOT FOUND
> MSGWRT ERROR      3 AT OPEN
> FILAI1: ZCREAT: FILE DA00:BAD002002; ALREADY EXISTS
>  ZMSGOP: VOLUME  1 FOR FILE DA01:MSD001000.001;      NOT FOUND
> MSGWRT ERROR      3 AT OPEN
> FILAI1: ZCREAT: FILE DA00:BAD001003; ALREADY EXISTS
>  ZMSGOP: VOLUME  1 FOR FILE DA01:MSD001000.001;      NOT FOUND
> MSGWRT ERROR      3 AT OPEN
> FILAI1: ZCREAT: FILE DA00:BAD002003; ALREADY EXISTS
>  ZMSGOP: VOLUME  1 FOR FILE DA01:MSD001000.001;      NOT FOUND
> MSGWRT ERROR      3 AT OPEN
> FILAI1: ZCREAT: FILE DA00:TDD000004; ALREADY EXISTS
>  ZMSGOP: VOLUME  1 FOR FILE DA01:MSD001000.001;      NOT FOUND
> MSGWRT ERROR      3 AT OPEN
> FILAI1: ZCREAT: FILE DA00:ICD000000; ALREADY EXISTS
>  ZMSGOP: VOLUME  1 FOR FILE DA01:MSD001000.001;      NOT FOUND
> MSGWRT ERROR      3 AT OPEN
> FILAI1: ZCREA2: TROUBLE TRANSLATING LOGICAL = DA01
>  ZMSGOP: VOLUME  1 FOR FILE DA01:MSD001000.001;      NOT FOUND
> MSGWRT ERROR      3 AT OPEN
> FILAI1: ZCREAT: DISK  1 NOT FOUND FOR DA01:MSD001000.001;
>  ZMSGOP: VOLUME  1 FOR FILE DA01:MSD001000.001;      NOT FOUND
> MSGWRT ERROR      3 AT OPEN
> FILAI1: FILE TYPE MS CREATE ERROR      2
>  ZMSGOP: VOLUME  1 FOR FILE DA01:MSD001000.001;      NOT FOUND
> MSGWRT ERROR      3 AT OPEN
> FILAI1: ZCREAT: FILE TSTMEM:MED000000; ALREADY EXISTS
>  ZMSGOP: VOLUME  1 FOR FILE DA01:MSD001000.001;      NOT FOUND
> MSGWRT ERROR      3 AT OPEN
> FILAI1: ZCREAT: FILE DA00:MED000001; ALREADY EXISTS
>  ZMSGOP: VOLUME  1 FOR FILE DA01:MSD001000.001;      NOT FOUND
> MSGWRT ERROR      3 AT OPEN
> FILAI1: ZCREAT: FILE DA00:MED000002; ALREADY EXISTS
>  ZMSGOP: VOLUME  1 FOR FILE DA01:MSD001000.001;      NOT FOUND
> MSGWRT ERROR      3 AT OPEN
> FILAI1: ZCREAT: FILE DA00:MED000003; ALREADY EXISTS
>  ZMSGOP: VOLUME  1 FOR FILE DA01:MSD001000.001;      NOT FOUND
> MSGWRT ERROR      3 AT OPEN
> FILAI1: ZCREAT: FILE DA00:MED000004; ALREADY EXISTS
>  ZMSGOP: VOLUME  1 FOR FILE DA01:MSD001000.001;      NOT FOUND
> MSGWRT ERROR      3 AT OPEN
> FILAI1: ZCREAT: FILE DA00:MED000005; ALREADY EXISTS
>  ZMSGOP: VOLUME  1 FOR FILE DA01:MSD001000.001;      NOT FOUND
> MSGWRT ERROR      3 AT OPEN
> FILAI1: ZCREAT: FILE DA00:MED000006; ALREADY EXISTS
>  ZMSGOP: VOLUME  1 FOR FILE DA01:MSD001000.001;      NOT FOUND
> MSGWRT ERROR      3 AT OPEN
> FILAI1: ZCREAT: FILE DA00:MED000007; ALREADY EXISTS
>  ZMSGOP: VOLUME  1 FOR FILE DA01:MSD001000.001;      NOT FOUND
> MSGWRT ERROR      3 AT OPEN
> FILAI1: ZCREAT: FILE DA00:MED000008; ALREADY EXISTS
>  ZMSGOP: VOLUME  1 FOR FILE DA01:MSD001000.001;      NOT FOUND
> MSGWRT ERROR      3 AT OPEN
> FILAI1: ZCREAT: FILE DA00:MED000009; ALREADY EXISTS
>  ZMSGOP: VOLUME  1 FOR FILE DA01:MSD001000.001;      NOT FOUND
> MSGWRT ERROR      3 AT OPEN
> FILAI1: ZCREAT: FILE DA00:MED00000A; ALREADY EXISTS
>  ZMSGOP: VOLUME  1 FOR FILE DA01:MSD001000.001;      NOT FOUND
> MSGWRT ERROR      3 AT OPEN
> FILAI1: ZCREAT: FILE DA00:MED00000B; ALREADY EXISTS
>  ZMSGOP: VOLUME  1 FOR FILE DA01:MSD001000.001;      NOT FOUND
> MSGWRT ERROR      3 AT OPEN
> FILAI1: Init POPS memory files 1 through 12 with program POPSGN
>  ZMSGOP: VOLUME  1 FOR FILE DA01:MSD001000.001;      NOT FOUND
> MSGWRT ERROR      3 AT OPEN
> FILAI1: ZCREAT: FILE DA00:SPD000000; ALREADY EXISTS
>  ZMSGOP: VOLUME  1 FOR FILE DA01:MSD001000.001;      NOT FOUND
> MSGWRT ERROR      3 AT OPEN
> FILAI1: ZCREAT: FILE DA00:ACD000000; ALREADY EXISTS
>  ZMSGOP: VOLUME  1 FOR FILE DA01:MSD001000.001;      NOT FOUND
> MSGWRT ERROR      3 AT OPEN
> FILAI1: AC FILE NOT INITIALIZED. USE FILINI IF YOU REALLY MEAN IT
>  ZMSGOP: VOLUME  1 FOR FILE DA01:MSD001000.001;      NOT FOUND
> MSGWRT ERROR      3 AT OPEN
> FILAI1: ZCREAT: FILE DA00:TPD001001; ALREADY EXISTS
>  ZMSGOP: VOLUME  1 FOR FILE DA01:MSD001000.001;      NOT FOUND
> MSGWRT ERROR      3 AT OPEN
> FILAI1: ZCREAT: FILE DA00:TPD001002; ALREADY EXISTS
>  ZMSGOP: VOLUME  1 FOR FILE DA01:MSD001000.001;      NOT FOUND
> MSGWRT ERROR      3 AT OPEN
> FILAI1: ZCREAT: FILE DA00:TPD001003; ALREADY EXISTS
>  ZMSGOP: VOLUME  1 FOR FILE DA01:MSD001000.001;      NOT FOUND
> MSGWRT ERROR      3 AT OPEN
> FILAI1: ZCREAT: FILE DA00:TPD001004; ALREADY EXISTS
>  ZMSGOP: VOLUME  1 FOR FILE DA01:MSD001000.001;      NOT FOUND
> MSGWRT ERROR      3 AT OPEN
> FILAI1: ZCREAT: FILE DA00:TPD001005; ALREADY EXISTS
>  ZMSGOP: VOLUME  1 FOR FILE DA01:MSD001000.001;      NOT FOUND
> MSGWRT ERROR      3 AT OPEN
> FILAI1: ZCREAT: FILE DA00:TPD001006; ALREADY EXISTS
>  ZMSGOP: VOLUME  1 FOR FILE DA01:MSD001000.001;      NOT FOUND
> MSGWRT ERROR      3 AT OPEN
> FILAI1: ZCREAT: FILE DA00:TPD001007; ALREADY EXISTS
>  ZMSGOP: VOLUME  1 FOR FILE DA01:MSD001000.001;      NOT FOUND
> MSGWRT ERROR      3 AT OPEN
> FILAI1: ZCREAT: FILE DA00:TPD001008; ALREADY EXISTS
>  ZMSGOP: VOLUME  1 FOR FILE DA01:MSD001000.001;      NOT FOUND
> MSGWRT ERROR      3 AT OPEN
> FILAI1: ZCREAT: FILE DA00:TPD001009; ALREADY EXISTS
>  ZMSGOP: VOLUME  1 FOR FILE DA01:MSD001000.001;      NOT FOUND
> MSGWRT ERROR      3 AT OPEN
> FILAI1: ZCREAT: FILE DA00:TPD00100A; ALREADY EXISTS
>  ZMSGOP: VOLUME  1 FOR FILE DA01:MSD001000.001;      NOT FOUND
> MSGWRT ERROR      3 AT OPEN
> FILAI1: ZCREAT: FILE DA00:GRD000000; ALREADY EXISTS
>  ZMSGOP: VOLUME  1 FOR FILE DA01:MSD001000.001;      NOT FOUND
> MSGWRT ERROR      3 AT OPEN
> FILAI1: GR FILE NOT INITIALIZED. USE FILINI IF YOU REALLY MEAN IT
>  ZMSGOP: VOLUME  1 FOR FILE DA01:MSD001000.001;      NOT FOUND
> MSGWRT ERROR      3 AT OPEN
> FILAI1: ZCREAT: FILE DA00:PWD000000; ALREADY EXISTS
>  ZMSGOP: VOLUME  1 FOR FILE DA01:MSD001000.001;      NOT FOUND
> MSGWRT ERROR      3 AT OPEN
> FILAI1: PW FILE NOT INITIALIZED. USE FILINI IF YOU REALLY MEAN IT
>  ZMSGOP: VOLUME  1 FOR FILE DA01:MSD001000.001;      NOT FOUND
> MSGWRT ERROR      3 AT OPEN
> FILAI1: ZCREAT: FILE DA00:TCD000001; ALREADY EXISTS
>  ZMSGOP: VOLUME  1 FOR FILE DA01:MSD001000.001;      NOT FOUND
> MSGWRT ERROR      3 AT OPEN
> FILAI1: Done!
> 
> 
> 
> 
> I have checked DADEVS.LIST and my data area is defined as it is in 
> NETSP. I cannot find the .dadevs file and the only unusual thing that I 
> can potentially see in the AIPSASSN.\* is that
> 
> setenv DATA_ROOT /DEFINE_ME
> 
> As such I have no idea why the data area is not being defined.  I am not 
> even sure whether this is the actual problem. I did run LOGIN.CSH and 
> RUN FILAIP as suggetted but this did not help.
> 
> After struggling with this for a while I gave up and tried the text 
> installation istead.
> 
>   Bye
>        Philip Lah
> 
> On Fri, 8 Apr 2011, Eric Greisen wrote:
> 
>> Philip Lah wrote:
>>> Hello daip at nrao.edu,
>>>
>>>    I have been trying to install AIPS on a Fedora 14 Linux 64bit 
>>> machine without sucess.  Frank Briggs (my supervisor) suggested I 
>>> contact you.
>>>
>>>    I first tried a binary installation and got nowhere so I have been 
>>> working on getting a Text installation working.
>>>
>>> I have reached the stage of INSTEP2 but this fails with:
>>>
>>> AipsWiz: Error: INSTEP2 failed, no point in proceeding.
>>>
>>>
>>> Looking in the INSTEP2.LOG there are the below failed compliation 
>>> message:
>>>
>>> COMRPL    : Compile failed!
>>> COMRPL    : Deleted    /home/AIPS/AIPS/31DEC11/LNX64/PREP/UVDESC.f
>>>
>>> COMRPL    : Compile failed!
>>> COMRPL    : Deleted    /home/AIPS/AIPS/31DEC11/LNX64/PREP/POSITION.f
>>>
>>>
>>> The only other problems I could find in the INSTEP2.LOG were a series 
>>> of messages like this:
>>>
>>>
>>> /home/AIPS/AIPS/31DEC11/LNX64/PREP/POSITION.f:679: (continued):
>>>                 CALL IMDGET (OUT, 'CRVAL', TYPE, DIM, CRVAL, CDUMMY, 
>>> IERR)
>>>                      2
>>> Argument #5 of `imdget' is one precision at (2) but is some other 
>>> precision at (1) [info -f g77 M GLOBALS]
>>>
>>>
>>> I am not sure whether or not these would be a fatal errors.
>>>
>>>
>>> I am at a loss on how to fix these compilation problems.  I have a 
>>> suspicion that it may be due to the compiler options I used.  I do 
>>> not have access to ifort or icc so I am using g77 and gcc.  In order 
>>> to get these to work I had to remove several of the Compiler options.
>>>
>>> Currently I am using g77 with
>>>
>>> -c -ff90 -ip
>>>
>>> (previously with ifort -c -axWPT -w90 -w95 -cm -ip -save all)
>>>
>>> and gcc with
>>>
>>> -c -O3 -ip -I/home/AIPS/AIPS/31DEC11/INC -D_FILE_OFFSET_BITS=64 
>>> -DHAVE_LINUX_GLIBC
>>>
>>> (previously with icc -c -O3 -ip -axWPT -I/home/AIPS/AIPS/31DEC11/INC 
>>> -D_FILE_OFFSET_BITS=64 -DHAVE_LINUX_GLIBC   that is no -axWPT used 
>>> with gcc)
>>>
>>> It is possible that I need to add some options for g77 and gcc to 
>>> replace the ones I removed in order for ISTEP2 to compile.  It is 
>>> also possible that it is something completely different going wrong.
>>>
>>>    Any help that you could provide would be most welcome.
>>>
>>>    Bye
>>>          Philip Lah
>>
>> I would like to know what your problems with the binary installation 
>> were. Over 90% of our sites now appear to be using the binary 
>> installation and so avoid the issues of incompatible compilers etc.
>> In FDEFAULT.SH there are options indicated for gfortran and for f77 
>> but it is known that some versions of these compilers do not work 
>> correctly.
>> Furthermore, your -ff90 seems to assert that the code is Fortran 90 
>> compliant which it probably is not.  It is F77 code.  The warning 
>> message points out an "issue" which we handle carefully in the code in 
>> which the formal data types deliberately do not match across call 
>> sequences.  If we were to use a compiler that required a match it 
>> would literally take months to change things - I know because the code 
>> line above used to omit that character form and try to handle even 
>> that across the boundary (which is not legal in most Fortrans) so I 
>> had to go fix it.  If real vs integer vs array vs ??? had to be fixed 
>> the problem would be vastly more difficult.  Let us try to solve your 
>> binary install issues - you will get executables that run faster and 
>> are expected to work.
>>
>> Eric Greisen
>>
> 
> **************************************************
>     Philip Lah
>   Postdoctoral Fellow, joint appointment at
>   National Centre for Radio Astrophysics
>     and
>   Australian National University
> 
>   Home Page: http://www.mso.anu.edu.au/~plah/
> 
> **************************************************

You will get this same issue eventually should your compilations 
actually work.

The most common problem with DADEVS.LIST files is that the data 
directory names do not include (in upper case letters) the name of the 
computer.  This is fine if they are required foir all computers using 
that site (i.e. a + in column 1) but not if they are used only for a 
specific computer.  Thus my computer (primate) has data areas

-  /DATA/PRIMATE_1
-  /DATA/PRIMATE_2

in our site's enormous DADEVS.LIST file.  You can either rename your 
intended data areas or change the - sign in column 1 to a + sign.  That 
will be fine if only one actual computer is to use the installation. 
Unfortunately, we have to build for sites where 100 computers use one 
installation.

If this is not the problem, send me your DADEVS.LIST file.

Eric Greisen




More information about the Daip mailing list