[daip] AIPS install failure Linux 64 bit
Eric Greisen
egreisen at nrao.edu
Thu May 12 15:40:13 EDT 2011
Bill Boyd wrote:
> Dear AIPS Designate,
>
> I just tried to build the 31DEC10 version of AIPS on a 64-bit Linux machine (openSUSE 11.3) and I am getting the oddest failure. When the install script tries to build XAS, the compile command for xas.c is 'c xas.c' instead of '/usr/bin/gcc xas.c', and none of the options are showing up. I tried running 'make -d xas' in the XAS directory but don't get any further clues. I'm guessing that the environment is messed up such that the Makefile does not set the $CC and other variables correctly. This may be the first time we've tried to build AIPS on a purely 64 bit system with no 32 bit libraries, so that may be a factor.
>
> Here is the exact output of the install script:
>
> AipsWiz: About to try to make XAS...
>
> rm -f *.o xas XAS
> c xas.c
> make: c: Command not found
> make: [xas.o] Error 127 (ignored)
>
>
> Does this error look like something you've seen before? If so, your experienced knowledge will certainly save me time and make a bunch of astronomers happy.
Let me ask a more pertinent question first. Why are you compiling AIPS
yourselves? If you plan to develop your own AIPS tasks, then I guess
you are stuck doing that. But if you do not plan on doing so, I would
suggest usinng the binary installation instead. It runs fasterthan the
binaries produced by the gnu compiler.
perl install.pl -n
will do the network or binary install.
Check the file $HOME/.AIPSRC for the option CCOM. That might not have
been set properly leading to a C compiler called "c". If that is okay,
maybe something went wrong in the auto-editing of the make file. Look
at $YSERV/XAS/Makefile for the CCOM_$ARCH appropriate to your $ARCH
(should be LNX64). Simply edit this file. But you had better also
chack $SYSLOCAL/CCOPTS.SH (and that $SYSLOCAL is properly defined).
Often what happens is a problem between the SITE name from previous
installations and the current one causing your computer doing the
compile to know the correct new answers in some places and use the
previously correct answers elsewhere. $SYSLOCAL should be
$SYSLNX64/$SITE which may or may not be happening. I think it is that
confusion that has been behind the compiler names not being set as
expected (so CCOPTS.SH is read from $SYSLNX64 not from the edited
version in the correct $SYSLOCAL).
Eric Greisen
More information about the Daip
mailing list