[GRASS-user] GRASS GIS 7.03 for Mac OS X, problem with wxPython (missing)

Adam Dershowitz adershowitz at exponent.com
Tue Mar 15 10:39:43 PDT 2016


I don’t see an option to do that.  The portfile has a few variants, but
nothing related to the gui.

-- Adam






On 3/15/16, 12:32 PM, "Rainer M Krug" <Rainer at krugs.de> wrote:

>Adam Dershowitz <adershowitz at exponent.com> writes:
>
>> I use Macports for a  bunch of other things (and Homebrew is
>>incompatible
>> with Macports)   So, I figured that I would just tried to install grass7
>> using macports.  It does seem to install, but the gui doesn’t work:
>>
>>  $grass70 
>> Cleaning up temporary files...
>> Starting GRASS GIS...
>> ERROR: wxGUI requires wxPython. No module named wxversion
>> Error in GUI startup. If necessary, please report this error to the
>>GRASS
>> developers.
>> Switching to text mode now.
>>
>
>I don't use MacPorts - but can you try to install without GUI?
>
>>
>> Hit RETURN to continue...
>>
>>
>>
>> This is odd, since wxpython is installed.
>> But, it seems like this is a different problem.
>>
>>
>> -- Adam
>>
>>
>>
>>
>>
>>
>> On 3/15/16, 9:50 AM, "Rainer M Krug" <Rainer at krugs.de> wrote:
>>
>>>Michael Barton <Michael.Barton at asu.edu> writes:
>>>
>>>> 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).
>>>
>>>OK - so if I understand you correctly, installing via homebrew, should
>>>not be that difficult, as GRASS is compiled for a specific wxPython -
>>>correct?
>>>
>>>
>>>
>>>>
>>>> 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, http://csdc.asu.edu
>>>>
>>>>     On Mar 15, 2016, at 3:14 PM, Carlos Grohmann
>>>>     <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> 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 )
>>>>         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
>>>>     http://orcid.org/0000-0001-5073-5572
>>>>     
>>>>     ________________
>>>>     Can’t stop the signal.
>>>>
>>>>
>>>
>>>-- 
>>>Rainer M. Krug
>>>email: Rainer<at>krugs<dot>de
>>>PGP: 0x0F52F982
>>
>> _______________________________________________
>> grass-user mailing list
>> grass-user at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/grass-user
>
>-- 
>Rainer M. Krug
>email: Rainer<at>krugs<dot>de
>PGP: 0x0F52F982



More information about the grass-user mailing list