Vladimir G. Ivanovic writes:
 This error occurs when compiling dired.c. What I don't understand
is
 why this error has not cropped up before in the compilation sequence.
 The files alloc.c, console-stream.c, console.c and device.c all
 #include sysdeps.h and are compiled before dired.c is. Yet g++ doesn't
 complain until it gets to dired.c 
Do those files declare `environ' themselves?  Do they use it?
 BTW, I'm using the g++ compiler merely to generate build errors,
as a
 sort of QA effort. If I'm wasting everyone's time, please let me know
 and I'll stop. 
No, don't stop!  I've been too lazy to build with g++ recently, but
that's what the --xemacs-compiler switch is there for, so that it's
easy to check the code for cleanliness across compilers.  I don't
recall ever hearing it needed by a user because configure picked a
totally bogus compiler; this is a developer's tool.
If you use Adrian Aichner's build-report.el, you can easily format and
send a report on your builds to xemacs-buildreports(a)xemacs.org.  If
get a failure that we should know about, send that report and cc:
xemacs-beta.  Successes should just go to xemacs-buildreports.  It
would be appreciated if you would glance at the warnings and if you
see any you are not pretty sure are known (eg, the etags "not a
prototype" warning is a WONTFIX upstream, we know that's coming), a
note at the top of the report would be appreciated.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta