[GRASS-user] GRASS GIS 7.03 for Mac OS X, problem with wxPython (missing)
Adam Dershowitz
adershowitz at exponent.com
Tue Mar 15 07:04:00 PDT 2016
I don’t understand why that should matter. It Is great that it is packaged with the whole combination to run in different configurations. But, does GRASS then write to /usr at runtime? Can’t it just run the correct library from in the Application package?
Or is there something about SIP beyond protection against writing to a few key folders?
Just to be clear, I’m not trying to be the last bit accusatory, but I’m just curious about understanding the problem. If all of the correct included versions of libraries are included in the application package, then the issue should just be about pointing to the correct dynamic libraries. Why should SIP care about that at all?
-- Adam
From: Michael Barton <Michael.Barton at asu.edu<mailto:Michael.Barton at asu.edu>>
Date: Tuesday, March 15, 2016 at 9:36 AM
To: Carlos Guâno Grohmann <carlos.grohmann at gmail.com<mailto:carlos.grohmann at gmail.com>>
Cc: Adam Dershowitz <adershowitz at exponent.com<mailto:adershowitz at exponent.com>>, Rainer M Krug <Rainer at krugs.de<mailto:Rainer at krugs.de>>, grass-user grass-user <grass-user at lists.osgeo.org<mailto:grass-user at lists.osgeo.org>>, William Kyngesburye <kyngchaos at kyngchaos.com<mailto:kyngchaos at kyngchaos.com>>, Anna Petrášová <kratochanna at gmail.com<mailto:kratochanna at gmail.com>>
Subject: Re: [GRASS-user] GRASS GIS 7.03 for Mac OS X, problem with wxPython (missing)
The reason is that I (and William) package some key dependencies with the binary. The most important is wxPython, which is required by the GUI. If a user does not have exactly the same version of wxPython used to compile the binary, the GUI will fail. Making this more complicated is the fact that the only versions of wxPython that work completely correctly with Mac GRASS are 32 bit. But some other components are 64 bit. This means that I need to compile GRASS with 32/64 bit dual architecture. So this is a consequence of making binaries that run on anyone's Mac (except the newest system with SIP enabled).
Michael
____________________
C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Head, Graduate Faculty in Complex Adaptive Systems Science
Arizona State University
voice: 480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC)
www: http://www.public.asu.edu/~cmbarton<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.public.asu.edu_-7Ecmbarton&d=CwMGaQ&c=t0wRGL5ICVzH157W8C8Wew&r=5usL3OGqXabRLtSzGmh8YEvbco28TaiOmWcn6rCn8wM&m=N34HRpJ-bC99jAGZ6tcCUmsLYWp4ag3ao63cVcQxtas&s=OOfq3SrregbqJyJJsSRq_KnX6v97McV_ZatMot9KoUo&e=>, http://csdc.asu.edu<https://urldefense.proofpoint.com/v2/url?u=http-3A__csdc.asu.edu&d=CwMGaQ&c=t0wRGL5ICVzH157W8C8Wew&r=5usL3OGqXabRLtSzGmh8YEvbco28TaiOmWcn6rCn8wM&m=N34HRpJ-bC99jAGZ6tcCUmsLYWp4ag3ao63cVcQxtas&s=aW2Qzkj3CbpJ_WG702f-HFbsFcbHaDAMFuOnfIPKnto&e=>
On Mar 15, 2016, at 3:14 PM, Carlos Grohmann <carlos.grohmann at gmail.com<mailto:carlos.grohmann at gmail.com>> wrote:
I run GRASS on OSX El Capitan (with SIP disabled). I don't think that setting up a CLI-only version would be a solution as well. As Rainer said, other software runs natively (see QGIS) and they don't have any problems with OSX/SIP. We should look into that.
I don't understand why GRASS is offending SIP. Perhaps we should seek out for help from others. Maybe Apple itself.
One point is that we need to disable SIP for the binary provided by Michael Barton, but not if you compile it from source (or using homebrew), so this could be fixable by changing paths, like Adam suggested. Homebrew uses /usr/local, why can't we?
best
Carlos
On Tue, Mar 15, 2016 at 9:51 AM, Adam Dershowitz <adershowitz at exponent.com<mailto:adershowitz at exponent.com>> wrote:
Yes, SIP is a new security feature that prevents any applications from
writing to a few key OS paths. I believe that it really is that simple.
(see: https://support.apple.com/en-us/HT204899<https://urldefense.proofpoint.com/v2/url?u=https-3A__support.apple.com_en-2Dus_HT204899&d=CwMGaQ&c=t0wRGL5ICVzH157W8C8Wew&r=5usL3OGqXabRLtSzGmh8YEvbco28TaiOmWcn6rCn8wM&m=N34HRpJ-bC99jAGZ6tcCUmsLYWp4ag3ao63cVcQxtas&s=a-oC6gCKpo7blZOUSNUaANduhi07GUVwoFKvZ6jYnoI&e=> )
Which, does beg the questionŠwhy does running GRASS require writes to any
of these folders? That suggests that GRASS is doing something that it
shouldn¹t be doing. Why should it be writing to system folders at all at
runtime?
It is the only application that I have run into that has any problems with
SIP. It would seem that this should be an easy fix. (for example just
use /usr/local instead of /usr, or whatever the problem folder is).
-- Adam
--
Prof. Carlos Henrique Grohmann
Institute of Energy and Environment - Univ. of São Paulo, Brazil
- Digital Terrain Analysis | GIS | Remote Sensing -
http://carlosgrohmann.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__carlosgrohmann.com_&d=CwMGaQ&c=t0wRGL5ICVzH157W8C8Wew&r=5usL3OGqXabRLtSzGmh8YEvbco28TaiOmWcn6rCn8wM&m=N34HRpJ-bC99jAGZ6tcCUmsLYWp4ag3ao63cVcQxtas&s=Ew41-e1ZzKaTM31cbqiTRNAw8p0Nb7GbyHm68N9MRdM&e=>
http://orcid.org/0000-0001-5073-5572<https://urldefense.proofpoint.com/v2/url?u=http-3A__orcid.org_0000-2D0001-2D5073-2D5572&d=CwMGaQ&c=t0wRGL5ICVzH157W8C8Wew&r=5usL3OGqXabRLtSzGmh8YEvbco28TaiOmWcn6rCn8wM&m=N34HRpJ-bC99jAGZ6tcCUmsLYWp4ag3ao63cVcQxtas&s=mlnJnRzf0pkSB_QcSB1g227Y2mS-F8hTxtOrvzdiae4&e=>
________________
Can’t stop the signal.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-user/attachments/20160315/9efc90c4/attachment-0001.html>
More information about the grass-user
mailing list