Recent Forum Posts
From categories:
page »

I just posted a new GRASS 7.5 dev binary. It has a fix for the menu bar bug switching between 2D and 3D mode.

New GRASS 7.5 dev binary by cmbarton54cmbarton54, 07 Apr 2018 00:09

I just updated these stable versions with a bug fix for a problem in setting display and output fonts.

Releases and updates by cmbarton54cmbarton54, 07 Apr 2018 00:08


Someone else had a similar problem but other people have not. My guess (truly a guess) is that is some kind of issue with downloading from Google drive, the only place I have available to post the binaries right now. If you send me your email, I can try to provide a temporary alternative download location and see if that works. Contact me at moc.liamg|notrab.leahcim.c#moc.liamg|notrab.leahcim.c.


Right. It is not compiled with PostGIS support at the present. This is a compiler option that may or may not be easy to implement. At the moment, I'm still trying to make sure that the new way of compiling works and get GRASS to the level of functionality that it was with the old method. I also am hoping to work with others on the dev team to deal with several nasty bugs that have appeared with the switch to 64bit wxPython. I do hope to be able to compile new versions in the coming weeks with some bug fixes.

When trying to install GRASS 7.x, on opening the unzipped dmg image, I receive the following message:

The following disk images could not be opened
image: grass-7.4.0.dmg
reason: no mountable file systems

Though results for GRASS 7.4 are shown, the problem occurs with all three GRASS 7. disk images on the grassmac site.

The files were downloaded using both Safari (twice) and then Chrome (once) under OS 10.11.6 (El Capitan) w/o success via the Finder.

I then tried running the UNIX clean-up utilities
Then I tried a second reboot

all to no avail.

I was able to mount the disk image using terminal:

$ hdiutil attach -noverify -nomount ./GRASS-7.4.0.dmg
$ diskutil mountDisk /dev/disk2


the newly mounted image was empty. Disk Utility could 'see' the mounted device, and was able to run First Aid, which yielded the following:

'Problems were found with the partition map which might prevent booting'

but couldn't fix the read-only dmg. Everything else, according to Disk First Aid, seemed okay.

I note that these most recent images were not tested under OSXs earlier than Sierra (10.12). Perhaps this [my running El Capitan 10.11] is the problem?

Any suggestions/help [to get GRASS installed] would be greatly appreciated.

Thanks very much, in advance.


didn't try though

hi there,

the 7.4.0 and 7.2.2 .app do not support postgis currently.
It gives:

pg: no such driver available
WARNING: Unable to start driver <pg>
WARNING: Unable open database <v4> by driver <pg>

And v.out.postgis command not available at all.
Seems like it needs to be compiled —with-postgres


Postgresql/postgis support by alex_melnykalex_melnyk, 27 Mar 2018 09:14

I've just posted some fixes and enhancements to the GRASS binaries on this site. It looks like it will not be easy (maybe not possible) to build GRASS with libLAS support for direct LiDAR processing the way I am now compiling binaries. There is hope for the future if the GRASS team adopts PDAL as a replacement for no longer supported libLAS (in the works). In the meantime, I've added LAStools command line tools for LiDAR processing and translation to ASCII formats that GRASS can read. Type lasinfo [return] from the command line to see some of this, with more information at:

Also, I've managed to add a fix to a problem found by Rob Shepard. Attempting to create a new LOCATION from an EPSG code failed. It works now. These should all be available in the fully bundled GRASS binaries on the download page.

You did not explain this issue very clearly. But I think I figured out what you did.

1. You started GRASS and tried to create a new location from EPSG code. You got the error above.

2. Then, instead of trying to create a location a different way, you tried to launch GRASS by opening the and running the ../bin/grass74 file, bypassing the startup scripts.

I might be able to fix #1 and am lookin into it, though I don't understand why this variable is not set by default.

For #2, you can't start GRASS that way. The startup scripts set up the GRASS environment so it can find all the many parts of the program it needs.


Yesterday I downloaded GRASS for the first time. OS X, gras version 7.4.0

I was unable to bootstrap the database as I was unable to create a location. this was the error:

GRASS ERROR 4: Unable to open EPSG support file gcs.csv. Try setting the GDAL_DATA environment variable to point to the directory containing EPSG csv files. ERROR: Unable to translate EPSG code

I finally worked around this problem by running the grass74 binary on the commandline with GDAL_DATA set in the env and using -c EPSG:3857

I then set off a long running operation (r.contours) and went to bed.

GRASS must have crashed in the night at some point as it was not running this morning.

