MacOSX GRASS errors

From GRASS-Wiki
Revision as of 15:37, 1 December 2016 by Neteler (talk | contribs) (+ support forum url)

Jump to: navigation, search

Here some problems reported by users along with solutions:

Starting GRASS GIS on MacOSX, I get "image not found"

You are lacking the installation of one or several "frameworks" (e.g. GDAL). Get them from here:
--> Install the required framework packages first

Starting GRASS GIS on MacOSX, I get "bad cpu type in executable"

It looks like a macports problem (maybe homebrew also uses /opt/local?) with their Python. A guess is that their python is 64bit-only, and GRASS is trying to run python 32bit because it couldn't find a 64bit wxpython because 64bit wxpython isn't existing yet in the stable release.
Work-around: Edit the file ".bash_profile" in your HOME directory and add therein:

export GRASS_PYTHON=/usr/bin/python2.6
export GRASS_PYTHONWX=/usr/bin/pythonw2.6

When using g.extension, I get "fatal error: grass/gis.h: No such file or directory"

Hint: g.extension should indeed work. The main key is that you need to install the Xcode command line tools. This can be done either from the Xcode app (free from app store), or by downloading the command line tools installer separately (from an Apple developer account).

Starting GRASS GIS on MacOSX, I get "AppleScript Error. Terminal got an error: Can't get window 1. (-1728)"

Note: Normally when Terminal is activated (running or not), it starts a new window if there is none open, but I've seen cases where it does not when you start Terminal when it was NOT running.

Solution: Try starting Terminal first, then start GRASS.

Starting GRASS GIS on MacOSX, I get "ERROR: unknown locale: UTF-8"

You need to add these two lines

export LC_ALL=en_US.UTF-8
export LANG=en_US.UTF-8

to the file ".bash_profile" in your HOME directory. You can use any text editor to create/edit the file $HOME/.bash_profile (the same: ~/.bash_profile) and copy-paste the these two lines. Just be sure to save it as ".bash_profile" in your home directory.

d.legend does not show numbers

Problem: d.legend and other text is not shown in the display!

Solution: You need to rescan the fonts available on your system:

 g.mkfontcap -o

See also