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