I'm a novice at git, so I'll spell out what I did in case I screwed it up:

git init
git clone git://github.com/pyinstaller/pyinstaller.git
git fetch git://github.com/pyinstaller/pyinstaller.git
git checkout d9b704e08e2

Ran pyinstaller and got ERROR: could not find TCL/TK

git checkout 2cf1972b9

Ran pyinstaller and got ERROR: could not find TCL/TK

Next I went to the old version of my program, the one that builds fine with 
v1.5.1.  I get the same errors with both versions as above *in 64-bit*, but if 
I run in 32-bit, d9b704e08e2 works and 2cf1972b9 fails.

git bisect start
git bisect bad 2cf1972b9
git bisect good d9b704e08e2
Bisecting: 5 revisions left to test after this (roughly 3 steps)
[72875a36453d9ff00e8cb46210db96aa9463ea7d] Yet unused TkPKG and TkTree throw 
error if used.

I tested this version in 32 bit and it fails.

git bisect bad
Bisecting: 2 revisions left to test after this (roughly 1 step)
[b24adc13eb454a59f6f4aee222cde197c7e32fbe] Replace useTK.py by a normal 
runtime-hook.

This one fails.

git bisect bad
Bisecting: 0 revisions left to test after this (roughly 0 steps)
[2411de16d11918787abc4a96135d5dbfbb03c4c9] Eliminate useless tcl/tk 
version-number from dist-data-dir.

This one fails, which I guess makes it the culprit in 32-bit.  
 
Finally, I went back to my current program and tried it with d9b704e0802 in 
32-bit mode, but it still generates the TCL/TK error.   


On Mar 15, 2012, at 2:13 AM, Hartmut Goebel wrote:

> Am 15.03.2012 01:11, schrieb Lynn Oliver:
>> 
>> A little more info.  Pyinstaller-1.5.1 works with a framework build and does 
>> not include the file hook-_tkinter.py. 
> 
> hook-_tkinter was introduced *after* 1.5.1. We removed the "special" handling 
> of Tcl/Tk and made it normla hooks like any other modules, too.
> 
> Please test the following:
> 
> - Check out [d9b704e08e2] (2012-01-01 14:51:47), this should work for you, as 
> this still uses the code like in 1.5.1
> - Then check out [2cf1972b9] (2012-01-21 15:22:30), which is the end of the 
> change-series. This should not work.
> 
> Then please use git bisect to track down the change introducing the error:
> git bisect start
> git bisect bad 2cf1972b9
> git bisect good d9b704e08e2
> 
> Please see the man-page of git-bisect for more information.
> 
> If 2cf1972b9 is working, the error is caused somewhere else. In this case, 
> the git bisect sequence should look like
> git bisect start
> git bisect good d9b704e08e2
> git bisect bad HEAD
> 
> HTH
> -- 
> Schönen Gruß - Regards
> Hartmut Goebel
> Dipl.-Informatiker (univ.), CISSP, CSSLP
> 
> Goebel Consult 
> Spezialist für IT-Sicherheit in komplexen Umgebungen
> http://www.goebel-consult.de
> 
> Monatliche Kolumne: http://www.cissp-gefluester.de/
> Goebel Consult ist Mitglied bei http://www.7-it.de

-- 
You received this message because you are subscribed to the Google Groups 
"PyInstaller" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/pyinstaller?hl=en.

Reply via email to