[GRASS5] 5.0.0pre1 on mac osx

[andy agena]

Hi Malcom:

> Sorry. I wasn't clear here.  In /usr/X11R6/include you should do 'grep
> ErrorFunction *.h'  This should find out if the ErrorFunction symbols 
> are
> redefined.  Also, do 'grep Xdebug *.h'.

[localhost:X11r6/include/x11] root# grep ErrorFunction *.h
Xlibint.h:extern int (*_XIOErrorFunction)(
Xlibint.h:extern int (*_XErrorFunction)(
[localhost:X11r6/include/x11] root# grep Xdebug *.h
Xlib.h:#define _Xdebug (*_Xdebug_p)
Xlib.h:extern int _Xdebug;

> These results seem strange.  The symbols that ld can't find should be 
> coming from
> here.  The XDRIVER code doesn't call these routines, or define the 
> variables, so
> they must be in the header files in /usr/X11R6/include and in libraries 
> that are
> being used.  Hopefully the grep (above) will find out how they are 
> declared.
> These symbols should be in libX11.a, but perhaps they are defined 
> differently
> through the include files.  I was expecting to see that they only had 
> one leading
> underscore, rather than 2.  We can do the same thing a different way.
>
> Check to see if your system has the nm utility.  Do 'nm -s libX11.a'.  
> This
> should produce a lot of output on the symbols.  To use this, I pipe to 
> less like
> 'nm -s libX11.a | less'. Then you can find the string, using the find 
> operator in
> less (/).  Once in less do '/ErrorFunction'.  This should find the
> __XIOErrorFunction and __XErrorFunction symbols.  Or you can pipe to 
> grep like
> 'nm -s libX11.a | grep ErrorFunction'.
>
> You can do the same thing with libXext.a.

my nm wants:

Usage: nm [-agnoprumxjl[s segname sectname] [-] [[-arch 
<arch_flag>] ...] [file ...]

and I wasn't sure what i need to put in for "setname sectname" so I just 
used -a:

[localhost:/usr/x11r6/lib] root# nm -a libX11.a | grep ErrorFuntion
nm: no name list
nm: no name list
nm: no name list
[localhost:/usr/x11r6/lib] root# nm -a libXext.a | grep ErrorFunction
00000004 C __XExtensionErrorFunction
          U __XExtensionErrorFunction

> Tiff and png are probably OK, but to be safe, you could add 
> -I/usr/local/include
> to the include files (INC or INCPATH) and -L/usr/local/lib to the 
> library lines
> (LIB and LIBPATH), like this:
>
> #Image formats:
> PNGINC              =  -I/usr/local/include -I/usr/include
> PNGLIB              = -L/usr/local/lib  -L/usr/lib
>
> TIFFINCPATH         = -I/usr/local/include
> TIFFLIBPATH         = -L/usr/local/lib
>
> Check to see that the header files are in /usr/local/include.  You 
> should find
> tiff.h and png.h there, these are the include (or header) files.  Once 
> you get
> the *.h files from Jeshua, you can do the same for the TCL/TK lines.

Jeshua can't get to his *.h for a few days, so I'm trying to find the 
tcl/tk source, and one of pages I found 
<http://dev.scriptics.com/software/tcltk/downloadnow83.html> keeps 
timing out when I attempt to download.

> Did the tcltkgrass menu's start up here?  This should start the GUI.  
> You will
> know when it starts.

tcltkgrass did start here--and at times I can be an idiot:  I didn't 
even see the menu until I maximized my vnc window.

Thanks,
Andy

---------------------------------------- 
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo at geog.uni-hannover.de with
subject 'unsubscribe grass5'