Re: [gdal-dev] Re: Conflicts when using GDAL with minGW

2009-02-24 Thread Ari Jolma
LF kirjoitti: Ozy Sjahputera missouri.edu> writes: ... error: `snprintf' is not a member of `std' e:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/math.h error: declaration of C function `float _copysign(float, float)' conflicts with e:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../.

Re: [gdal-dev] [1.6.0][GDALWARP] World file name is empty

2009-02-24 Thread RICHARD Didier
> Hi, > > yes that very same problem was detected in 1.6.0 as ticket > http://trac.osgeo.org/gdal/ticket/2760 and it was fixed in both trunk and > branches/1.6. So it will be solved in 1.6.1. > Thanks Even (I could not find it in the trac), and yes (Frank), it is working with the trunk ! All the

Re: [gdal-dev] [1.6.0][GDALWARP] World file name is empty

2009-02-24 Thread Even Rouault
Hi, yes that very same problem was detected in 1.6.0 as ticket http://trac.osgeo.org/gdal/ticket/2760 and it was fixed in both trunk and branches/1.6. So it will be solved in 1.6.1. Best regards, Even Le Tuesday 24 February 2009 19:18:45 Frank Warmerdam, vous avez écrit : > RICHARD Didier wro

Re: [gdal-dev] [1.6.0][GDALWARP] World file name is empty

2009-02-24 Thread Frank Warmerdam
RICHARD Didier wrote: Hi all, I am having the following behavior with gdalwarp (freshly compiled from 1.6.0) when I am requiring to get a tfw file (former releases didn't have this behavior) : $ gdalwarp ... -co "TFW=YES" in.tif out.tif "out.tif" and ".tfw" files are generated (before 1.6.0, I

[gdal-dev] [1.6.0][GDALWARP] World file name is empty

2009-02-24 Thread RICHARD Didier
Hi all, I am having the following behavior with gdalwarp (freshly compiled from 1.6.0) when I am requiring to get a tfw file (former releases didn't have this behavior) : $ gdalwarp ... -co "TFW=YES" in.tif out.tif "out.tif" and ".tfw" files are generated (before 1.6.0, I got "out.tif" and "out.

[gdal-dev] Re: Conflicts when using GDAL with minGW

2009-02-24 Thread LF
LF interfree.it> writes: > > It seems that the GDAL library is causing some functions in the minGW > > C++ library (cstdio) to be undeclared. > I had two conflicts between mingw and gdal for variables *_copysign* > and *ssize_t*, defined in both mingw and gdal. > Should I define some macros or

[gdal-dev] Re: Conflicts when using GDAL with minGW

2009-02-24 Thread LF
Ozy Sjahputera missouri.edu> writes: > ... > > error: `snprintf' is not a member of `std' > e:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/math.h error: > declaration of C function `float _copysign(float, float)' conflicts with > e:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../incl