>>>> Eric S Johansson <esj(a)harvee.org> writes:
Eric> what do you need in a build report?
* Short answer:
The "Installation"-file from your build and the part of the build that
fails. Look in the root folder of your xemacs sources for the
Installation-file. Cut and Paste the relevant error messages from the
build. Send the mail to xemacs-buildreports with the subject starting
with [Failure]. Look in the archives for earlier postings.
* Longer answer for the true way:
There is a package, build, in the package tree that provides the
command build-report. So equipped with that you should be able to do
M-x built-report and be guided trough the process to create a
build-report.
* Even longer answer for a semi true way:
Unfortunately the build-report command fails for me at the moment and
have done so in the past too at occasions. And if you haven't the
packages, which can be the situation when setting up XEmacs to begin
with, your lost. For this situation, and for some other reasons, I
have created two python scripts that produces a report that is similar
to the build-report. You can browse them here:
"http://hg.debian.org/hg/xemacs/xemacs-builds/file/4c98a8044dec/matsl/build_report/"
I use them daily when building different versions of XEmacs and find
it very convenient. YMMW.
Yours
--
%% Mats
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta