Re: [GRASS-dev] SWIG-Python lacking from install sequence in main Makefile

2009-07-28 Thread Moritz Lennert
On 28/07/09 16:55, Glynn Clements wrote: Moritz Lennert wrote: I am still having problems compiling swig/python on Debian/Lenny (current stable) / 64bit with the latest GRASS 6.5svn. the proj headers are missing from the $() Make rules: "error: ogr_srs_api.h: No such file or directory" it c

Re: [GRASS-dev] SWIG-Python lacking from install sequence in main Makefile

2009-07-28 Thread Glynn Clements
Moritz Lennert wrote: > >> I am still having problems compiling swig/python on Debian/Lenny (current > >> stable) / 64bit with the latest GRASS 6.5svn. > >> > >> the proj headers are missing from the $() Make rules: > >> "error: ogr_srs_api.h: No such file or directory" > >> > >> it compiles in

Re: [GRASS-dev] SWIG-Python lacking from install sequence in main Makefile

2009-07-27 Thread Moritz Lennert
On 24/07/09 12:21, Glynn Clements wrote: Hamish wrote: I am still having problems compiling swig/python on Debian/Lenny (current stable) / 64bit with the latest GRASS 6.5svn. the proj headers are missing from the $() Make rules: "error: ogr_srs_api.h: No such file or directory" it compiles

Re: [GRASS-dev] SWIG-Python lacking from install sequence in main Makefile

2009-07-24 Thread Glynn Clements
Hamish wrote: > I am still having problems compiling swig/python on Debian/Lenny (current > stable) / 64bit with the latest GRASS 6.5svn. > > the proj headers are missing from the $() Make rules: > "error: ogr_srs_api.h: No such file or directory" > > it compiles in trunk ok. Note that using

Re: [GRASS-dev] SWIG-Python lacking from install sequence in main Makefile

2009-07-23 Thread Hamish
I am still having problems compiling swig/python on Debian/Lenny (current stable) / 64bit with the latest GRASS 6.5svn. the proj headers are missing from the $() Make rules: "error: ogr_srs_api.h: No such file or directory" it compiles in trunk ok. [...] gcc -I/usr/local/src/grass/svn/grass65

Re: [GRASS-dev] SWIG-Python lacking from install sequence in main Makefile

2009-07-19 Thread Hamish
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

Re: [GRASS-dev] SWIG-Python lacking from install sequence in main Makefile

2009-07-19 Thread Glynn Clements
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

Re: [GRASS-dev] SWIG-Python lacking from install sequence in main Makefile

2009-07-19 Thread Hamish
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

Re: [GRASS-dev] SWIG-Python lacking from install sequence in main Makefile

2009-07-19 Thread Hamish
> > 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

Re: [GRASS-dev] SWIG-Python lacking from install sequence in main Makefile

2009-07-19 Thread Hamish
> 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

Re: [GRASS-dev] SWIG-Python lacking from install sequence in main Makefile

2009-07-19 Thread Hamish
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

Re: [GRASS-dev] SWIG-Python lacking from install sequence in main Makefile

2009-07-19 Thread Markus Neteler
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

Re: [GRASS-dev] SWIG-Python lacking from install sequence in main Makefile

2009-07-19 Thread Markus Neteler
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

Re: [GRASS-dev] SWIG-Python lacking from install sequence in main Makefile

2009-07-17 Thread Hamish
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 'pyseq_to_ptr': utils_wrap.c:2495: error: 'Py_ssize_t' undeclared (fi

Re: [GRASS-dev] SWIG-Python lacking from install sequence in main Makefile

2009-07-17 Thread Glynn Clements
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? Installation shouldn't need any special treatment in the top-level Makefi

[GRASS-dev] SWIG-Python lacking from install sequence in main Makefile

2009-07-17 Thread Markus Neteler
Hi, 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? Markus ___ grass-dev mailing list grass-dev@lists.osge