Hi Pietro,
2013/11/29 Pietro Zambelli peter.z...@gmail.com:
On Friday 29 Nov 2013 06:54:59 you wrote:
What it is wrong and how to fix it? Any ideas?
Please try make distclean,I had similar problems some day ago
I did, actually, so should be something else I guess...
please could you
Hi,
2013/11/27 Vaclav Petras wenzesl...@gmail.com:
it's not really related to this issue. Anyway it would be probably
good idea to rename all environmental variables related to rendering,
e.g. GRASS_WIDTH to GRASS_DISPLAY_WIDTH, GRASS_DISP_WIDTH, or
GRASS_RENDER_WIDTH and so on.
The
#2134: Create a general exit-safe interface to C libraries
--+-
Reporter: wenzeslaus| Owner: grass-dev@…
Type: enhancement | Status: new
It looks very much like an out-of-memory error. In the gdb backtrace I see
#4 0x76601ebd in RTreeNewListBranch (t=0x609c30) at node.c:441
p = 0x0
which means that memory allocation failed.
Try
export GRASS_VECTOR_LOWMEM=1
r.to.vect --o --v input=seg_0.05_final@pietro
I've been chilling out after Thanksgiving and thought I'd try compiling GRASS
on Mavericks.
I had a couple of configure issues.
--with-odbc failed. Is this not included with Mavericks or do I need to
reference it in some other way?
--with nls also failed. I wonder if I have to update the
On Fri, Nov 29, 2013 at 9:02 PM, Michael Barton michael.bar...@asu.edu wrote:
I've been chilling out after Thanksgiving and thought I'd try compiling
GRASS on Mavericks.
I had a couple of configure issues.
--with-odbc failed. Is this not included with Mavericks or do I need to
reference it
#2139: g.parser does not allow newline character in option value for Python
scripts
+---
Reporter: wenzeslaus | Owner: grass-dev@…
Type: defect
