[Gdal-dev] Compling GDAL 1.3.1 in MinGW

Mike Leahy mgleahy at golden.net
Thu Dec 8 22:18:10 EST 2005 

Ok, without sqlite, I get a new error:

(cd .libs && rm -f libgdal.la && ln -s ../libgdal.la libgdal.la)
make[1]: Leaving directory `/Downloads/gdal-1.3.1'
(cd swig; make build)
make[1]: Entering directory `/Downloads/gdal-1.3.1/swig'
for dir in ; do (cd $dir; make build ); done
/bin/sh.exe: -c: line 1: syntax error near unexpected token `;'
/bin/sh.exe: -c: line 1: `for dir in ; do (cd $dir; make build ); done'
make[1]: *** [build] Error 2
make[1]: Leaving directory `/Downloads/gdal-1.3.1/swig'
make: *** [swig-target] Error 2

Is there something else I've missed?

Mike

Mike Leahy wrote:
> Daniel,
> 
> All of your suggestions seem to have worked fine so far.  Thanks for the
> help.
> 
> However, I now I'm having issues with sqlite:
> 
> .libs/libgdal.la-3.o:ogrsqlitedatasource.cpp:(.text+0x1068c3): undefined
> reference to `sqlite3_close'
> .libs/libgdal.la-3.o:ogrsqlitedatasource.cpp:(.text+0x106a63): undefined
> reference to `sqlite3_close'
> .libs/libgdal.la-3.o:ogrsqlitedatasource.cpp:(.text+0x106c03): undefined
> reference to `sqlite3_close'
> .libs/libgdal.la-3.o:ogrsqlitedatasource.cpp:(.text+0x106e1b): undefined
> reference to `sqlite3_open'
> .libs/libgdal.la-3.o:ogrsqlitedatasource.cpp:(.text+0x106e2a): undefined
> reference to `sqlite3_errmsg'
> 
> <snip>
> 
> .libs/libgdal.la-3.o:ogrsqlitetablelayer.cpp:(.text+0x10a280): undefined
> reference to `sqlite3_exec'
> .libs/libgdal.la-3.o:ogrsqlitetablelayer.cpp:(.text+0x10a3c5): undefined
> reference to `sqlite3_exec'
> .libs/libgdal.la-3.o:ogrsqlitetablelayer.cpp:(.text+0x10a7ae): more
> undefined references to `sqlite3_exec' follow
> .libs/libgdal.la-3.o:ogrsqlitetablelayer.cpp:(.text+0x10aba2): undefined
> reference to `sqlite3_free'
> collect2: ld returned 1 exit status
> make[1]: *** [libgdal.la] Error 1
> make[1]: Leaving directory `/Downloads/gdal-1.3.1'
> make: *** [check-lib] Error 2
> 
> I'll give it another run, and see if it works without sqlite support.
> 
> Mike
> 
> Daniel Wallner wrote:
>> Hi,
>> I just stumbled into this myself a few hours ago :)
>>
>> The problem is in this file:
>> frmts/gtiff/libtiff/tif_jpeg.c
>> Comment out line 69 and 71
>> (Don't know a clean solution though.)
>>
>> And unfortunately here too:
>> (eeek, my bad, I wrote that driver :)
>> frmts/rik/GNUmakefile
>> you need to add -I../zlib to the compile options
>> (Don't know how this is best done either.)
>>
>> Then you need to add cpl_vsil_win32.o to
>> port/GNUmakefile too.
>>
>> That should do it.
>>
>> And I think you need these options:
>> ./configure --without-unix-stdio-64 --with-sqlite=/c/mingw
>>
>> Regards,
>> Daniel
>>
>>> From: Mike Leahy <mgleahy at golden.net>
>>> Date: 2005/12/09 fr AM 12:07:32 CET
>>> To: gdal-dev at lists.maptools.org
>>> Ämne: [Gdal-dev] Compling GDAL 1.3.1 in MinGW
>>>
>>> Hello list,
>>>
>>> I'm hoping some of the other users out there that have has success with
>>> this might be able to give me some advice.  I've been trying to compile
>>> GDAL with MinGW/MSYS, and I'm currently running into trouble when the
>>> make process hits tif_jpeg.c.  I've configured GDAL with the following
>>> options:
>>>
>>>
>>> ./configure --prefix=/usr/local --with-jpeg=internal --with-png=internal
>>> --with-tiff=internal --with-libz=internal --with-sqlite=/c/mingw
>>> --without-unix-stdio-64
>>>
>>>
>>> And I get the following errors when I compile:
>>>
>>>
>>> In file included from ../../jpeg/libjpeg/jpeglib.h:24,
>>>                  from tif_jpeg.c:75:
>>> ../../jpeg/libjpeg/jconfig.h:12:1: warning: "HAVE_STDLIB_H" redefined
>>> In file included from tif_config.h:2,
>>>                  from tiffconf.h:3,
>>>                  from tiff.h:30,
>>>                  from tiffio.h:33,
>>>                  from tiffiop.h:60,
>>>                  from tif_jpeg.c:27:
>>> ../../../port/cpl_config.h:75:1: warning: this is the location of the
>>> previous definition
>>> In file included from tif_jpeg.c:75:
>>> ../../jpeg/libjpeg/jpeglib.h:94: error: syntax error before "boolean"
>>> ../../jpeg/libjpeg/jpeglib.h:94: warning: no semicolon at end of struct
>>> or union
>>> ../../jpeg/libjpeg/jpeglib.h:95: warning: type defaults to `int' in
>>> declaration of `JQUANT_TBL'
>>> ../../jpeg/libjpeg/jpeglib.h:95: warning: data definition has no type or
>>> storage class
>>> ../../jpeg/libjpeg/jpeglib.h:110: error: syntax error before "boolean"
>>> ../../jpeg/libjpeg/jpeglib.h:110: warning: no semicolon at end of struct
>>> or union
>>> ../../jpeg/libjpeg/jpeglib.h:111: warning: type defaults to `int' in
>>> declaration of `JHUFF_TBL'
>>> ../../jpeg/libjpeg/jpeglib.h:111: warning: data definition has no type
>>> or storage class
>>> ../../jpeg/libjpeg/jpeglib.h:160: error: syntax error before "boolean"
>>> ../../jpeg/libjpeg/jpeglib.h:160: warning: no semicolon at end of struct
>>> or union
>>> ../../jpeg/libjpeg/jpeglib.h:175: error: syntax error before '*' token
>>> ../../jpeg/libjpeg/jpeglib.h:175: warning: type defaults to `int' in
>>> declaration of `quant_table'
>>> ../../jpeg/libjpeg/jpeglib.h:175: warning: data definition has no type
>>> or storage class
>>> ../../jpeg/libjpeg/jpeglib.h:179: error: syntax error before '}' token
>>> ../../jpeg/libjpeg/jpeglib.h:179: warning: type defaults to `int' in
>>> declaration of `jpeg_component_info'
>>> ../../jpeg/libjpeg/jpeglib.h:179: warning: data definition has no type
>>> or storage class
>>> ../../jpeg/libjpeg/jpeglib.h:254: error: syntax error before "boolean"
>>> ../../jpeg/libjpeg/jpeglib.h:254: warning: no semicolon at end of struct
>>> or union
>>> ../../jpeg/libjpeg/jpeglib.h:259: error: syntax error before '}' token
>>> ../../jpeg/libjpeg/jpeglib.h:269: error: syntax error before "boolean"
>>> ../../jpeg/libjpeg/jpeglib.h:269: warning: no semicolon at end of struct
>>> or union
>>>
>>> etc...
>>>
>>> I've been digging around, and found some stuff about different ways of
>>> declaring booleans when compiling GDAL with MinGW (e.g., int vs.
>>> unsigned char), but from what I can tell after looking at the code this
>>> seems to have been taken care of already (at least in GDAL-1.3.1).  Is
>>> there be anything else I should try?
>>>
>>> Regards,
>>> Mike
>>> _______________________________________________
>>> Gdal-dev mailing list
>>> Gdal-dev at lists.maptools.org
>>> http://lists.maptools.org/mailman/listinfo/gdal-dev
>>>
>> _______________________________________________
>> Gdal-dev mailing list
>> Gdal-dev at lists.maptools.org
>> http://lists.maptools.org/mailman/listinfo/gdal-dev
>>
> 
> _______________________________________________
> Gdal-dev mailing list
> Gdal-dev at lists.maptools.org
> http://lists.maptools.org/mailman/listinfo/gdal-dev
>

More information about the Gdal-dev mailing list