Carlos Grohmann <carlos.grohm...@gmail.com> writes: > 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.
Absolutely. > > I don't understand why GRASS is offending SIP. Perhaps we should seek > out for help from others. Maybe Apple itself. There were some explanations from Michael why this happens on this list and also possible solutions - I'll see if I can find them... Here: ,---- | Subject: Re: [GRASS-dev] GRASS on OS X El Capitan - slowly dying or is something happening? | To: GRASS developers list <grass-...@lists.osgeo.org> | Cc: Rainer M Krug <rai...@krugs.de>, William Kyngesburye <kyngch...@kyngchaos.com>, Anna Petrášová <kratocha...@gmail.com>, Brian Miles <selimna...@gmail.com> | Date: Thu, 21 Jan 2016 19:19:10 +0000 | | AFAICT, the binaries I am compiling under Mavericks work with El Capitan IF you turn off System Integrity Protection (to get to the same level of security available in | Mavericks). | | I have not yet updated to El Capitan because I'm hoping someone can tell me if they can compile GRASS with it. I don't want to get to situation where I can't produce binaries | for the community. But I would like to upgrade pretty soon. | | There are several things in process right now. William, Brian Miles, and I have talked about how to deal with the SIP problem. William has an idea of why it is a problem. | Fixing it will require significant change for how dependencies are packaged and referenced. This related to the second thing. | | We've had to compile GRASS with dual 32 bit/64 bit architecture for several years because v. 2.8.x of wxPython is 32 bit and subsequent versions of wxPython did not work well | or did not work with GRASS. We've started trying again to get GRASS working with 64 bit wxPython 3 and are having some success. (If anyone wants to test a version, please let | me know and I'll provide a link to a binary). Because we have to package wxPython with GRASS, and the 32/64 bit dual architecture compilation is causing increasing problems, | we need to solve that. | | If we can get these things worked out, I hope someone can try to compile GRASS with El Capitan and stock Mac Python, etc. to make sure it all works. `---- Also the Thread "GRASS on OS X El Capitan - slowly dying or is something happening?" > > 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? Using /usr/local is also tricky as it needs to be created without SIP - but afterwards, SIP can be enabled again. (see http://digitizor.com/install-homebrew-osx-el-capitan/ ) I actually think that if homebrew is easiewr to make to work, than this should be the first step. Cheers, Rainer > > best > > Carlos > > On Tue, Mar 15, 2016 at 9:51 AM, Adam Dershowitz > <adershow...@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 -- Rainer M. Krug email: Rainer<at>krugs<dot>de PGP: 0x0F52F982
signature.asc
Description: PGP signature
_______________________________________________ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
