Up to top level
AO15   AO16   AO17   AO18   Backgrounds   Calibration   Conference   Data   Docs   EPICMOS   EPICpn   Feedback   Gallery   Misc   OM   Pending   PhD_Theses   Publications   RGS   RadMonitor   SAS_Hardware   SAS_WS   SASv16.0   SASv16.0_Installation   SASv16.1   SASv16.1_Installation   SASv17.0   SASv17.0_Installation   SciSim   Simulators_other   Suggestions   Trash   Visibility   XMM-bouncing   XMM-news   XRPS   XSA   esas   incoming  

Logged in as guest

Viewing SASv16.1/82575
Full headers

From: nathansecrest@msn.com
Subject: dyld: Library not loaded...
Compose reply
Move To:
1 replies: 1
0 followups:

Private message: yes  no

Notes:

Notification:


Date: Fri, 10 Nov 2017 17:40:08 GMT
From: nathansecrest@msn.com
To: xmmhelp@sciops.esa.int
CC: nathansecrest@msn.com
Subject: dyld: Library not loaded...
Full_Name: Nathan Secrest
Submission from: (NULL) (73.133.129.57)


This is not a question so much as a clarification that may help some SAS users.

I was running into the "dyld: Library not loaded..." issue with my Python
script. However, the source of the problem was not that my System Integrity
Protection (SIP) is enabled, as stated in the SAS Watchout pages. The issue
turned out to be that the Python subprocess.call function is not compatible with
the SAS commands if the shell=True option is enabled. For example,

call('cifbuild', shell=True)

gives the dyld error, while

call(['cifbuild'])

does not. My system specs are:

OSX Sierra 10.12.6
SAS release: xmmsas_20170719_1539-16.1.0
Python 3.6.3

For users who are scripting their SAS analysis with Python, I recommend first
checking that problematic SAS routines still do not work if manually entered
into a terminal before disabling SIP.

Cheers,

Nathan Secrest



Reply 1

Resend
From: Nora Loiseau <xmmhelp@sciops.esa.int>
To: nathansecrest@msn.com
Subject: Re: dyld: Library not loaded... (PR#82575)
Date: Mon Nov 13 17:38:47 2017
Dear Nathan,

Thanks for your comment!, I consulted a SAS expert about it and here is his
reply:
--
In principle, to use SAS in Sierra it is not necessary to disable SIP. We use it
with SIP enabled and there seems to be no problem. 
I have used a very simple python script to try to reproduce the problem and I am
not able to get the error reported by the user. 

Here is my python test script:

#! /usr/bin/env python

from subprocess import call

call('cifbuild --version', shell=True)

Running this script does not give any error but instead produces the expected
result:

cifbuild (cifbuild-4.8) [xmmsas_20170719_1539-16.1.0]
=========

Many thanks again,

Nora


> This is not a question so much as a clarification that may help some SAS
users.
> 
> I was running into the "dyld: Library not loaded..." issue with my Python
> script. However, the source of the problem was not that my System
Integrity
> Protection (SIP) is enabled, as stated in the SAS Watchout pages. The
issue
> turned out to be that the Python subprocess.call function is not compatible
with
> the SAS commands if the shell=True option is enabled. For example,
> 
> call('cifbuild', shell=True)
> 
> gives the dyld error, while
> 
> call(['cifbuild'])
> 
> does not. My system specs are:
> 
> OSX Sierra 10.12.6
> SAS release: xmmsas_20170719_1539-16.1.0
> Python 3.6.3
> 
> For users who are scripting their SAS analysis with Python, I recommend
first
> checking that problematic SAS routines still do not work if manually
entered
> into a terminal before disabling SIP.
> 
> Cheers,
> 
> Nathan Secrest
> 
> 
> ----
Dr. Nora Loiseau
XMM-Newton User Support Group

Up to top level
AO15   AO16   AO17   AO18   Backgrounds   Calibration   Conference   Data   Docs   EPICMOS   EPICpn   Feedback   Gallery   Misc   OM   Pending   PhD_Theses   Publications   RGS   RadMonitor   SAS_Hardware   SAS_WS   SASv16.0   SASv16.0_Installation   SASv16.1   SASv16.1_Installation   SASv17.0   SASv17.0_Installation   SciSim   Simulators_other   Suggestions   Trash   Visibility   XMM-bouncing   XMM-news   XRPS   XSA   esas   incoming  

Logged in as guest


Please make your (short) question the subject of your request!


Web interface using JitterBug ... back to the XMM home page