64bit Linux support

[Frank Warmerdam]

On Wed, Jan 16, 2002 at 07:07:31PM -0800, Mark Aubin wrote:
> I've just done a clean checkout. I'm afraid that
> maybe my hacking around might have left some cruft.
> 
> Here's what I get:
> 
> 
> ./configure --with-unix-stdio-64
> 
> make
> (cd port; make)
...
> c++ -c -Wall -fPIC -O2 -I/usr/local/include cpl_vsil_unix_stdio_64.cpp -o 
> cpl_vsil_unix_stdio_64.o
> cpl_vsil_unix_stdio_64.cpp: In function `int VSIFSeekL (FILE *, long
> long unsigned int, int)':
> cpl_vsil_unix_stdio_64.cpp:87: `fseek64' undeclared (first use this
> function)
> cpl_vsil_unix_stdio_64.cpp:87: (Each undeclared identifier is reported
> only once for each function it appears in.)
> cpl_vsil_unix_stdio_64.cpp: In function `vsi_l_offset VSIFTellL (FILE
> *)':
> cpl_vsil_unix_stdio_64.cpp:97: `ftell64' undeclared (first use this
> function)
> make[1]: *** [cpl_vsil_unix_stdio_64.o] Error 1
> make[1]: Leaving directory `/home/aubin/trees/gdal/port'
> make: *** [port-target] Error 2
> 
> 
> 
> Then it occured to me that maybe I shouldn't use the special
> configure flag. I re-do the configure and try make again, and it
> seems to be happy!
> 
> Now I am trying to run gdal_translate on a 2.5GB file. I'll
> let you know.
> 
> So at this point, looks good. Thanks for taking the plunge. :)

Mark, 

Detection of 64bit stdio is automatic. All the --with-unix-stdio-64
option does is force configure to skip all the checking and use the
default configuration. Mainly the commandline options would be used
as "--without-unix-stdio-64" in cases where it should be avoided even
if detected as legal by configure. 

Best regards,

-- 
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up | Frank Warmerdam, warmerdam at p...
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush | Geospatial Programmer for Rent