[daip] Fwd: Re: Ask for help to install the AIPS on the newest MacBook Pro

[Eric Greisen]

-------- Forwarded Message --------
Subject: Re: [daip] Ask for help to install the AIPS on the newest 
MacBook Pro
Date: Fri, 12 May 2017 09:00:18 -0600
From: Eric Greisen <egreisen at nrao.edu>
Organization: National Radio Astronomy Observatory
To: cuiyuzhu <cyz3640 at 126.com>

On 05/11/2017 11:25 PM, cuiyuzhu wrote:

> dyld: Library not loaded: @rpath/libsvml.dylib
>   Referenced from: /opt/aips/31DEC17/MACINT/LOAD/ZSTRTA.EXE
>   Reason: image not found
> Abort trap: 6
>

It appears that you did not run the script fix_aips_elcap.sh which may 
be found in $AIPS_ROOT among other places and must be run under bash.
This makes links for the run-time libraries including libsvml.

Since that did not happen you will need to run FILAIP and POPSGN.
cd $AIPS_ROOT
source LOGIN.CSH    (or . LOGIN.SH under bash)
$CDTST
RUN FILAIP
8 2
RUN POPSGN
0 POPSDAT TST
<cr>





> XAS: ** TrueColor FOUND!!!
> XAS: ***  Using shared memory option for speed ***
> XAS: Using screen width 1430 height 778,
>      max grey level 8191 in 16 grey-scale memories
> Shared memory id failure: Invalid argument
> Warning: locale not supported by Xlib, locale set to C
> Warning: locale not supported by Xlib, locale set to C
>

The shared memory issue comes from Mac's small allowed shared memory. 
The AIPS Manager FAQ on this is as follows:


After you follow the instructions below appropriate to your release of 
the Mac operating system, you must re-boot the computer. The control 
file for shared memory is read at boot time only. Note that a re-boot is 
not simply logging the current user out and then back in. You must do a 
full restart.

  On the latest "leopard", "snow leopard", "lion", "mountain lion", and 
"yosemite" (X 10.5-10.10) systems, /etc/rc is gone and creating it will 
have no effect. You need to create an /etc/sysctl.conf file and put the 
values in it,

             kern.sysv.shmmax=10485760
             kern.sysv.shmmin=1
             kern.sysv.shmmni=32
             kern.sysv.shmseg=8
             kern.sysv.shmall=4096


You should use the values you had when you were running tiger. Those 
could be in /Previous\ System/etc/rc, assuming you have "Previous 
System". So three different OS upgrades and three different ways to 
adjust the default shared memory. Note: You will need to reboot the 
system for the change in shared memory to take place. You can check if 
the shared memory changes happened by typing "sysctl kern.sysv" in a 
terminal or xterm window. Look for the kern.sysv.shm* values. If the 
values have not changed, make sure you haven't inadvertently left in 
"sysctl -w" in the /etc/sysctl.conf file or mis-typed one of the values. 
If the /etc/sysctl.conf file is not properly formatted, or shmmax is not 
an integer multiple of shmall, the shared memory will not be adjusted 
after the reboot.


ERic Greisen