<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=windows-1256">
<meta content="text/html; charset=utf-8">
</head>
<body>
<div>
<div style="font-family:Calibri,sans-serif; font-size:11pt">And unfortunately, a lot of that work may need to be redone for 3.5 and VC14... Sorry about that, but once the other compilers have caught up with the new CRT interface then it will (should) all be
better in the long run.<br>
<br>
Cheers,<br>
Steve<br>
<br>
Top-posted from my Windows Phone</div>
</div>
<div dir="ltr">
<hr>
<span style="font-family:Calibri,sans-serif; font-size:11pt; font-weight:bold">From:
</span><span style="font-family:Calibri,sans-serif; font-size:11pt"><a href="mailto:njs@pobox.com">Nathaniel Smith</a></span><br>
<span style="font-family:Calibri,sans-serif; font-size:11pt; font-weight:bold">Sent:
</span><span style="font-family:Calibri,sans-serif; font-size:11pt">ý3/ý18/ý2015 10:31</span><br>
<span style="font-family:Calibri,sans-serif; font-size:11pt; font-weight:bold">To:
</span><span style="font-family:Calibri,sans-serif; font-size:11pt"><a href="mailto:techtonik@gmail.com">anatoly techtonik</a></span><br>
<span style="font-family:Calibri,sans-serif; font-size:11pt; font-weight:bold">Cc:
</span><span style="font-family:Calibri,sans-serif; font-size:11pt"><a href="mailto:python-ideas@python.org">python-ideas@python.org</a></span><br>
<span style="font-family:Calibri,sans-serif; font-size:11pt; font-weight:bold">Subject:
</span><span style="font-family:Calibri,sans-serif; font-size:11pt">Re: [Python-ideas] Rewriting the build system (part 2)</span><br>
<br>
</div>
<div>
<p dir="ltr">On Mar 18, 2015 8:14 AM, "anatoly techtonik" <<a href="mailto:techtonik@gmail.com">techtonik@gmail.com</a>> wrote:<br>
><br>
> On Mon, Mar 16, 2015 at 7:31 PM, Chris Barker <<a href="mailto:chris.barker@noaa.gov">chris.barker@noaa.gov</a>> wrote:<br>
> > On Mon, Mar 16, 2015 at 6:24 AM, anatoly techtonik <<a href="mailto:techtonik@gmail.com">techtonik@gmail.com</a>><br>
> > wrote:<br>
> >><br>
> >> "Autotools has reached the Chandrasekhar mass limit of software and<br>
> >> become a black hole of suck that consumes endless hours of bright<br>
> >> peoples’ time without any good result. It is well past time for it to<br>
> >> die." (c) "Autotools must die", ESR. <a href="http://esr.ibiblio.org/?p=1877">
http://esr.ibiblio.org/?p=1877</a><br>
> >><br>
> >> I couldn't sum up this better. It looks even worse from Windows machine.<br>
> ><br>
> > Is it even used for building Python on Windows (for the "normal" <a href="http://python.org">
python.org</a><br>
> > builds)?<br>
><br>
> There was some success with MinGW toolchain, but I am not tracking if it was<br>
> integrated into official source. The FUD was that compiled extensions are not<br>
> compatible between MSVC builds and MinGW builds, but I could not confirm<br>
> that. If I understand correctly, the incompatibility is only for C++ programs,<br>
> because of strange SEH strategy and proprietary name mangling.</p>
<p dir="ltr">This isn't FUD, alas. mingw in almost all of its variants uses effectively a different "libc" than MSVC, so code compiled with two compilers can't even agree on the meaning of file numbers. It is mostly possible to set up a mingw-w64 build that
produces MSVC-compatible extensions, but it requires using a configuration that's undocumented and untested upstream (I.e. you will run into mingw bugs). NumPy *may* switch to this at some point -- we've been working on it for like a year now -- but it's extremely
non-trivial.</p>
<p dir="ltr">-n</p>
</div>
</body>
</html>