undefined reference in Windows

[Mats Lidell]

>>>>> Eric S Johansson <esj at harvee.org> writes:

Eric> esj at jumper ~/xemacs-beta
Eric> $ ./build-report
Eric> rm -f core
[...]

Ah. Sorry. There is a README that goes with the scripts. It reads:

----------------------------------------------------------------------
Place your favorite configure variation in the file CONFIG in the
build directory. The "build-report" script will build XEmacs saving
all, or at least tries to get some, relevant details in the file
"xemacs-build-report.err". The file is possible to use as a base for
sending a build report to build-reports at xemacs.org.

It isn't perfect. The filter scripts requires python and sh. You may
also need to edit the line pointing out where the filter script is
placed. See "build-report" for details. It doesn't handle the multi
line patterns that the build report XEmacs package support. 
----------------------------------------------------------------------

So the file "CONFIG" should look something like this: (My standard
configuration used as example. Use your own favorite configure
options)

./configure --prefix=/src/xemacs \
	--with-package-path=~/.xemacs:/src/xemacs/xemacs-packages:/src/xemacs/mule-packages:/src/xemacs/site-packages\
        --with-mule\
        --with-newgc\
        --with-xft=all

and place the file in the root folder of your XEmacs sources.

Then you run the built-report script and the build report will be in
the file xemacs-build-report.err.

Hope that helps.

Yours
-- 
%% Mats