Hello andrew!

25 Jan 03 07:27, andrew clarke wrote to Gerrit Kuehn:


 >>>> gcc 3.x complains about va_start in fidoconfs line.c and refuses 

 >> Actually I just wanted to know if this is known to happen.

 ac> Don't know.  I use gcc 2.95.3 here under BSD.  Google might know 
 ac> though.

I was using the same (2.95.4/FreeBSD), but then I thought it would be a
good idea to try gcc 3.x, because some people had reported problems on
systemes using newer gccs. I still had gcc 3.1 available on my system,
which I had to install to be able to compile OpenOffice some months ago.
This one gave me those strange errors.
Now with gcc 3.2 everything is fine, again. I used Google to find some
information about the problem, but the output was rather sparse. The
problem seems to have existed in gcc up to 3.1; there are also people still
reporting the same problem with gcc 3.2, though the issue should have been
fixed there.
Well, all I can say is that now with gcc 3.2.1 it's ok for me.


Regards,
Gerrit

--- Msged/BSD 6.0.0