On Fri, 17 Sep 2010 13:55:50 -0400 (EDT), "Dan Halbert"
<[email protected]> wrote:
> On Friday, September 17, 2010 4:32am, "Giovanni Bajo"
<[email protected]>
> said:
>> On Thu, 16 Sep 2010 12:30:10 -0700 (PDT), Raoul Snyman said:
>>>>> Dan Halbert said:
>>>> > Interestingly (?), my executable continues and runs fine after I
>>>> > click through the R6034 dialog box.
>>>
>>> I can confirm that I am getting the same error from trunk HEAD. I
>>> checked out revision 844 (when the 2.6 branch was merged into trunk)
>>> and built my app again with this, and it worked perfectly. I did not
>>> change anything  other than PyInstyaller between the two builds.
>> 
>> Would you mind running a bisect between r844 and the current trunk?
That
>> would surely help!
> 
> I have successfully done a bisect. No error rev 854 and before; 855 and
> after get an R6034. The only change between revs 854 and 855 is in
> bindepend.py. I did the bisect with my original program: I still don't
have
> a small test case, but I hope the diff will narrow it down:
> 
> Index: bindepend.py
> ===================================================================
> --- bindepend.py        (revision 854)
> +++ bindepend.py        (revision 855)
> @@ -502,12 +502,7 @@
>                      nm = assembly.name + fext
>                  else:
>                      nm = os.path.basename(fn)
> -                if nm.lower() == (assembly.name + ".dll").lower():
> -                    # If single DLL assembly with embedded manifest, do
> not
> -                    # create a subfolder
> -                    ftocnm = nm
> -                else:
> -                    ftocnm = os.path.join(assembly.name, nm)
> +                ftocnm = nm
>                  if assembly.language not in (None, "", "*", "neutral"):
>                      ftocnm = os.path.join(assembly.getlanguage(),
>                                            ftocnm)

Thank you very much! Can you confirm that current trunk works if you just
revert this change? 

This is the Windows 2000 compatibility change, but Florian will have to
investigate further :)

In the link that Riccardo posted in this thread, there are instructions on
how to inspect system logs to get a more useful error message and even a
trace log with full details of what the operating system is doing. Would
you please go through those instructions and provide more information?
Thanks!
-- 
Giovanni Bajo   ::  [email protected]
Develer S.r.l.  ::  http://www.develer.com

My Blog: http://giovanni.bajo.it

-- 
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