Re: problems building tkinter module
Thu, 09 Jun 1994 11:12:26 +0200

> 1) Since I'm linking against shared libraries for Tcl and Tk,
> tkintermodule.c must contain a symbol called "Tcl_AppInit", or the
> linker objects. Apparently this doesn't matter if you link against
> static libraries. I added the following: [...]

Thanks. I guess what happens is this. According to the docs, the
application is supposed to provide Tcl_AppInit, but since many apps
don't want to, there's a default one in the library, so Steen got away
with not defining it. However if you use shared libs, putting one in
the lib would create conflicts for those apps that do want to provide
their own, so it's not in the shared lib version. My suggestion is to
define WITH_APPINIT by default -- the only situation where this would
be inappropriate is when Python + tkinter is embedded into a Tcl app
that wants to provide its own Tcl_AppInit...

> 2) I compile python with Sun's bundled "cc", a K&R compiler. When I
> attempt to compile tkinter, I get the following warning: [...]

You mentioned a fake gcc in another message. Could it possibly be
that you switched compilers without rerunning configure and running
make clean?

> 3) The library lib.a is constructed with "ar cr lib.a...", and isn't
> ranlib'ed. This causes warnings from the SunOS linker. It should
> probably use $(AR) and $(RANLIB), or whatever the Python solution is.

That's my fault for providing a "universal" Makefile for extensions
that isn't processed by configure. I'll see if I can fix it.

--Guido van Rossum, CWI, Amsterdam <>
URL: <>