8:40 p.m.
Anybody else noticed that 'make check' fails horribly because of the
package changes lately?
Testing /usr/local/src/xemacs-21.5/tests/automated/byte-compiler-tests.el...
Unexpected error (void-function defadvice) while executing interpreted code.
Test suite execution aborted.
Unexpected error (void-variable message) while executing byte-compiled code.
Test suite execution aborted.
byte-compiler-tests.el: No tests run
Test suite execution failed unexpectedly.
[...]
Testing /usr/local/src/xemacs-21.5/tests/automated/symbol-tests.el...
Unexpected error (void-variable pathname-coding-system) while executing interpreted code.
Test suite execution aborted.
Unexpected error (void-variable pathname-coding-system) while executing byte-compiled
code.
Test suite execution aborted.
symbol-tests.el: 246 of 248 (99%) tests successful.
Test suite execution failed unexpectedly.
Testing /usr/local/src/xemacs-21.5/tests/automated/syntax-tests.el...
Unexpected error (void-function c-mode) while executing interpreted code.
Test suite execution aborted.
Unexpected error (void-function c-mode) while executing byte-compiled code.
Test suite execution aborted.
syntax-tests.el: 60 of 60 (100%) tests successful.
Test suite execution failed unexpectedly.
Done
Is this just not working yet? I was going to flood stephen with build
reports for linux for the 64 variants my scripts build, but didn't want to
submit bogus 'check' results.
-bp
--
Ceterum censeo vi esse delendam
9:31 p.m.
>>>> "BP" == William M Perry
<wmperry(a)gnu.org> writes:
BP> Anybody else noticed that 'make check' fails horribly because of the
BP> package changes lately?
BP> Testing /usr/local/src/xemacs-21.5/tests/automated/byte-compiler-tests.el...
BP> Unexpected error (void-function defadvice) while executing interpreted code.
BP> Test suite execution aborted.
BP> Unexpected error (void-variable message) while executing byte-compiled code.
BP> Test suite execution aborted.
BP> byte-compiler-tests.el: No tests run
BP> Test suite execution failed unexpectedly.
BP> [...]
BP> Testing /usr/local/src/xemacs-21.5/tests/automated/symbol-tests.el...
BP> Unexpected error (void-variable pathname-coding-system) while executing
interpreted code.
BP> Test suite execution aborted.
BP> Unexpected error (void-variable pathname-coding-system) while executing
byte-compiled code.
BP> Test suite execution aborted.
BP> symbol-tests.el: 246 of 248 (99%) tests successful.
BP> Test suite execution failed unexpectedly.
BP> Testing /usr/local/src/xemacs-21.5/tests/automated/syntax-tests.el...
BP> Unexpected error (void-function c-mode) while executing interpreted code.
BP> Test suite execution aborted.
BP> Unexpected error (void-function c-mode) while executing byte-compiled code.
BP> Test suite execution aborted.
BP> syntax-tests.el: 60 of 60 (100%) tests successful.
BP> Test suite execution failed unexpectedly.
BP> Done
BP> Is this just not working yet? I was going to flood stephen
BP> with build reports for linux for the 64 variants my scripts
BP> build, but didn't want to submit bogus 'check' results.
Hi Bill,
I can confirm the breakage in (emacs-version)
"XEmacs 21.5 (beta5) \"beets\" [Lucid] (i586-pc-win32, Mule) of Tue
Apr 02 2002 on D5DC120J"
as well (native Windows).
So I presume your results wouldn't be bogus, since these are for real.
I think Ben is aware of these.
Best regards,
Adrian
BP> -bp
BP> --
BP> Ceterum censeo vi esse delendam
--
Adrian Aichner
mailto:adrian＠xemacs.org
http://www.xemacs.org/
4:05 a.m.
>>>> "-BP" == William M Perry
<wmperry(a)gnu.org> writes:
-BP> Anybody else noticed that 'make check' fails horribly because
-BP> of the package changes lately?
Yes. I know what's happening, but I haven't had time to fix it.
Basically what needs to be done is to hand-load, not require, the
packages from the "expected" place and if that fails spit out a "not
found" warning, plus some information about how to point to it
properly. It's not trivial though, because it means looking up
EMACSPACKAGEPATH or something like that "by hand".
-BP> Is this just not working yet? I was going to flood stephen
-BP> with build reports for linux for the 64 variants my scripts
-BP> build, but didn't want to submit bogus 'check' results.
Go ahead, I know what's bogus and what's not. Or you can fix the
tests first if you prefer. ;-)
--
Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Don't ask how you can "do" free software business;
ask what your business can "do for" free software.
2 p.m.
>>>> "Stephen" == Stephen J Turnbull
<stephen(a)xemacs.org> writes:
Stephen> Yes. I know what's happening, but I haven't had time to fix it.
When I perform the 'make check', I also get:
Testing /home/malcolmp/devl/xemacs/xemacs-21.5/tests/automated/c-tests.el...
Fatal error: assertion failed, file
/home/malcolmp/devl/xemacs/xemacs-21.5/src/tests.c, line 364, !memcmp
(BI_BUF_BYTE_ADDRESS (current_buffer, charbpos_to_bytebpos (current_buffer,
((current_buffer)->bufpt + 0))), int_foo, sizeof (int_foo) - 1)
Is this related to the above?
Machine: PPC Linux, gcc 2.95.2. and gcc 3.0.4.
Malcolm
--
Malcolm Purvis <malcolmpurvis(a)optushome.com.au>
The hidden, terrible cost of nuclear warfare is Really Bad Public Art.
- Angus McIntyre, alt.peeves, 13/3/02.
6:28 p.m.
Ben,
Any ideas why Malcolm might get an assert here?
to Malcolm: no, XEmacs should never ever terminate without your
explicit permission. (Of course, the user is expected to be gracious
about OS crashes and power failures. :^) Thanks for reporting this.
What I was referring to were Lisp errors that simply throw back to the
top-level read-eval-redisplay loop, and were clearly due to
file-not-found or the like.
>>>> "Malcolm" == Malcolm Purvis
<malcolmpurvis(a)optushome.com.au> writes:
>>>> "Stephen" == Stephen J Turnbull
<stephen(a)xemacs.org> writes:
Stephen> Yes. I know what's happening,
but I haven't had time to fix it.
Malcolm> When I perform the 'make check', I also get:
Testing /home/malcolmp/devl/xemacs/xemacs-21.5/tests/automated/c-tests.el...
Fatal error: assertion failed, file
/home/malcolmp/devl/xemacs/xemacs-21.5/src/tests.c, line 364, !memcmp
(BI_BUF_BYTE_ADDRESS (current_buffer, charbpos_to_bytebpos (current_buffer,
((current_buffer)->bufpt + 0))), int_foo, sizeof (int_foo) - 1)
Malcolm> Is this related to the above?
Malcolm> Machine: PPC Linux, gcc 2.95.2. and gcc 3.0.4.
--
Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Don't ask how you can "do" free software business;
ask what your business can "do for" free software.
4:22 p.m.
>>>> "William" == William M Perry
<wmperry(a)gnu.org> writes:
William> Anybody else noticed that 'make check' fails horribly
William> because of the package changes lately?
i have sent at least 3 possible 4 build reports stating this fact
it made me a bit dubious about actualling installing it
the xemacs process doing the checking core dumps on my box
--
XEmacs Advocate | Do not try the patience of Wizards,
FreeBSD Devote | for they are subtle and quick to anger.
Perl Hacker | - Elric (Technomage) , Babylon 5.
Apache God | <mailto:rendhalver＠xemacs.org>
8058
days inactive
8068
days old
5 comments
5 participants
participants (5)
-
Adrian Aichner -
Malcolm Purvis -
Rendhalver [Peter Brown] -
Stephen J. Turnbull -
William M. Perry