On Sat, 2007-11-03 at 13:20 -0400, Chip Griffin wrote: > I was not able to get GDAL (1.4.3) to compile. I tried with just "./ > configure" and got an error when I tried to 'make' it. So, per the > INSTALL file, I tried several of the switches mentioned. I added the > 'internal' options one at a time, and still wasn't able to get it to > compile even after they were all added. This is the error at the end > of the make when the exact "./configure" with switches is used from > the INSTALL file. > > > Undefined symbols: > > "_gtCSLCount", referenced from: > > OGCDatumName2EPSGDatumCode(char const*)in gt_wkt_srs.o > > "_gtCPLError", referenced from: > > _GTIFSetFromOGISDefn in gt_wkt_srs.o > > _GTIFWktFromMemBuf in gt_wkt_srs.o > > _GTIFMemBufFromWkt in gt_wkt_srs.o > > "_gtCPLMalloc", referenced from: > > _GTIFMemBufFromWkt in gt_wkt_srs.o > > "_gtCSLDestroy", referenced from: > > OGCDatumName2EPSGDatumCode(char const*)in gt_wkt_srs.o > > OGCDatumName2EPSGDatumCode(char const*)in gt_wkt_srs.o > > OGCDatumName2EPSGDatumCode(char const*)in gt_wkt_srs.o > > "_gtCSVFilename", referenced from: > > OGCDatumName2EPSGDatumCode(char const*)in gt_wkt_srs.o > > OGCDatumName2EPSGDatumCode(char const*)in gt_wkt_srs.o > > "_gtCSVReadParseLine", referenced from: > > OGCDatumName2EPSGDatumCode(char const*)in gt_wkt_srs.o > > OGCDatumName2EPSGDatumCode(char const*)in gt_wkt_srs.o > > OGCDatumName2EPSGDatumCode(char const*)in gt_wkt_srs.o > > "_gtCPLCalloc", referenced from: > > _GTIFWktFromMemBuf in gt_wkt_srs.o > > "_gtCPLStrdup", referenced from: > > WKTMassageDatum(char**) in gt_wkt_srs.o > > WKTMassageDatum(char**) in gt_wkt_srs.o > > _GTIFGetOGISDefn in gt_wkt_srs.o > > _GTIFGetOGISDefn in gt_wkt_srs.o > > _GTIFGetOGISDefn in gt_wkt_srs.o > > _GTIFWktFromMemBuf in gt_wkt_srs.o > > _GTIFWktFromMemBuf in gt_wkt_srs.o > > ld: symbol(s) not found > > collect2: ld returned 1 exit status > > make[1]: *** [libgdal.la] Error 1 > > make: *** [check-lib] Error 2
Looks like improperly setup libtiff or libgeotiff to me. Did you try using 'internal' for both of them together? It could also be a C++ issue, but hard to tell from this vantage. C++ is plagued with inconsistencies and portability issues. Frank almost wishes he didn't start the gdal project using C++. It's been difficult to maintain. If you're still having trouble, I'd suggest trying #gdal, #osgeo, or the gdal mailing list for a quicker resolution. -- 73, de Brad KB8UYR/6 <rez touchofmadness com> _______________________________________________ Xastir mailing list [email protected] http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
