Well, I've fixed this, but I had to remove the entire build dir and recompile. I'm guessing that when ./configure is run the first time, it creates some sort of mapscript file used later by distutils when Python mapscript is built. I can't prove it, and I don't have the time to keep re-testing, but it appears that neither running "make clean", or recompiling makes a difference once that file is present. --
On Thu, Jan 28, 2010 at 10:18 AM, Roger André <ran...@gmail.com> wrote: > Hi All, > > I'm getting kinda stumped by this error. I'm running MapServer-5.6.0, > Python 2.6, postgresql-8.4.2, and postgis-1.4.1 on an Ubuntu 9.10 box. I've > compiled mapserver with PostGIS support... > > $ /usr/lib/cgi-bin/mapserv -v > MapServer version 5.6.0 OUTPUT=GIF OUTPUT=PNG OUTPUT=JPEG OUTPUT=WBMP > OUTPUT=SVG SUPPORTS=PROJ SUPPORTS=AGG SUPPORTS=FREETYPE SUPPORTS=ICONV > SUPPORTS=WMS_SERVER SUPPORTS=WMS_CLIENT SUPPORTS=WFS_SERVER > SUPPORTS=WFS_CLIENT SUPPORTS=WCS_SERVER SUPPORTS=FASTCGI SUPPORTS=THREADS > SUPPORTS=GEOS INPUT=TIFF INPUT=EPPL7 INPUT=POSTGIS INPUT=OGR INPUT=GDAL > INPUT=SHAPEFILE > > and I'm able to make a regular old "mode=map" request via cgi to a layer > that is coming from PostGIS. However, when I try to access the same layer > via Python mapscript, I get the following error: > > _mapscript.MapServerError: msDrawMap(): Image handling error. Failed to > draw layer named 'roadsPG'. > msPostGISLayerOpen(): General error message. PostGIS support is not > available. > > I had omitted to include Postgis support in my MapServer build initially, > but did a "make clean" and rebuilt it. I also re-ran the Python mapscript > install afterwards. Is there something else I need to do to clean out the > old mapscript module? I'm no distutils expert, so any help would be > appreciated. > > Thanks, > > Roger > -- >
_______________________________________________ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
