compile python witout tkinter

[Gerhard Häring]

* kosh at aesaeion.com <kosh at aesaeion.com> [2002-06-21 01:55 -0600]:
> On Fri, 21 Jun 2002, Gerhard [iso-8859-15] Häring wrote:
> 
> > * kosh at aesaeion.com <kosh at aesaeion.com> [2002-06-21 01:40 -0600]:
> > > On Fri, 21 Jun 2002, Gerhard [iso-8859-15] Häring wrote:
> > >
> > > > * kosh at aesaeion.com <kosh at aesaeion.com> [2002-06-21 01:26 -0600]:
> > > > > On a machine I need to build python on I need to build it without tkinter.
> > > >
> > > > Why? Even if Tkinter gets compiled, it doesn't change anything for the
> > > > rest. You could even delete the tkinter modules afterwards, if you're
> > > > short on disk (quota).
> > >
> > > Because the libraries it depends on are not installed on that machine and
> > > there is no point installing them since they are not needed.
> >
> > No problem, then. It won't get built if the dependencies are not met.
> > As seen in Modules/Setup.
> 
> The problem is that it is trying to build it ayways. All the tkinter lines
> in Modules/Setup that I can find are commented out but it doesn't seem to
> have done any good.

It looks like in Python 2.1.3, Tkinter gets built with distutils in
Python's setup.py. I fear I don't have a solution to your problem, as
detect_tkinter in Python 2.1.3's setup.py looks fine to me. Maybe you
have a very strange or broken Tcl/Tk setup on your machine. As a
temporary workaround, you could try to insert a return right at the
beginning of detect_tkinter in Python's setup.py.

I sincerly hope some Tkinter expert here can come up with a better
solution and help finding the real reason behind this.

Gerhard
-- 
This sig powered by Python!
Außentemperatur in München: 24.5 °C      Wind: 2.1 m/s