8:48 a.m.
This is failing currently. Its configure line is:
./configure --with-xemacs-compiler=g++ --with-mule --with-pdump --with-error-checking=all
--with-debug=yes --with-bignum=gmp --with-xft=all --with-kkcc --with-newgc
--with-union-type --with-optimization
And it seems to be using gcc-5.4. The compile fails when temacs is run to byte
compile. This error comes from bytecomp.el:
Symbol's value as variable is void: wrapper # bind (stack-trace-on-signal
debug-on-signal stack-trace-on-error debug-on-error)
# (unwind-protect ...)
(put wrapper (quote byte-compile) (function (lambda (form) (let* ((gensym (gensym))
(byte-compile-bound-variables (acons gensym byte-compile-global-bit
byte-compile-bound-variables))) (setq byte-compile-output-preface (byte-compile-top-level
(list (quote progn) (list (quote setq) gensym (list (quote progn) (second form)))
byte-compile-output-preface) t (quote file))) (byte-compile-form (list (quote
symbol-value) (list (quote quote) gensym)) nil)))))
As far as I am concerned, this is very likely to be a compiler bug rather than
a bug in the XEmacs code. I can’t reproduce it locally. I don’t intend to fix
it, I can be more useful with other code. Is there any option for WONTFIX in
the buildbot? If not, could we try changing the buildbot to be
--without-optimizaiton?
Best,
Aidan
--
‘As I sat looking up at the Guinness ad, I could never figure out /
How your man stayed up on the surfboard after forty pints of stout’
(C. Moore)
5:58 p.m.
Aidan Kehoe writes:
Is there any option for WONTFIX in the buildbot?
You mean like not flagging a build as failed if it fails due to an error that
will not be fixed or how should the WONTFIX option work?
If not, could we try changing the buildbot to be
--without-optimizaiton?
The builds are configurable. Feel free to suggest what builds you find most
valuable and what they should contain. Both number of configurations and what
each configuration should contain can be changed.
We have now four different setups based on what once was use for
manually verifying builds. These are:
1. # Most useful debugging:
["--with-mule",
"--with-pdump",
"--with-bignum=gmp",
"--with-debug=yes",
"--with-error-checking=all",
"--with-kkcc=no",
"--with-newgc=no"]
2. # Maximum error catching:
["--with-xemacs-compiler=g++",
"--with-mule",
"--with-pdump",
"--with-error-checking=all",
"--with-debug=yes",
"--with-bignum=gmp",
"--with-xft=all",
"--with-kkcc",
"--with-newgc",
"--with-union-type",
"--with-optimization"]
3. # Maximal difference:
["--with-mule=no",
"--with-pdump",
"--with-kkcc=no",
"--with-newgc=no",
"--with-error-checking=none",
"--with-debug=no",
"--with-bignum=no",
"--with-system-malloc",
"--with-optimization"]
4. # All windows systems:
["--with-xemacs-compiler=g++",
"--with-mule",
"--with-pdump",
"--with-kkcc=no",
"--with-newgc",
"--with-debug=no",
"--with-bignum=no",
"--with-xft=all",
"--with-menubars=no",
"--with-toolbars=no",
"--with-widgets=no",
"--with-jpeg=no",
"--with-tiff=no",
"--with-xpm=no",
"--with-scrollbars=no",
"--with-dialogs=no",
"--with-gif=no",
"--with-png=no",
"--with-xface=no"]
Yours
--
%% Mats
11:47 p.m.
Ar an dara lá déag de mí na Samhain, scríobh Mats Lidell:
> Aidan Kehoe writes:
> Is there any option for WONTFIX in the buildbot?
You mean like not flagging a build as failed if it fails due to an error
that will not be fixed or how should the WONTFIX option work?
Something like that. I suppose on thinking about it further it’s not very
practical.
> If not, could we try changing the buildbot to be
--without-optimizaiton?
The builds are configurable. Feel free to suggest what builds you find
most valuable and what they should contain. Both number of configurations
and what each configuration should contain can be changed.
We have now four different setups based on what once was use for
manually verifying builds. These are:
1. # Most useful debugging:
["--with-mule",
"--with-pdump",
"--with-bignum=gmp",
"--with-debug=yes",
"--with-error-checking=all",
"--with-kkcc=no",
"--with-newgc=no"]
2. # Maximum error catching:
["--with-xemacs-compiler=g++",
"--with-mule",
"--with-pdump",
"--with-error-checking=all",
"--with-debug=yes",
"--with-bignum=gmp",
"--with-xft=all",
"--with-kkcc",
"--with-newgc",
"--with-union-type",
"--with-optimization"]
OK, we should just remove --with-optimization from this. Full optimization
with a G++ build is pointless, it won’t give faster code than the equivalent
gcc for the end user, and will only flush out compiler bugs for us, it is
unlikely to pick up a bug with our code that one of the other builds doesn’t
provoke.
I’m happy enough with the others.
--
‘As I sat looking up at the Guinness ad, I could never figure out /
How your man stayed up on the surfboard after forty pints of stout’
(C. Moore)
10:02 a.m.
Aidan Kehoe writes:
> 2. # Maximum error catching:
> ["--with-xemacs-compiler=g++",
> "--with-mule",
> "--with-pdump",
> "--with-error-checking=all",
> "--with-debug=yes",
> "--with-bignum=gmp",
> "--with-xft=all",
> "--with-kkcc",
> "--with-newgc",
> "--with-union-type",
> "--with-optimization"]
OK, we should just remove --with-optimization from this.
Fine. I'll apply that change. I'll report back when it is activated.
Yours
--
%% Mats
2566
days inactive
2567
days old
4 comments
2 participants
participants (2)
-
Aidan Kehoe -
Mats Lidell