On Tuesday 04 August 2009, John Hunter wrote:
Very odd. I suggest opening up setupext.py and finding the
function check_for_tk. There are a series of test which
ultimately set the gotit variable to determine whether you have
tk for building. Insert a lot of debug print statements throughout
Using the latest SVN matplotlib, the TkAgg backed does not get built
even though all the libraries are installed (Linux 64-bit). The
following error message occurs during the build:
Tkinter: no
* Using default library and include directories for
* Tcl and Tk because a Tk
On Tue, Aug 4, 2009 at 3:52 AM, Johann Rohwerj...@sun.ac.za wrote:
Using the latest SVN matplotlib, the TkAgg backed does not get built
even though all the libraries are installed (Linux 64-bit). The
following error message occurs during the build:
Tkinter: no
* Using default library
On Tue, Aug 4, 2009 at 3:52 AM, Johann Rohwerj...@sun.ac.za wrote:
Using the latest SVN matplotlib, the TkAgg backed does not get built
even though all the libraries are installed (Linux 64-bit). The
following error message occurs during the build:
Tkinter: no
* Using default library
On Tuesday 04 August 2009, John Hunter wrote:
On Tue, Aug 4, 2009 at 3:52 AM, Johann Rohwerj...@sun.ac.za wrote:
Using the latest SVN matplotlib, the TkAgg backed does not get
built even though all the libraries are installed (Linux 64-bit).
The following error message occurs during the
On Tue, Aug 4, 2009 at 9:14 AM, Johann Rohwerj...@sun.ac.za wrote:
Type help, copyright, credits or license for more information.
import Tkinter
a=Tkinter.tkinter.create()
which creates a tk window on my desktop.
So really in the dark what's going on here
Very odd. I suggest opening
What distro are you on? It seems that Tcl/Tk moves the header files
around on a regular basis while not providing a standard way to
determine their location. It's like a wild goose chase ;) Perhaps
you're running something new and blazing new territory here ;)
Mike
John Hunter wrote:
On
