Hi,

numpy, scipy test binaries (32 bit, openblas) can be downloaded from
https://code.google.com/p/mingw-w64-static/ .
link:
https://drive.google.com/file/d/0B4DmELLTwYmlc2tjMkpwUDF5cDg/edit?usp=sharing

log-files:
https://gist.github.com/anonymous/7457182

Regards

Carl


2013/11/13 Carl Kleffner <cmkleff...@gmail.com>

> Hi,
>
> yes it also works for scipy. I didn't patch the scipy source other than
> creating site.cfg with the path to openblas.I will upload the binaries and
> logs later today.
>
> Regards
>
> Carl
>
> scipy.test(verbose=2) runs without segfault:
>
> ...
>
> ======================================================================
> FAIL: Tests for the minimize wrapper.
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>   File "d:\devel32\WinPy2753\python-2.7.5\lib\site-packages\nose\case.py",
> line 197, in runTest
>     self.test(*self.arg)
>   File
> "d:\devel32\WinPy2753\python-2.7.5\lib\site-packages\scipy\optimize\tests\test_optimize.py",
> line 435, in test_minimize
>     self.test_powell(True)
>   File
> "d:\devel32\WinPy2753\python-2.7.5\lib\site-packages\scipy\optimize\tests\test_optimize.py",
> line 209, in test_powell
>     atol=1e-14, rtol=1e-7)
>   File
> "d:\devel32\WinPy2753\python-2.7.5\lib\site-packages\numpy\testing\utils.py",
> line 1181, in assert_allclose
>     verbose=verbose, header=header)
>   File
> "d:\devel32\WinPy2753\python-2.7.5\lib\site-packages\numpy\testing\utils.py",
> line 644, in assert_array_compare
>     raise AssertionError(msg)
> AssertionError:
> Not equal to tolerance rtol=1e-07, atol=1e-14
>
> (mismatch 100.0%)
>  x: array([[ 0.75077639, -0.44156936,  0.47100962],
>        [ 0.75077639, -0.44156936,  0.48052496],
>        [ 1.50155279, -0.88313872,  0.95153458],...
>  y: array([[ 0.72949016, -0.44156936,  0.47100962],
>        [ 0.72949016, -0.44156936,  0.48052496],
>        [ 1.45898031, -0.88313872,  0.95153458],...
>
> ======================================================================
> FAIL: Powell (direction set) optimization routine
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>   File "d:\devel32\WinPy2753\python-2.7.5\lib\site-packages\nose\case.py",
> line 197, in runTest
>     self.test(*self.arg)
>   File
> "d:\devel32\WinPy2753\python-2.7.5\lib\site-packages\scipy\optimize\tests\test_optimize.py",
> line 209, in test_powell
>     atol=1e-14, rtol=1e-7)
>   File
> "d:\devel32\WinPy2753\python-2.7.5\lib\site-packages\numpy\testing\utils.py",
> line 1181, in assert_allclose
>     verbose=verbose, header=header)
>   File
> "d:\devel32\WinPy2753\python-2.7.5\lib\site-packages\numpy\testing\utils.py",
> line 644, in assert_array_compare
>     raise AssertionError(msg)
> AssertionError:
> Not equal to tolerance rtol=1e-07, atol=1e-14
>
> (mismatch 100.0%)
>  x: array([[ 0.75077639, -0.44156936,  0.47100962],
>        [ 0.75077639, -0.44156936,  0.48052496],
>        [ 1.50155279, -0.88313872,  0.95153458],...
>  y: array([[ 0.72949016, -0.44156936,  0.47100962],
>        [ 0.72949016, -0.44156936,  0.48052496],
>        [ 1.45898031, -0.88313872,  0.95153458],...
>
> ======================================================================
> FAIL: Test that bode() doesn't fail on a system with a pole at 0.
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>   File "d:\devel32\WinPy2753\python-2.7.5\lib\site-packages\nose\case.py",
> line 197, in runTest
>     self.test(*self.arg)
>   File
> "d:\devel32\WinPy2753\python-2.7.5\lib\site-packages\scipy\signal\tests\test_ltisys.py",
> line 346, in test_06
>     assert_equal(w[0], 0.01)  # a fail would give not-a-number
>   File
> "d:\devel32\WinPy2753\python-2.7.5\lib\site-packages\numpy\testing\utils.py",
> line 317, in assert_equal
>     raise AssertionError(msg)
> AssertionError:
> Items are not equal:
>  ACTUAL: 0.010000000000000002
>  DESIRED: 0.01
>
> ======================================================================
> FAIL: test_ltisys.Test_freqresp.test_pole_zero
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>   File "d:\devel32\WinPy2753\python-2.7.5\lib\site-packages\nose\case.py",
> line 197, in runTest
>     self.test(*self.arg)
>   File
> "d:\devel32\WinPy2753\python-2.7.5\lib\site-packages\scipy\signal\tests\test_ltisys.py",
> line 437, in test_pole_zero
>     assert_equal(w[0], 0.01)  # a fail would give not-a-number
>   File
> "d:\devel32\WinPy2753\python-2.7.5\lib\site-packages\numpy\testing\utils.py",
> line 317, in assert_equal
>     raise AssertionError(msg)
> AssertionError:
> Items are not equal:
>  ACTUAL: 0.010000000000000002
>  DESIRED: 0.01
>
> ----------------------------------------------------------------------
> Ran 8937 tests in 173.925s
>
> FAILED (KNOWNFAIL=114, SKIP=213, failures=4)
> Running unit tests for scipy
> NumPy version 1.8.0
> NumPy is installed in
> d:\devel32\WinPy2753\python-2.7.5\lib\site-packages\numpy
> SciPy version 0.13.0
> SciPy is installed in
> d:\devel32\WinPy2753\python-2.7.5\lib\site-packages\scipy
> Python version 2.7.5 (default, May 15 2013, 22:43:36) [MSC v.1500 32 bit
> (Intel)]
> nose version 1.3.0
>
>
>
>
> 2013/11/12 David Cournapeau <courn...@gmail.com>
>
>>
>>
>>
>> On Mon, Nov 11, 2013 at 1:32 PM, Carl Kleffner <cmkleff...@gmail.com>wrote:
>>
>>> Hi David,
>>>
>>> i used my customized mingw-w64 toolkit mentioned in this thread to
>>> circumvent several problems with the mixed compiler enviroment. It is a
>>> fully statically gcc build. Hence the compiled executables and dlls never
>>> depend on mingw dlls even without usage of -static -static-libgcc ...
>>> compiler options. The crt runtime is msvcr90.dll as used by python-2.7. The
>>> manifest is linked to the executables per default. I have to write some
>>> documentation about that, but this may take some time due to my workload.
>>>
>>
>> Hm, interesting, I did not even know this was possible !
>>
>> Does that work for scipy as well ? I am a bit worried about using custom
>> toolchains, OTOH, that's the only real solution we seem to have ATM.
>>
>> David
>>
>>>
>>> You can test it on a windows cmd prompt with:  objdump -p
>>> numpy\core\_dotblas.pyd | findstr DLL
>>>         DLL
>>>  vma:            Hint    Time      Forward  DLL       First
>>>         DLL Name: ADVAPI32.dll
>>>         DLL Name: KERNEL32.dll
>>>         DLL Name: msvcr90.dll
>>>         DLL Name: python27.dll
>>>
>>> Carl
>>>
>>>
>>> 2013/11/11 David Cournapeau <courn...@gmail.com>
>>>
>>>>
>>>>
>>>>
>>>> On Mon, Nov 11, 2013 at 10:28 AM, Carl Kleffner 
>>>> <cmkleff...@gmail.com>wrote:
>>>>
>>>>> done
>>>>>
>>>>> all logs in https://gist.github.com/anonymous/7411039
>>>>>
>>>>
>>>> Thanks. Looking at the log, it does not look like you are statically
>>>> linking the mingw runtimes, though. I would expect numpy not to work if you
>>>> don't have mingw dlls in your %PATH%, right ?
>>>>
>>>> David
>>>>
>>>>>
>>>>>
>>>>> Regards Carl
>>>>>
>>>>>
>>>>> 2013/11/11 David Cournapeau <courn...@gmail.com>
>>>>>
>>>>>> Carl,
>>>>>>
>>>>>> It looks like the google drive contains the binary and not the actual
>>>>>> log ? For the log, it is more convenient to put it on gist.github.com
>>>>>> ,
>>>>>>
>>>>>> thanks for the work,
>>>>>> David
>>>>>>
>>>>>>
>>>>>> On Mon, Nov 11, 2013 at 9:51 AM, Carl Kleffner 
>>>>>> <cmkleff...@gmail.com>wrote:
>>>>>>
>>>>>>> Hi David,
>>>>>>>
>>>>>>> I made a new build with the numpy-1.8.0 code base. binaries and logs
>>>>>>> are included in the following archive:
>>>>>>>
>>>>>>> 2013-11-11_i686-numpy-1.8.0-py27-openblastest.7z<https://drive.google.com/file/d/0B4DmELLTwYmlajBzZFpXcVYycEE/edit?usp=sharing>
>>>>>>> https://drive.google.com/file/d/0B4DmELLTwYmlajBzZFpXcVYycEE/edit?usp=sharing
>>>>>>>
>>>>>>> Regards
>>>>>>>
>>>>>>> Carl
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> 2013/11/8 David Cournapeau <courn...@gmail.com>
>>>>>>>
>>>>>>>> Hi Carl,
>>>>>>>>
>>>>>>>> Thanks for that. I am a bit confused by the build log
>>>>>>>> https://drive.google.com/file/d/0B4DmELLTwYmlRTRlOHpJbjdmbTQ/edit?usp=sharing,
>>>>>>>> in particular the failures for lapack_lite and umath.
>>>>>>>>
>>>>>>>> May we ask you to put the logs on gists.github.com ? google docs
>>>>>>>> is rather painful to use for logs (no line number, etc...)
>>>>>>>>
>>>>>>>> thanks,
>>>>>>>> David
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Fri, Nov 8, 2013 at 7:42 AM, Carl Kleffner <cmkleff...@gmail.com
>>>>>>>> > wrote:
>>>>>>>>
>>>>>>>>> Hi list,
>>>>>>>>>
>>>>>>>>> I created a repository at google code
>>>>>>>>> https://code.google.com/p/mingw-w64-static with some downloads as
>>>>>>>>> well as my last numpy setp.py log.
>>>>>>>>>
>>>>>>>>> Regards
>>>>>>>>>
>>>>>>>>> Carl
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> NumPy-Discussion mailing list
>>>>>>>>> NumPy-Discussion@scipy.org
>>>>>>>>> http://mail.scipy.org/mailman/listinfo/numpy-discussion
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> NumPy-Discussion mailing list
>>>>>>>> NumPy-Discussion@scipy.org
>>>>>>>> http://mail.scipy.org/mailman/listinfo/numpy-discussion
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> NumPy-Discussion mailing list
>>>>>>> NumPy-Discussion@scipy.org
>>>>>>> http://mail.scipy.org/mailman/listinfo/numpy-discussion
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> NumPy-Discussion mailing list
>>>>>> NumPy-Discussion@scipy.org
>>>>>> http://mail.scipy.org/mailman/listinfo/numpy-discussion
>>>>>>
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> NumPy-Discussion mailing list
>>>>> NumPy-Discussion@scipy.org
>>>>> http://mail.scipy.org/mailman/listinfo/numpy-discussion
>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> NumPy-Discussion mailing list
>>>> NumPy-Discussion@scipy.org
>>>> http://mail.scipy.org/mailman/listinfo/numpy-discussion
>>>>
>>>>
>>>
>>> _______________________________________________
>>> NumPy-Discussion mailing list
>>> NumPy-Discussion@scipy.org
>>> http://mail.scipy.org/mailman/listinfo/numpy-discussion
>>>
>>>
>>
>> _______________________________________________
>> NumPy-Discussion mailing list
>> NumPy-Discussion@scipy.org
>> http://mail.scipy.org/mailman/listinfo/numpy-discussion
>>
>>
>
_______________________________________________
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion

Reply via email to