[m-users.] Compiler trouble

[Sebastian Godelet]

So yes when the patch I submitted to enable compilation with VS 2015, that could be backported to the 14.01 release branch,

Alternatively one could try to use:
> If you are linking with Windows SDK 8.1 or earlier, you might encounter these unresolved external symbol errors.
> In that case, you should resolve the error by adding legacy_stdio_definitions.lib to the linker input as described previously.

So for the CL command output, add that lib and it should be worth a shot.

Cheers,

Sebastian

> -----Original Message-----
> From: Julien Fischer [mailto:jfischer at opturion.com]
> Sent: Monday, August 08, 2016 11:04
> To: Sebastian Godelet <sebastian.godelet at outlook.com>
> Cc: Noah Scott Goldman <noahsg at badmousedriver.xyz>; Julien Fischer
> <jfischer at opturion.com>; users at lists.mercurylang.org
> Subject: RE: [m-users.] Compiler trouble
> 
> 
> Hi,
> 
> On Mon, 8 Aug 2016, Sebastian Godelet wrote:
> 
> > I think this is a mismatch between the used Visual C++ compilers,
> >
> > Can you send the output of “cl”, e.g.
> >
> >
> >
> > Microsoft (R) C/C++ Optimizing Compiler Version 19.00.24213.1 for x86
> >
> > Copyright (C) Microsoft Corporation.  All rights reserved.
> 
> Microsoft have apparently re-arranged a good deal of their C runtime
> between VS2013 and VS2015.  Based on <https://msdn.microsoft.com/en-
> us/library/bb531344.aspx>, I think we would need to build a separate binary
> packages that targets versions of MSVC later than 2013.
> 
> Julien.