I don't think GDALFPolygonize is the problem, that's just a test for a new feature in development GDAL and it's OK if it fails. After that should be the "checking for GDAL Python bindings" info.
On Oct 17, 2011, at 10:28 PM, Puneet Kishor wrote: > > On Oct 17, 2011, at 9:22 PM, William Kyngesburye wrote: > >> Try looking in config.log for a more detailed explanation why it couldn't >> find GDAL python. > > > I see stuff like this... > > configure:19000: result: TOPOLOGY: Topology support requested > configure:19023: result: RASTER: Raster support requested > configure:19111: checking for GDAL >= 1.6.0 > configure:19145: result: found > configure:19148: checking for GDALFPolygonize in -lgdal > configure:19173: gcc -o conftest -g -O2 -I/opt/local/include > -I/opt/local/include -I/opt/local/include/libxml2 conftest.c -lgdal -lxml2 > -L/opt/local/lib -lxml2 -lz -lpthread -liconv -lm >&5 > Undefined symbols for architecture x86_64: > "_GDALFPolygonize", referenced from: > _main in cclcxE0h.o > ld: symbol(s) not found for architecture x86_64 > > and.. > > GDALFPOLYGONIZE='' > GEOSCONFIG='/opt/local/bin/geos-config' > GEOS_CPPFLAGS='-I/opt/local/include' > GEOS_LDFLAGS='-L/opt/local/lib' > > and perhaps > > #define HAVE_LIBGEOS_C 1 > #define POSTGIS_GEOS_VERSION 33 > #define HAVE_CFPREFERENCESCOPYAPPVALUE 1 > #define HAVE_CFLOCALECOPYCURRENT 1 > #define POSTGIS_PROJ_VERSION 47 > #define HAVE_LIBPROJ 1 > #define POSTGIS_DEBUG_LEVEL 0 > #define POSTGIS_PROFILE 0 > #define POSTGIS_VERSION "2.0 USE_GEOS=1 USE_PROJ=1 USE_STATS=1" > #define POSTGIS_LIB_VERSION "2.0.0SVN" > #define POSTGIS_BUILD_DATE "2011-10-18 02:30:06" > #define POSTGIS_SCRIPTS_VERSION "2.0 r7940" > #define POSTGIS_AUTOCACHE_BBOX 1 > #define POSTGIS_USE_STATS 1 > #define POSTGIS_RASTER_MAJOR_VERSION "0" > #define POSTGIS_RASTER_MINOR_VERSION "1" > #define POSTGIS_RASTER_MICRO_VERSION "6d" > #define POSTGIS_RASTER_VERSION "0.1" > #define POSTGIS_RASTER_LIB_VERSION "0.1.6d" > #define POSTGIS_RASTER_BUILD_DATE "2011-10-18 02:30:06" > #define POSTGIS_RASTER_SCRIPTS_VERSION "0.1.6d" > #define GDALFPOLYGONIZE 0 > > > Other than that, I can't really tell. > > > >> >> On Oct 17, 2011, at 8:48 PM, Puneet Kishor wrote: >> >>> Any suggestions, anyone? As shown below, I believe I have the Python >>> bindings for GDAL installed, yet, I get the following error >>> >>> RASTER: Raster support requested >>> checking for GDAL >= 1.6.0... found >>> checking for GDALFPolygonize in -lgdal... no >>> checking for GDAL Python bindings... not found >>> configure: error: GDAL Python bindings required by raster2pgsql.py loader >>> >>> I am not quite sure how to convince the .configure script that I do have >>> gdal w/Python. >>> >>> >>> On Oct 16, 2011, at 2:31 PM, Mr. Puneet Kishor wrote: >>> >>>> From: "Mr. Puneet Kishor" <punk...@eidesis.org> >>>> Subject: configure: error: GDAL Python bindings required by >>>> raster2pgsql.py loader >>>> Date: October 16, 2011 2:29:19 PM CDT >>>> To: PostGIS Users Discussion <postgis-users@postgis.refractions.net> >>>> >>>> >>>> I believe I did install the GDAL Python bindings (via MacPorts), but my >>>> PostGIS 2.0 configure script claims I don't have it. Is there are way I >>>> can determine whether or not I have the bindings installed? (I am not >>>> Python-savvy) But, I do see stuff like so ----- William Kyngesburye <kyngchaos*at*kyngchaos*dot*com> http://www.kyngchaos.com/ "Time is an illusion - lunchtime doubly so." - Ford Prefect _______________________________________________ postgis-users mailing list postgis-users@postgis.refractions.net http://postgis.refractions.net/mailman/listinfo/postgis-users
