Re: va_dcl

[Geoff Keating <geoffk@ozemail.com.au>]

> From: "Jack Howarth" <howarth@bromo.med.uc.edu>
> Date: Sun, 8 Nov 1998 13:09:53 -0500
> 
>    I assume this really is a egcs problem but I was curious if anyone here
> knew the answer. I am finding under egcs_1_1_branch/glibc 2.0.100 that
> programs like xbl and xfig that use va_dcl are generating compile errors
> on linuxppc. From what I can see all the vararg related headers belong
> entirely in egcs now. Is this different from glibc 2.0.7/egcs 1.0.x?
> I kinda recall seeing a varargs.h include at some point in the past
> being in /usr/include. In any case, the following syntax seems to be
> unacceptable now
> 
> va_dcl 
> {
> ...misc statements...
> }
> 
> Any idea why this is no longer valid under glibc 2.0.100/egcs 1.1?

I just built xfig from redhat 5.1, xfig-3.2-3.src.rpm, under glibc
2.0.97 and egcs 1.1b, and it built fine.

The only places it seems to use va_dcl are:

int
put_msg(va_alist)
    va_dcl
{
    va_list ap;
    char *format;
...

int
file_msg(va_alist) va_dcl
{
    va_list arglist;
    XawTextBlock block;
    va_list ap;
...

static void show_msg(va_alist)
     va_dcl
{
  va_list ap;
  char *format;
...

all of which look perfectly reasonable to me.

-- 
Geoffrey Keating <geoffk@ozemail.com.au>