Re: autoconf + automake support for MSVC

Peter Rosin wrote: > my MSYS install seems very reliable to me The groff people have made a different experience. See -- In memoriam Sergei Tretyakov

Re: autoconf + automake support for MSVC

Peter Rosin wrote: > From time to time, I'm wondering if reusing *-*-mingw* for cl is the > right decision. I think so, yes. mingw and msvc share the same kernel, the same object file format, and large parts of the C library. But it definitely ought to be documented, because it is very non-obviou

Re: autoconf + automake support for MSVC

Den 2011-09-10 02:22 skrev Bruno Haible: > Peter Rosin wrote: >> The platform name was discussed a few years back on the libtool lists (I >> think somewhere in the gigantic thread "[patch #6448] [MSVC 7/7] Add MSVC >> Support" from August 2008 approximately) [0], the outcome was that compiling >> w

MSVC and __STDC__

The MSVC 9 compiler does not define __STDC__. And we cannot define __STDC__, because then many declarations will be hidden in the system header files. So the workaround is either to test for _MSC_VER explicitly (this is what the GNU standards recommend [1]), or to assume an ANSI C compiler outright

*printf: support for msvc

This patch adds support for the MSVC 9 platform to the *printf modules. Three things are special about this platform: - It has more *printf bugs than any other platform. - The test whether %n is supported crashes because of a "parameter validation". The crash pops up 6 dialog boxes and

nocrash: support Windows

This patch add support for native Windows to the 'nocrash' module. 2011-09-10 Bruno Haible nocrash: Add support for native Windows. * m4/nocrash.m4 (GL_NOCRASH): Avoid a crash also on native Windows. --- m4/nocrash.m4.orig Sat Sep 10 20:52:11 2011 +++ m4/nocrash.m4 Sat

Re: [Patch] Support for backslash in m4 macros

Hi, Michael Goffioul wrote: > I'd like to propose the 2 following patches that add support for backslashes > in > path names for the corresponding macros. This allows those macros to play > nicer in Win32 environment. Thanks, I confirm that this is the right change to make these macros work with

m4 brackets question

Hi Eric, Again, I've stumbled across a behaviour of brackets in autoconf macros that I don't understand. If in file m4/include_next.m4 at line 210 I add the following code --- case "$host_os" in