[daip] FW: MacOS Question

[Eric Greisen]

DePree, Chris writes:

 > I am installing AIPS on my new MacBook Pro, and I am running into a problem. I installed the Intel c ad fortran compilers, and made sure that the defaults files were correct. However, when it tries to build XAS, it chokes (see below), I think because it is using an incorrect link to a version that I don't have. I don't kow where it is grabbing this, because according o the install script, t is pointing to all the rigt locations! Any ideas MUCH appreciated.
 > 

      Of course you could also do the binary installation...

 > --
 > catalog.c(348): (col. 10) remark: LOOP WAS VECTORIZED.
 > catalog.c(353): (col. 10) remark: LOOP WAS VECTORIZED.
 > catalog.c(166): (col. 7) remark: LOOP WAS VECTORIZED.
 > catalog.c(191): (col. 10) remark: LOOP WAS VECTORIZED.
 > catalog.c(109): (col. 10) remark: LOOP WAS VECTORIZED.
 > /opt/intel/cc/10.0.016/bin/icc -L/usr/X11R6/lib -L/opt/intel/cc/9.1.018/lib -O2 -axP -D_BSD -DUSE_SHM xas.o image.o comm.o cursor.o screen.o init.o colors.o catalog.o -lXext -lX11 -lm  -o xas
 > ipo: warning #11021: file format not recognized for /usr/X11R6/lib/libXext.dylib
 > ipo: warning #11021: file format not recognized for /usr/X11R6/lib/libX11.dylib
 > ld: warning -L: directory name (/opt/intel/cc/9.1.018/lib) does not exist
 > ld: warning /usr/X11R6/lib/libXext.dylib cputype (18, architecture ppc) does not match cputype (7) for specified -arch flag: i386 (file not loaded)
 > ld: warning /usr/X11R6/lib/libX11.dylib cputype (18, architecture ppc) does not match cputype (7) for specified -arch flag: i386 (file not loaded)
 > ld: Undefined symbols:

The Makefile is calling for a link library "-L/usr/X11R6/lib" which
for some reason on your machine is for the old ppc architecture rather
than your new Intel architecture.  When I cd to /usr/X11R6/lib and
enter the command

        file libXext.dylib

it tells me that the file is a universal binary with 2 architectures
(ppc and i386).  With that library it links fine.  I suspect that you
need to reinstall X11 for your new machine.

Eric Greisen