[GRASS5] Darwin Pre2 Config Errors

Jeshua Lacock jeshua at OpenOSX.com
Fri Sep 21 19:00:35 EDT 2001


On Friday, September 21, 2001, at 07:17  AM, Glynn Clements wrote:

>>
>>> checking for location of PNG includes... /usr/local/include
>>> checking for png.h... yes
>>> checking for location of PNG library... /usr/local/lib
>>> checking for png_read_png in -lpng... no
>>> configure: warning: *** Unable to locate PNG library.
>
> I would need to see the config.log file to determine why this test
> fails. I can't do anything without it.

Thanks for the help Glynn and Markus!

I'm sorry, my bad, the lib just need to be ranlib'ed...

>>> checking for location of GD includes... /usr/local/include
>>> checking for gd.h... yes
>>> checking for location of GD library... /usr/local/lib
>>> checking for gdImageCreate in -lgd... no
>>> checking for gdImageCreate in -lgd... no
>>> checking for gdImageCreate in -lgd... no
>>> checking for gdImageCreate in -lgd... no
>>> configure: warning: *** Unable to locate GD library.
>
> GD often requires PNG, so this may just be a consequence of the PNG
> failure.

It got further now that PNG works, but I am getting a "Undefined 
symbols: _gdImageGif.

Here is the relevant section from the confg.log:

configure:4759: checking for location of GD includes
configure:4791: checking for gd.h
configure:4801: gcc -E -traditional-cpp  -I/usr/local/include conftest.c 
 >/dev/null 2>conftest.out
configure:4833: checking for location of GD library
configure:4862: checking for gdImageCreate in -lgd
configure:4881: gcc -o conftest -O2 -mcpu=ppc    conftest.c -lgd   1>&5
configure:5040: checking for gdImageGif
configure:5068: gcc -o conftest -O2 -mcpu=ppc    -lgd conftest.c  1>&5
/usr/bin/ld: Undefined symbols:
_gdImageGif

Does gd need to be built with GIF support or something?

>>> checking for gdImageGif... no
>>> checking for gdImagePng... no
>>> checking for location of Tcl/Tk includes... /usr/local/include/
>>> checking for tcl.h... yes
>>> checking for tk.h... no
>>> configure: warning: *** Could not find 'tk.h'.
>>
>> This one is really weird, it finds 'tcl.h' but not 'tk.h' located in 
>> the
>> same directory.
>
> Odd. This check (AC_CHECK_HEADERS) involves attempting to pre-process
> (via e.g. "cpp", "gcc -E" or similar) the following test program:
>
> 	#line 5436 "configure"
> 	#include "confdefs.h"
> 	#include <tk.h>
>
> If the check fails, but tk.h is present, this implies that
> pre-processing tk.h fails, e.g. because one of the headers which tk.h
> includes can't be found.
>
> My suspicion is that the X headers can't be found. I'll look into
> adding the appropriate -I switch(es) automatically (via X_CFLAGS). If
> I'm correct, you should be able to work around the problem using e.g.
>
> 	--with-tcltk-includes=/usr/X11R6/include
>
> Note: this option accepts a space-separated list of directories, e.g.
>
> 	--with-tcltk-includes='/usr/local/include /usr/X11R6/include'

Yes, you are correct!  Adding X11R6 to the tcltk includes fixed all the 
tcl/tk errors, thanks!

>>> configure: warning: *** Tcl/Tk version mismatch.
>>
>> Hmm, this one is new. I'm stumped.
>
> This is an artifact of the tk.h test failing.
>
>>> checking for location of Tcl/Tk libraries... /usr/local/lib
>>> checking for Tcl_Init in -ltcl... yes
>>> checking for Tk_MainWindow in -ltk... no
>>> checking for Tk_MainWindow in -ltk... no
>>> checking for Tk_MainWindow in -ltk... no
>>> checking for Tk_MainWindow in -ltk... no
>>> configure: warning: *** Unable to locate Tk library.
>
> Possibly related to X libraries, although I would need to see
> config.log to be sure.

You are correct, it's all fixed now, thanks again!

>> BTW: I have decided to skip the BLAS and LAPACK libraries for now
>> because they are Fortran.  What module(s) use them?
>
> I don't think that anything uses them at present.

OK, great thanks for the scoop..


Kind regards,

Jeshua Lacock                                http://OpenOSX.com
Programmer/Owner                     http://SierraMaps.com
Phone: (760) 935-4736            http://3dTopoMaps.com




More information about the grass-dev mailing list