On 9/23/16 08:18, Hartmut Goebel wrote:
Am 23.09.2016 um 17:13 schrieb Coyot Linden (Glenn Glazer):
$ ls -l
C:\\Users\\coyot\\AppData\\Roaming\\pyinstaller\\bincache00_py27_32bit\\unicodedata.pyd
-rwxr-xr-x 1 coyot None 688640 Sep 23 07:41
'C:\Users\coyot\AppData\Roaming\pyinstaller\bincache00_py27_32bit\unicodedata.pyd'
Sure this is the same user? This `ls -l` seems to be a cygwin bash
commands, while PyInstaller seems to be run via cmd.exe. BTW: the
group is "None".
Anyway, you may try running pyinstaller --clean.
cmd.exe understands some unix-style commands these days:
C:\Users\coyot> ls -l
C:\\Users\\coyot\\AppData\\Roaming\\pyinstaller\\bincache00_py27_32bit\\unicodedata.pyd
-rwxr-xr-x 1 coyot None 688640 Sep 23 08:18
'C:\\Users\\coyot\\AppData\\Roaming\\pyinstaller\\bincache00_py27_32bit\\unicodedata.pyd'
But yes, I think this is the source of the problem, many thanks. I just
re-ran the build not from cygwin but from cmd.exe and it succeeded
without either this or the access by another program error.
I think I need to have a discussion with our build team. I do sort of
wonder why many builds before this succeeded in cygwin.
Thanks again,
coyot
--
You received this message because you are subscribed to the Google Groups
"PyInstaller" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/pyinstaller.
For more options, visit https://groups.google.com/d/optout.