Double clicking /Applications/GRASS-7.4.0 just gives me a program icon but no windows etc.

On the command line I get this:

$ /Applications/ -gui
Cleaning up temporary files…
Starting GRASS GIS…
This program needs access to the screen.
Please run with a Framework build of python, and only when you are
logged in on the main display of your Mac.
ERROR: Error in GUI startup. See messages above (if any) and if necessary, please report this error to the GRASS developers.
On systems with package manager, make sure you have the right GUI package, probably named grass-gui, installed.
To run GRASS GIS in text mode use the -text flag.
Use '—help' for further options
grass74 —help
See also: REDACTED

I've no idea ho to fix this.


This question seems like it would be better to ask to the GRASS users list than this forum that is focused on the Mac binaries. You will get a wider range of useful answers there.


Re: HELP WITH V.VOL.RST by cmbarton54cmbarton54, 20 Feb 2018 03:58

Hello, my name is Miguel Silva and I am new to this group. I need help because I am comparing interpolation methods for precipitation, I am working with all the methods that GRASS has available but the v.vol.rst module is the only one that I can not really use, it generates the interpolation but when I export the raster it only weighs 1kb, and does not have any information.

When I’m doing the interpolation I do not load the raster to perform the cross validation, that’s why I can not do the interpolation well? … I’m not very good at working with commands, so the manual of the module vf.vol.rst, I can not understand it well.

when the method asks me for the name of the layer for cross validation, should I load a raster or vector with values x, y, and z that will be used to perform the validation? ..

If you could help me, I would be very grateful and excuse my English, it’s not very good ..

HELP WITH V.VOL.RST by ilianovichilianovich, 20 Feb 2018 02:47

One important thing to know. You MUST install and run these binaries from /Applications. They cannot be in another folder or a subfolder of /Applications. This is an issue with the way conda (Anaconda) builds the GRASS environment. My colleague Eric might be able to find a way for GRASS apps to run anywhere, but it might be too complicated to be worth it right now.

After many hours of work over the past year+, I finally have a new way to create GRASS binaries for the Mac. This is due in a large part to the help of Eric Hutton at the Community Surface Dynamics Modeling System (CSDMS) at U Colorado.

These new binaries, built with Anaconda, bundle all dependencies inside the *app, including Python and wxPython. They should be much more robust at avoiding conflicts with other versions of dependency programs you may have installed (e.g., gdal, Python, or wxPython). You do NOT need to install any frameworks for these to work, and they ignore any frameworks you have installed. Also, they do not seem to have any problem running with Apple's System Integrity Protection enabled.

Take them for a spin. I do not know which OS X version can run them. Hopefully all recent ones. Ultimately, I'll be archiving all older versions of GRASS, except the legacy pre-OSX 10.8 versions and replacing them with the new ones.

With Eric's help, there may also be an Anaconda package of GRASS in the future, for those who use that environment.


New Mac binaries at last by cmbarton54cmbarton54, 20 Jan 2018 04:51

Thanks for the quick reply Michael! I'm going to poke and prod my machine to try and get it running again, and I can work on my Windows machine in the interim. I wish I could help you out but I'm not much of a programmer. Please keep at it - I love using Grass and appreciate your efforts greatly!


I apologize for not replying to this or other posts sooner. I don't see these forum posts as often as I should due to a very busy past year.

Over the past year +, I've been trying to get GRASS to compile under the new OS (now up to OSX 10.13 - High Sierra). Unfortunately, there has been no one in the GRASS dev community who is able to help with this. Since last summer, I've been working with a colleague to try a new way to build GRASS. It looks hopeful, but we have not yet had success. I hope to have a bit of time over winter break to continue this.

If it all works out, it should avoid the long-running SIP incompatibilities and other problems with 16/32bit dual architecture compiling. There is still a ways to go on this however. I will keep you all posted as this develops. I wish I had better news for the holidays. But I will keep working on this.


Hi -

I've been using Grass for quit a while on my Mac and began experiencing issues with application startup about 6 months ago. I get the same error many others are experiencing with GUI startup and failure (see error message pasted in below). The offending file is:

I usually delete the app and then reload the frameworks and app to get it running again and it usually works for a while but the same error keeps resurfacing. It happened again today when I started Grass 7.0 (and same for reloaded 7.2; both of which work on this machine).

Today was a bit different - I got a notification from my security software that it detected an OSX.Trojan.Gen virus and deleted the file /Applications/

