py2exe

Brad McRae wrote:

> About 10% of Windows users get errors in two modules:
> numpy.core._dotblas.pyd
> and
> scipy.linalg.flapack.pyd

Are you able to test an un-py2exe'd version of your program on any of the
machines that crash the app?

Ahh - I didn't have a problem with 2 VMWare'd XP machines, but my laptop
just blew up in core._dotblas as I was composing this email (different
offset).  I'll look into this further when I get some free bandwidth
(not in the next 24 hours).

Cheers.


-- 
Regards,
  Daryl Tester

"Scheme is an exotic sports car. Fast. Manual transmission. No radio.
 Common Lisp is Howl's Moving Castle."
  -- Steve Yegge, comparing Lisp families to cars.

> -----Original Message-----
> From: Brad McRae [mailto:bmcrae@...] 
> Sent: 18 October 2009 16:08
> To: py2exe-users@...
> Subject: [Py2exe-users] Numpy problems with py2exe
> 
> We're experiencing a strange error with a python program compiled with
> py2exe.
> 
> It only affects a minority Windows machines, with no apparent 
> pattern of
> Windows version or build (the error occurs in both 32-bit XP 
> and Vista). If
> we compile on a machine it runs on that machine.  But no 
> single compilation
> will run on all machines, which is what we need to release 
> our software.
> 
> About 10% of Windows users get errors in two modules:
> numpy.core._dotblas.pyd
> and
> scipy.linalg.flapack.pyd
> 
> Here are what the windows error signatures look like:
> 
> AppName: cs_gui.exe      AppVer: 3.1.0.0         ModName:
> numpy.core._dotblas.pyd    ModVer: 0.0.0.0     Offset: 00064a95
> 
> AppName: cs_gui.exe      AppVer: 3.1.0.0         ModName:
> scipy.linalg.flapack.pyd     ModVer: 0.0.0.0      Offset: 00459e7b
> 
> Here is our program:
> http://www.circuitscape.org/Circuitscape/Windows.html
> 
> Can anybody help us determine what is causing our compiled 
> code to run on
> some machines and not others?
> 
> Thanks!
> Brad
> 

I had a problem with numpy in py2exe not working on certain computers. I can't remember the exact details, but the computers that failed all had older CPUs that didn't support the SSE instructions that numpy was trying to use.

I think numpy detects the instruction sets supported by your CPU when it is compiled. The resulting binary may not run on older computers that don't support those instructions. I ended up using the numpy 1.0.4 binaries from Sourceforge, which seemed to be built without SSE support.

Here's an example of someone else having the same problem:

http://www.mail-archive.com/numpy-discussion@...>

Hope that helps,

Simon

It looks like this has fixed our problem!  Our code was breaking on
computers that had CPU's without SSE3 support.  We now install Numpy
and Scipy with the /arch nosse option and this has fixed the error on
the computers we've tested.

Many thanks to Simon and Zach for pointing me in the right direction.

-Brad


On Mon, Oct 19, 2009 at 2:06 AM, King Simon-NFHD78 wrote:
>> -----Original Message-----
>> From: Brad McRae [mailto:bmcrae@...]
>> Sent: 18 October 2009 16:08
>> To: py2exe-users@...
>> Subject: [Py2exe-users] Numpy problems with py2exe
>>
>> We're experiencing a strange error with a python program compiled with
>> py2exe.
>>
>> It only affects a minority Windows machines, with no apparent
>> pattern of
>> Windows version or build (the error occurs in both 32-bit XP
>> and Vista). If
>> we compile on a machine it runs on that machine.  But no
>> single compilation
>> will run on all machines, which is what we need to release
>> our software.
>>
>> About 10% of Windows users get errors in two modules:
>> numpy.core._dotblas.pyd
>> and
>> scipy.linalg.flapack.pyd
>>
>> Here are what the windows error signatures look like:
>>
>> AppName: cs_gui.exe      AppVer: 3.1.0.0         ModName:
>> numpy.core._dotblas.pyd    ModVer: 0.0.0.0     Offset: 00064a95
>>
>> AppName: cs_gui.exe      AppVer: 3.1.0.0         ModName:
>> scipy.linalg.flapack.pyd     ModVer: 0.0.0.0      Offset: 00459e7b
>>
>> Here is our program:
>> http://www.circuitscape.org/Circuitscape/Windows.html
>>
>> Can anybody help us determine what is causing our compiled
>> code to run on
>> some machines and not others?
>>
>> Thanks!
>> Brad
>>
>
> I had a problem with numpy in py2exe not working on certain computers. I can't remember the exact details, but the computers that failed all had older CPUs that didn't support the SSE instructions that numpy was trying to use.
>
> I think numpy detects the instruction sets supported by your CPU when it is compiled. The resulting binary may not run on older computers that don't support those instructions. I ended up using the numpy 1.0.4 binaries from Sourceforge, which seemed to be built without SSE support.
>
> Here's an example of someone else having the same problem:
>
> http://www.mail-archive.com/numpy-discussion@...>
>
> Hope that helps,
>
> Simon
>