[GRASSLIST:1735] Re: configure problems on OSX

Giacomo giacomo.bertoldi at ing.unitn.it
Wed Nov 12 14:29:19 EST 2003


This is my configure file, for a MacX powerbook. You must check where 
are your libraries, and if you do not find some libraries install they 
by source using for example Fink Commander.

I hope this helps. Giacomo

./configure --prefix=/sw/share \
--with-postgres-includes=/usr/local/pgsql/include \
--with-postgres-libs=/usr/local/pgsql/lib \
--with-includes=/sw/include \
--with-libs=/sw/lib \
--with-tiff-includes=/sw/include \
--with-tiff-libs=/sw/lib \
--with-tcltk-includes=/sw/include \
--with-proj \
--with-tcltk-libs=/sw/lib/tcl8.4 \
--with-gd-includes=/sw/include \
--with-opengl-includes=/usr/X11R6/include \
--with-fftw-includes=/sw/include \
--with-gdal=/usr/local/bin/gdal-config \
--without-odbc




On Lunedì, nov 10, 2003, at 13:43 US/Pacific, Glynn Clements wrote:

>
> Kirk R. Wythers wrote:
>
>>> Look at the config.log file. Specifically, search for the text
>>> "checking for jpeg_start_compress". Any error messages will follow
>>> shortly afterwards.
>>
>> I'm not seeing any reference to "checking for jpeg_start_includes".
>> Here is the error log...
>
> 	configure:5503: checking for jpeg_start_compress in -ljpeg
> 	configure:5520: gcc -o conftest -g -O2     conftest.c -ljpeg   1>&5
> 	ld: can't locate file for: -ljpeg
> 	configure: failed program was:
> 	[snipped]
> 	configure:5539: checking for jpeg_start_compress in -ljpeg
> 	configure:5556: gcc -o conftest -g -O2     conftest.c -ljpeg  -lz   
> 1>&5
> 	ld: can't locate file for: -ljpeg
> 	configure: failed program was:
> 	[snipped]
>
> OK; it really is failing because it can't find the JPEG library
> (library failures are often more involved, e.g. a library may need
> other libraries which can't be found).
>
> You probably need something like:
>
> 	--with-jpeg-libs=/sw/lib
>
> The file in question will probably be called libjpeg.a or
> libjpeg.dylib; you need to specify the directory in which that file
> resides.
>
> If a lot of the external dependencies are in /sw/include and /sw/lib,
> it may be better to just use e.g.:
>
> 	--with-includes=/sw/include --with-libs=/sw/lib
>
> so that those directories are searched for every dependency.
>
> -- 
> Glynn Clements <glynn.clements at virgin.net>
>
>




More information about the grass-user mailing list