OS/2 and stdarg module

[Eric Blake]

[Moving from m4-patches to bug-gnulib]

> > 
> > You need to have a recent CVS checkout of gnulib available, and rerun m4's
> > bootstrap with gnulib-tool either on your path or located in the
> > environment variable GNULIB_TOOL.  (Hmm, I probably ought to add a HACKING
> > document for CVS only that better describes this).  M4_EARLY is built by
> > gnulib-tool, called during bootstrap.
> 
> Done. Then the linker complained about 'gl_va_copy' being an unresolved
> external. Reason is that va_copy is defined to gl_va_copy in config.h.
> gl_va_copy is supposed to be defined in m4/stdarg.m4. I added gl_STDARG_H
> manually to configure.ac but this didn't help because the gl_STDARG_H
> macro in m4/stdarg.m4 uses the AH_VERBATIM macro with an invalid syntax which
> results in a noop. 

More details, please.  Adding gl_STDARG_H to configure.ac is wrong; it is 
already
added by virtue of the fact that gnulib-tool calls it as part of 
M4_EARLY/M4_INIT.
The real question is why ./configure thinks that your compiler doesn't support
va_copy, and what stdarg.m4 should be sticking into config.h that will
work for your compiler.  Can you find the relevant portion of config.log that
shows what happened when testing for va_copy?  What compiler are
you using on OS/2?  What is va_list defined as?  Can you provide a better
fallback implementation that doesn't result in syntax errors?

-- 
Eric Blake