Please, please send build reports to xemacs-buildreports(a)xemacs.org.
See
http://www.xemacs.org/Releases/Public-21.2/tester.html.
Summary: use M-x build-report. If you don't get a working XEmacs, you
should report the build anyway, by setting build-report's
variables. The ones you need to set to use a different XEmacs to
report the build are build-report-installation-file and
build-report-make-output-files.
I am sure the precise reports given below will help Bill to solve the
problems. _I don't care about the showstoppers because those are
Bill's job; he'll either fix them or the decision is obvious._ What I
do care about is minor weirdnesses that _don't_ stop the build.
Of course, I won't be able to catch them all. But if I see even one
or two under --with-gtk=no I'll have to conclude that this feature is
too dangerous for inclusion in the release tarballs. Also, it's not
clear to me whether David's build is --with-gtk=no. This is easily
parsed from the build-report.
>>>> "Philip" == Philip Aston
<paston(a)bea.com> writes:
I've done the same under cygwin _with_ X libraries.
Don't see the first error, but I do see the second, plus another
cygwin problem as related in
http://list-archive.xemacs.org/xemacs-beta/200102/msg00481.html
--with-gtk=no seems to work fine though.
- Phil
Bush, David writes:
I checked out Xemacs from the gtk-xemacs-21-2 branch and build under
Cygwin. I ran into two problems.
1) lib-src/gnuclient.c fails to build with a parse error before else at line
654.
2) For the first time I see temacs looping when running
auto-autoloads.el This is reproducible. I reran "make beta" on
21-2.45 loaded from tarballs and this did not hang.
--
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091
_________________ _________________ _________________ _________________
What are those straight lines for? "XEmacs rules."