It looks like the deleted file is what's causing my application startup error. Same thing happened when I reinstalled 7.2. My guess this has been happening in the background for quite a while and I was missing the notifications for some reason. This is a huge problem for me now because I can't get the program to work and its impacting my research. Im now at the point where I've installed Grass on my Windows machine at home just to to work on some data (uhg….).

Any suggestions as to what to do in terms of a fix would be very helpful.


Launching <wxpython> GUI in the background, please wait…
GRASS 7.2.svn (wa_coast):~ > Traceback (most recent call last):
File "/Applications/", line 158, in <module>
File "/Applications/", line 145, in main
app = GMApp(workspaceFile)
File "/Applications/", line 48, in init
wx.App.init(self, False)
File "/Applications/", line 7981, in init
File "/Applications/", line 7555, in _BootstrapApp
return _core_.PyApp__BootstrapApp(*args, **kwargs)
File "/Applications/", line 90, in OnInit
from lmgr.frame import GMFrame
File "/Applications/", line 50, in <module>
from lmgr.layertree import LayerTree, LMIcons
File "/Applications/", line 37, in <module>
from mapdisp.frame import MapFrame
File "/Applications/", line 44, in <module>
from gui_core.query import QueryDialog, PrepareQueryResults
File "/Applications/", line 21, in <module>
from gui_core.treeview import TreeListView
File "/Applications/", line 25, in <module>
import wx.gizmos as gizmos
File "/Applications/", line 9, in <module>
import _gizmos
ImportError: dlopen(/Applications/, 2): Library not loaded: /usr/local/lib/wxPython-unicode-
Referenced from: /Applications/
Reason: image not found

I am having the same problem. I am trying to run it on a Mac Sierra. Help anyone??

Re: Grass 7 fails to start by briglmbriglm, 09 Nov 2017 10:20

New install of Grass7.2svn doesn't start with start screen - goes straight to terminal and auto-selects the last mapset and location I was working in. I'm able to start the gui just fine with g.gui wxpython and navigate to other mapsets from there Just a strange behavior that I haven't seen before. Any ideas on how to fix it?

I am experiencing a problem to launch GRASS in MacOS Sierra, when launched ended up with an error

"Last login: Mon Aug 21 09:10:02 on ttys000
MacBooks-MacBook-Pro:~ macbookpro$ '/Applications/'; exit
Rebuilding Addon HTML manual pages index…
Rebuilding Addon menu…
Python 2.7.10 found.
WARNING: Default locale settings are missing. GRASS running with C locale.
Starting GRASS GIS…
dyld: Library not loaded: /usr/local/lib/libintl.8.dylib
Referenced from: /Applications/
Reason: image not found
Traceback (most recent call last):
File "/Applications/", line 31, in <module>
from core import globalvar
File "/Applications/", line 29, in <module>
from core.debug import Debug
File "/Applications/", line 72, in <module>
Debug = DebugMsg()
File "/Applications/", line 37, in init
File "/Applications/", line 43, in SetLevel
self.debuglevel = int(grass.gisenv().get('WX_DEBUG', 0))
File "/Applications/", line 935, in gisenv
s = read_command("g.gisenv", flags='n')
File "/Applications/", line 443, in read_command
process = pipe_command(*args, **kwargs)
File "/Applications/", line 418, in pipe_command
return start_command(*args, **kwargs)
File "/Applications/", line 356, in start_command
if debug_level() > 0:
File "/Applications/", line 1519, in debug_level
_debug_level = int(gisenv().get('DEBUG', 0))
File "/Applications/", line 935, in gisenv
s = read_command("g.gisenv", flags='n')
File "/Applications/", line 446, in read_command
return handle_errors(returncode, stdout, args, kwargs)
File "/Applications/", line 313, in handle_errors
grass.exceptions.CalledModuleError: Module run None ['g.gisenv', '-n'] ended with error
Process ended with non-zero return code -6. See errors in the (error) output.
Error in GUI startup. If necessary, please report this error to the GRASS developers.
Switching to text mode now.

Hit RETURN to continue…

Traceback (most recent call last):
File "/Applications/", line 1461, in <module>
File "/Applications/", line 682, in set_data
gui_startup(grass_gui == 'gtext')
File "/Applications/", line 704, in gui_startup
os.execlp(cmd_name, "-text")
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/", line 329, in execlp
execvp(file, args)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/", line 346, in execvp
_execvpe(file, args)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/", line 382, in _execvpe
func(fullname, *argrest)
OSError: [Errno 2] No such file or directory

Please any idea

page »
Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License