[mapguide-trac] #1471: Mapguide Maestro 2.1. Validating a layer based on a view does not always work

MapGuide Open Source trac_mapguide at osgeo.org
Tue Oct 26 06:27:38 EDT 2010


#1471: Mapguide Maestro 2.1. Validating a layer based on a view does not always
work
--------------------------+-------------------------------------------------
   Reporter:  gabrimonfa  |       Owner:  jng        
       Type:  defect      |      Status:  new        
   Priority:  low         |   Milestone:  Maestro-3.0
  Component:  Maestro     |     Version:  2.1.0      
   Severity:  trivial     |    Keywords:             
External_id:              |  
--------------------------+-------------------------------------------------

Comment(by gabrimonfa):

 I'm using gdal 1.7.2 (from SVN stable), enabling PostgreSQL/PostGIS
 support

 I've compiled it on centos 5 i386.
 This is configuration report:

 GDAL is now configured for i686-pc-linux-gnu

   Installation directory:    /usr/local[[BR]]
   C compiler:                gcc -g -O2[[BR]]
   C++ compiler:              g++ -g -O2[[BR]]

   LIBTOOL support:           yes

   LIBZ support:              external[[BR]]
   GRASS support:             no[[BR]]
   CFITSIO support:           no[[BR]]
   PCRaster support:          internal[[BR]]
   NetCDF support:            no[[BR]]
   LIBPNG support:            internal[[BR]]
   LIBTIFF support:           external (BigTIFF=no)[[BR]]
   LIBGEOTIFF support:        internal[[BR]]
   LIBJPEG support:           external[[BR]]
   8/12 bit JPEG TIFF:        no[[BR]]
   LIBGIF support:            internal[[BR]]
   OGDI support:              no[[BR]]
   HDF4 support:              no[[BR]]
   HDF5 support:              no[[BR]]
   Kakadu support:            no[[BR]]
   JasPer support:            no[[BR]]
   ECW support:               no[[BR]]
   MrSID support:             no[[BR]]
   MSG support:               no[[BR]]
   GRIB support:              yes[[BR]]
   EPSILON support:           no[[BR]]
   cURL support (wms/wcs/...):yes[[BR]]
   PostgreSQL support:        yes[[BR]]
   MySQL support:             no[[BR]]
   Ingres support:            no[[BR]]
   Xerces-C support:          no[[BR]]
   NAS support:               no[[BR]]
   Expat support:             no[[BR]]
   ODBC support:              no[[BR]]
   PGeo support:              no[[BR]]
   PCIDSK support:            internal[[BR]]
   OCI support:               no[[BR]]
   GEORASTER support:         no[[BR]]
   SDE support:               no[[BR]]
   DODS support:              no[[BR]]
   SQLite support:            no[[BR]]
   SpatiaLite support:        no[[BR]]
   DWGdirect support          no[[BR]]
   INFORMIX DataBlade support: no[[BR]]
   GEOS support:              no[[BR]]
   VFK support:               yes[[BR]]

   SWIG Bindings:          no[[BR]]

   Statically link PROJ.4:    no[[BR]]
   enable OGR building:       yes[[BR]]
   enable pthread support:    no[[BR]]
   hide internal symbols:     no[[BR]]

 Then I installed it in /usr/local/lib and symlinked it in
 /usr/local/fdo-3.5.0/lib/libgdal.so.1

 I've verified that

 ldd /usr/local/lib/libgdal.so | grep not[[BR]]
 ldd -r /usr/local/lib/libgdal.so | grep undefined

 are empty (no missing symbols & libraries) and that

 ldd /usr/local/lib/libgdal.so | grep pq[[BR]]
         libpq.so.4 => /usr/lib/libpq.so.4

 (PostgreSQL support is indeed enabled) and that

 ldd libOGRProvider.so | grep gdal[[BR]]
         libgdal.so.1 => /usr/local/fdo-3.5.0/lib/libgdal.so.1

 and that

 ls -l /usr/local/fdo-3.5.0/lib/libgdal.so.1[[BR]]
    /usr/local/fdo-3.5.0/lib/libgdal.so.1 -> /usr/local/lib/libgdal.so

 and that

 ldd libOGRProvider.so| grep not[[BR]]
 ldd -r libOGRProvider.so| grep undefined

 are empty[[BR]]
 Thus no undefined symbols everywhere

 My libgdal.so.1.14.2, renamed to libgdal.so for your convenience, is
 attached

-- 
Ticket URL: <http://trac.osgeo.org/mapguide/ticket/1471#comment:3>
MapGuide Open Source <http://mapguide.osgeo.org/>
MapGuide Open Source Internals


More information about the mapguide-trac mailing list