FWIW, I haven't been able to compile GRASS 7 from source for many
weeks now. Last time I asked William Kyngesburye about it, he had not
been able to compile it either. Has anyone else tried on the Mac
recently? I get a lot of errors. I am using geos, with a path set to
one William's framwor
On Mon, Jul 20, 2009 at 6:07 AM, Glynn Clements wrote:
>
> Markus Neteler wrote:
>
>> currently no way to start GRASS as I am used to do:
>>
>> grass70 ~/grassdata/spearfish60/neteler/
>> Cleaning up temporary files ...
>> Starting GRASS ...
>> GISDBASE, LOCATION_NAME and MAPSET variables not set p
Hamish wrote:
> svn/trunk/dist.x86_64-unknown-linux-gnu/lib$ ldd
> libgrass_gis.so
> linux-vdso.so.1 => (0x7fffb79ff000)
> ! ->libgrass_datetime.so => /usr/lib/grass/lib/libgrass_datetime.so
> (0x7fdbaf4e5000)
> libpthread.so.0 => /lib/libpthread.so.0 (0x7fdbaf2c90
Hamish:
> > so (IIUC) swig 1.3.29 requires python >= 2.5 ?
Glynn:
> FWIW, the wrappers generated by SWIG 1.3.36 have:
> IOW, you should just need a newer version of SWIG.
aka ask users to upgrade their OS in order to install a user app. :-/
If this can not be worked around, anyone know what
> Hamish wrote:
> > Debian/Lenny on 64bit:
> > --
> > many/most modules fail to build with:
> > [...]
> > main.c:45: undefined reference to `G_add_keyword'
> >
> > it seems to be there in gisdefs.h . ??
Glynn:
> Defined in lib/gis/parser.c. This suggests that it's linkin
Markus Neteler wrote:
> currently no way to start GRASS as I am used to do:
>
> grass70 ~/grassdata/spearfish60/neteler/
> Cleaning up temporary files ...
> Starting GRASS ...
> GISDBASE, LOCATION_NAME and MAPSET variables not set properly.
> Interactive startup needed.
It doesn't like the trai
Hamish wrote:
> Debian/Lenny on 64bit:
> --
> many/most modules fail to build with:
> [...]
> main.c:45: undefined reference to `G_add_keyword'
>
> it seems to be there in gisdefs.h . ??
Defined in lib/gis/parser.c. This suggests that it's linking against
an old version
Hamish wrote:
> so (IIUC) swig 1.3.29 requires python >= 2.5 ?
FWIW, the wrappers generated by SWIG 1.3.36 have:
/* Py_ssize_t for old Pythons */
/* This code is as recommended by: */
/* http://www.python.org/dev/peps/pep-0353/#conversion-guidelines */
#if PY_VER
Markus Neteler wrote:
> in GRASS 7, I found that
> Rast__allocate_null_bits()
> Rast__null_bitstream_size()
> are used in r.null and r.support.
>
> Question: why Rast__xxx() and not Rast_xxx()?
That's the convention for functions which are meant for internal use
only.
The only code which n
Markus wrote:
> Could the CMD line startup added again? I am not much inclined to
> set three variables manually
yes, please. consider GRASS_BATCH_FILE too.
> when the shell history remembers so nicely
> previous calls (CTRL-R in bash!).
OT tip:
create a file ~/.inputrc and put this in it:
s
Hi,
currently I can't compile GRASS 7.svn on two different machines, fails
in two different ways:
Debian/Lenny on 64bit:
--
many/most modules fail to build with:
[...]
main.c:45: undefined reference to `G_add_keyword'
it seems to be there in gisdefs.h . ??
Debian/Etc
Hamish:
> so (IIUC) swig 1.3.29 requires python >= 2.5 ?
I can get a little further if I iteratively add this patch to *_wrap.c:
--- grass_wrap.c.ORIG 2009-07-20 13:06:52.0 +1200
+++ grass_wrap.c2009-07-20 13:07:15.0 +1200
@@ -111,6 +111,11 @@
/* Python.h has to appea
> > Hamish:
> building relbr6.4 swig/python/ from Debian/Etch (swig
> version 1.3.29-2.1) fails with:
> [...]
> utils_wrap.c: In function 'pyseq_to_ptr':
> utils_wrap.c:2495: error: 'Py_ssize_t' undeclared (first use in this function)
> [...]
> > a #include seems in order.
>
> I am trying t
These files are deleted upon successful completion of the module
using
the iostream lib, nothing left to inspect. They are probably only
useful
for the iostream lib developers for debugging. Same for the
segment lib,
intermediate files are probably only useful for developers working
> Hamish:
> > > building relbr6.4 swig/python/ from Debian/Etch (swig
> > > version 1.3.29-2.1) fails with:
> > > [...]
> > > utils_wrap.c: In function 'pyseq_to_ptr':
> > > utils_wrap.c:2495: error: 'Py_ssize_t' undeclared (first use in this
> > > function)
> > > [...]
>
> Markus:
> > See
> > h
Hamish:
> > building relbr6.4 swig/python/ from Debian/Etch (swig
> > version 1.3.29-2.1) fails with:
> >
> > [...]
> > utils_wrap.c: In function 'pyseq_to_ptr':
> > utils_wrap.c:2495: error: 'Py_ssize_t' undeclared (first use in this
> > function)
> > utils_wrap.c:2495: error: (Each undeclared i
#643: support external data sources in the wxPython-GUI
-+--
Reporter: timmie | Owner: grass-dev@lists.osgeo.org
Type: task| Status: closed
Priority: minor | Milestone: 6.4
Hi,
currently no way to start GRASS as I am used to do:
grass70 ~/grassdata/spearfish60/neteler/
Cleaning up temporary files ...
Starting GRASS ...
GISDBASE, LOCATION_NAME and MAPSET variables not set properly.
Interactive startup needed.
Could the CMD line startup added again? I am not much inc
#520: r.terraflow/iostream does not respect STREAM_DIR option
-+--
Reporter: mmetz | Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: major | Milestone
Hi,
in GRASS 7, I found that
Rast__allocate_null_bits()
Rast__null_bitstream_size()
are used in r.null and r.support.
Question: why Rast__xxx() and not Rast_xxx()?
Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/m
On Fri, Jun 19, 2009 at 1:27 PM, Hamish wrote:
> Hi,
>
> I'm a bit confused with v.lidar EDGE/TERRAIN/UNKNOWN #defines.
>
> v.lidar.edgedetection categorizes data points as either of those three.
>
> output vector map includes cats 0,1,2 by layer 1.
> (also there is a DB on layer 3, but that is no
#679: i.gensigset
--+-
Reporter: ptmt | Owner: grass-dev@lists.osgeo.org
Type: defect | Status: closed
Priority: normal | Milestone: 6.4.0
On Sat, Jul 18, 2009 at 8:14 AM, Hamish wrote:
>
> Glynn wrote:
>> 6.x still doesn't build the swig directory, but 7.0 does.
>
>
> to remind from an earlier thread:
>
> building relbr6.4 swig/python/ from Debian/Etch (swig version 1.3.29-2.1)
> fails with:
>
> [...]
> utils_wrap.c: In function 'pys
On Sat, Jul 18, 2009 at 6:48 AM, Glynn Clements wrote:
> Markus Neteler wrote:
>
>> still SWIG-Python is lacking from install sequence in main Makefile.
>> Is there a reason for that? Say, how to use the examples like
>> rasteraccess.py when I have "just" the installed GRASS version?
>
> Installati
#692: computational region in grasswxpy.po file
---+
Reporter: lucadelu | Owner: grass-dev@lists.osgeo.org
Type: defect| Status: new
Priority: normal| Miles
#692: computational region in grasswxpy.po file
---+
Reporter: lucadelu | Owner: grass-dev@lists.osgeo.org
Type: defect| Status: new
Priority: normal| Miles
#692: computational region in grasswxpy.po file
---+
Reporter: lucadelu | Owner: grass-dev@lists.osgeo.org
Type: defect| Status: new
Priority: normal| Miles
27 matches
Mail list logo
