make-w32
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Latest CVS compile problem - "error no variadic api"


From: Paul D. Smith
Subject: Re: Latest CVS compile problem - "error no variadic api"
Date: Fri, 5 Mar 2004 09:31:53 -0500

%% "J. Grant" <address@hidden> writes:

  jg> A minor problem with latest CVS checkout building for Windows32, using
  jg> build_w32.bat and MSVC6 compiler:

  jg> cl.exe /nologo /MT /W3 /GX /YX /O2 /I . /I glob /I w32/include /D NDEBUG
  jg> /D WINDOWS32 /D WIN32 /D _CONSOLE /D HAVE_CONFIG_H /FR.\WinRel/
  jg> /Fp.\WinRel/gnumake.pch /Fo.\WinRel/ /c misc.c
  jg> misc.c
  jg> misc.c(214) : error C2061: syntax error : identifier 'va_dcl'
  jg> misc.c(250) : error C2061: syntax error : identifier 'va_dcl'
  jg> misc.c(283) : error C2061: syntax error : identifier 'va_dcl'

  jg> __STDC__ is not defined on win32 builds, or defined as 1 etc.

Hm... really?  The ISO C standard says that if your compiler conforms to
the standard it should define __STDC__: I have to believe that in 2004
the Windows compilers at least comply with the 1989 standard!!

  jg> HAVE_VARIADIC and HAVE_STDARG_H both evaluate to true.  Is the
  jg> __STDC__ check needed? It was only added recently.

Hm.  The __STDC__ check is meant to decide whether or not the compiler
accepts the "..." form of function prototypes.

It could be considered redundant if you assume that any host with
stdarg.h must also support "...".

-- 
-------------------------------------------------------------------------------
 Paul D. Smith <address@hidden>          Find some GNU make tips at:
 http://www.gnu.org                      http://make.paulandlesley.org
 "Please remain calm...I may be mad, but I am a professional." --Mad Scientist




reply via email to

[Prev in Thread] Current Thread [Next in Thread]