[SciPy-user] issues with distributing Numeric separately on windows
eric at scipy.org
Fri Apr 5 10:03:43 CST 2002
Well, Travis O. knows Numeric inside-out and found a solution that puts the
whole question to rest. It turns out only a few functions were calling from
Numeric extensions into fastumath. Travis just copied these over to fastumath
and now everything works fine no matter how Numeric was compiled.
So, it looks like Numeric doesn't have to be bundled with SciPy on any platform
Thanks Travis. One down, several to go.
----- Original Message -----
From: "eric" <eric at scipy.org>
To: <scipy-dev at scipy.org>; <scipy-user at scipy.org>
Sent: Thursday, April 04, 2002 3:25 PM
Subject: [SciPy-user] issues with distributing Numeric separately on windows
> When upgrading to Python2.2 I re-discovered a windows specific issue that
> O. and I fought with before releasing SciPy-0.1. It has to do with Numeric
> fastumath. These guys work very closely together.
> On windows, the pre-compiled binaries available from source-forge are compiled
> with MSVC compiler. SciPy, and hence fastumath, is compiled with gcc. This
> works fine except for calls from Numeric C extensions into the C code of
> fastumath that return complex numbers. There is a binary incompatibility
> between MSVC and gcc in their structure layout that results in segmentation
> faults on complex number operations. So:
> >>> from scipy_base import *
> >>> array(1+1j)/1.
> will cause a seg fault if you use the standard Numeric module with SciPy.
> Some people balked when SciPy was distributed with Numeric last time. We've
> endeavored to separate things out this time so that that wasn't necessary.
> However, this is pretty much a show stopper on windows -- and was major reason
> we bundled them last time. I think we'll have to distribute a gcc compiled
> version of Numeric with SciPy on windows. This will get installed over (will
> clobber) your old installation of Numeric in the process. It does not affect
> Numeric's other than making it version 21.0. By this I mean, the gcc and MSVC
> versions will work identically and work with all your extension modules.
> If anyone has run into the binary incompatibility issue before and discovered
> solution, I'd love to here it. I found the --native-struct flag for mingw,
> it didn't seem to help. One other solution is to get SciPy working with MSVC.
> I think it might be possible (though there are some big issues), but it isn't
> high priority.
> So, let me know if you have a solution,
> Eric Jones <eric at enthought.com>
> Enthought, Inc. [www.enthought.com and www.scipy.org]
> (512) 536-1057
> SciPy-user mailing list
> SciPy-user at scipy.net
More information about the SciPy-user