I've managed to build HDF4.2r0 into gdal-1.1.9 so that I can build GRASS 5.3
with gdal support for importing ASTER images.
I'm having a little trouble running ./configure ...
When I run the script without arguments I get the jpeg libraries and get the
following results:
checking whether to use JPEG... yes
checking for location of JPEG includes...
checking for jpeglib.h... no
configure: error: *** Unable to locate JPEG includes.
$
if I started to explicity include the include/lib directories like
./configure --with-jpeg-includes=/usr/local/include --with-jpeg-libs=/usr/lo
cal/lib
I get to the next header/lib in the configuration process (tiff/png?) and
get the same results, I've started to explicity define all the include/lib
paths and realized these are all default paths on my machine and every other
time I've simply run ./configure I get a decent makefile (without odbc,
fftw, etc)
When I used the prefix or includedir/libdir I still get the same results.
Am I doing something wrong or is this a OS-specific problem.
Thanks,
Jeff.
---
Jeff D. Hamann
Forest Informatics, Inc.
PO Box 1421
Corvallis, Oregon USA 97339-1421
(office) 541-754-1428
(cell) 541-740-5988
jeff.hamann@forestinformatics.com
www.forestinformatics.com
Jeff D. Hamann wrote:
I've managed to build HDF4.2r0 into gdal-1.1.9 so that I can build GRASS 5.3
with gdal support for importing ASTER images.
I'm having a little trouble running ./configure ...
When I run the script without arguments I get the jpeg libraries and get the
following results:
checking whether to use JPEG... yes
checking for location of JPEG includes...
checking for jpeglib.h... no
configure: error: *** Unable to locate JPEG includes.
$
if I started to explicity include the include/lib directories like
./configure --with-jpeg-includes=/usr/local/include --with-jpeg-libs=/usr/lo
cal/lib
I get to the next header/lib in the configuration process (tiff/png?) and
get the same results, I've started to explicity define all the include/lib
paths and realized these are all default paths on my machine and every other
time I've simply run ./configure I get a decent makefile (without odbc,
fftw, etc)
Using:
--with-includes=/usr/local/include --with-libs=/usr/local/lib
will cause those directories to be checked automatically for every
header or library. However: it will also cause them to be checked
*before* /usr/include and /usr/lib, which may not be what you want.
When I used the prefix or includedir/libdir I still get the same results.
Those directories control where the project's (i.e. GRASS') components
are installed, not where it looks for existing dependencies (however,
only --prefix and --bindir are actually used by GRASS).
Am I doing something wrong or is this a OS-specific problem.
A mixture. On one hand, using --with-includes and --with-libs would
probably solve most of your problems. On the other hand, this wouldn't
be an issue if the compiler/linker used /usr/local/{include,lib}
automatically (as is the case for gcc on Linux).
--
Glynn Clements <glynn.clements@virgin.net>