Re: compiling 0115 snapshot on windows.

[Axel Kittenberger]

> Akim Demaille <address@hidden> wrote:
> 
> | | okay people i just compiled the snapshot on windows with MSVC (yuck
> :o)
> | | cygwin configure didn't work out since it said 'install-sh' is
> missing...
> |
> | Yep, the distro is not really portable those days, sorry.
> |
> | | --------------------------------------------------------------------
> | | diff -r -a -u bisonorg/lib/quote.c bisondiff/lib/quote.c
> | | --- bisonorg/lib/quote.c  Mon Oct 16 18:28:40 2000
> | | +++ bisondiff/lib/quote.c Tue Jan 16 12:36:19 2001
> | | @@ -5,6 +5,7 @@
> | |  #endif
> | |
> | |  #include <sys/types.h>
> | | +#include <stdio.h>
> | |  #include <quotearg.h>
> | |  #include <quote.h>
> | |
> | | diff -r -a -u bisonorg/lib/quotearg.c bisondiff/lib/quotearg.c
> | | --- bisonorg/lib/quotearg.c       Mon Oct 16 18:28:40 2000
> | | +++ bisondiff/lib/quotearg.c      Tue Jan 16 12:36:08 2001
> | | @@ -22,6 +22,7 @@
> | |  #endif
> | |
> | |  #include <sys/types.h>
> | | +#include <stdio.h>
> | |  #include <quotearg.h>
> | |  #include <xalloc.h>
> | |
> |
> | Why those two?  You say:
> |
> | | The one and only real stuff fixed is that it needed stdio.h in quote.c
> and
> | | quotearg.c to know from type_t.
> |
> | But clearly you meant something else.  size_t I suppose?
> 
> Having to include stdio.h to get the definition of size_t
> sounds rather bizarre.  Are you sure the only definition of
> size_t on that system is in stdio.h?
> 
> | | diff -r -a -u bisonorg/lib/xmalloc.c bisondiff/lib/xmalloc.c
> | | --- bisonorg/lib/xmalloc.c        Mon Oct  2 09:48:32 2000
> | | +++ bisondiff/lib/xmalloc.c       Tue Jan 16 12:36:55 2001
> | | @@ -47,11 +47,11 @@
> | |  #endif
> | |
> | |  #ifndef HAVE_DONE_WORKING_MALLOC_CHECK
> | | -you must run the autoconf test for a properly working malloc -- see
> 
> Double quote the string (the whole `you...see' line) and it will
> reliably induce a nice syntax error.
> 
> | | malloc.m4
> | | +#error you must run the autoconf test for a properly working malloc
> --
> | | see malloc.m4
> | |  #endif
> |
> | Not portable (well, at least we believe it is not), in the sense that
> | some compiler would choke on
> |
> | #if 0
> | # error Impossible!
> | #endif
> |
> | so, no.
> 

-- 
Sent through GMX FreeMail - http://www.gmx.net