RE: Re: [PATCH] latest patch for kkcc etc.
21 years, 4 months
Ben Wing
Ben Wing
btw as for those 37000 stack frames when marking a list, kkcc has a simple form of tail-recursion built into it that should ideally handle lists without any stack recursion. if that's not working it should be easy to fix it. (right, mike?)
------- Original Message -------
On
Fri, 20 Dec 2002 19:39:26 +0900 Stephen J. Turnbull?wrote:
FUT xemacs-beta.
>>>>> "Ben" == Ben Wing <wing(a)666.com> writes:
Ben> i did test this non-kkcc. in fact i tested it in quite a
Ben> number of configurations, so i'm surprised to see that it
Ben> broke. how did it break?
Well, for starters the MS-only (?) functions strupr and strlwr were
left naked in lisp.h, breaking the link. The crash I'm getting is
Fatal error: assertion failed, file /coda/Software/XEmacs/21.5/src/alloc.c, line 3323, GCLI_lh != 0
#5 0x080ea8e7 in assert_failed (
file=0x830d200 "/coda/Software/XEmacs/21.5/src/alloc.c", line=3323,
expr=0x830de6a "GCLI_lh != 0")
at /coda/Software/XEmacs/21.5/src/emacs.c:3624
#6 0x08093ae2 in mark_object (obj=
{gu = {type = Lisp_Type_Record, val = 35288680}, s = {bits = 0, val = 70577360}, u = {bits = 0, val = 70577360}, ui = 141154720, i = 141154720, v = 0x869d9a0}) at /coda/Software/XEmacs/21.5/src/alloc.c:3323
followed by about 150 frames of mark_foo(), details on request. Is
this symtomatic of broken union-type? This is a --use-union-type
build. I see this particular assert a fair amount myself, and
occasionally in backtraces on xemacs-beta.
I'll try with --use-union-type=no.
Ben> one more thing ... you're not using union-type, are you? i
Ben> get crashes galore in pdump with both gcc and vc++, using
Ben> union type. see all my messages about this.
It would be nice to have real bug reports (ie, >= C backtrace) on this
stuff so that (a) we can guess whether we're seeing what you've seen
and (b) we can pass it on to the GCC core developers who occasionally
contribute to XEmacs.
--
Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.
- 2 participants
- 1 comments
Re: [PATCH] latest patch for kkcc etc.
21 years, 4 months
Stephen J. Turnbull
Stephen J. Turnbull
FUT xemacs-beta.
>>>>> "Ben" == Ben Wing <wing(a)666.com> writes:
Ben> i did test this non-kkcc. in fact i tested it in quite a
Ben> number of configurations, so i'm surprised to see that it
Ben> broke. how did it break?
Well, for starters the MS-only (?) functions strupr and strlwr were
left naked in lisp.h, breaking the link. The crash I'm getting is
Fatal error: assertion failed, file /coda/Software/XEmacs/21.5/src/alloc.c, line 3323, GCLI_lh != 0
#5 0x080ea8e7 in assert_failed (
file=0x830d200 "/coda/Software/XEmacs/21.5/src/alloc.c", line=3323,
expr=0x830de6a "GCLI_lh != 0")
at /coda/Software/XEmacs/21.5/src/emacs.c:3624
#6 0x08093ae2 in mark_object (obj=
{gu = {type = Lisp_Type_Record, val = 35288680}, s = {bits = 0, val = 70577360}, u = {bits = 0, val = 70577360}, ui = 141154720, i = 141154720, v = 0x869d9a0}) at /coda/Software/XEmacs/21.5/src/alloc.c:3323
followed by about 150 frames of mark_foo(), details on request. Is
this symtomatic of broken union-type? This is a --use-union-type
build. I see this particular assert a fair amount myself, and
occasionally in backtraces on xemacs-beta.
I'll try with --use-union-type=no.
Ben> one more thing ... you're not using union-type, are you? i
Ben> get crashes galore in pdump with both gcc and vc++, using
Ben> union type. see all my messages about this.
It would be nice to have real bug reports (ie, >= C backtrace) on this
stuff so that (a) we can guess whether we're seeing what you've seen
and (b) we can pass it on to the GCC core developers who occasionally
contribute to XEmacs.
--
Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.
- 2 participants
- 1 comments
XEmacs crash
21 years, 4 months
Nikichine, Alexis
Nikichine, Alexis
Hello, my XEmacs disappeared in the air leaving a message prompting me to report, and the following line (which may not come from XEmacs however):
Fatal error: assertion failed, file eval.c, line 1877, abort()
Here is the installation description:
_____
uname -a: OSF1 vijay.xko.dec.com X5.1 1133 alpha
./configure 'alpha-dec-osf5.1' '--prefix=/usr/lib/xemacs-21.1.11' '--lispdir=/usr/lib/xemacs-21.1.11/lisp' '--etcdir=/usr/lib/xemacs-21.1.11/etc' '--infodir=/usr/lib/xemacs-21.1.11/info' '--archlibdir=/usr/lib/xemacs-21.1.11/alpha-dec-osf5.1' '--lockdir=/usr/lib/xemacs-21.1.11/lock' '--with-xpm' '--with-offix=no'
XEmacs 21.1.11 "Carlsbad Caverns" configured for `alpha-dec-osf5.1'.
Where should the build process find the source code? /usr/users/Xemacs/xemacs-21.1.11/xemacs-21.1.11
What installation prefix should install use? /usr/lib/xemacs-21.1.11
What operating system and machine description files should XEmacs use?
`s/decosf4-0.h' and `m/alpha.h'
What compiler should XEmacs be built with? cc -O3
Should XEmacs use the GNU version of malloc? yes
Should XEmacs use the relocating allocator for buffers? yes
What window system should XEmacs use? x11
Where do we find X Windows header files?
Where do we find X Windows libraries?
Compiling in support for XAUTH.
Compiling in support for XPM images.
--------------------------------------------------------------------
WARNING: Compiling without PNG image support.
WARNING: You should strongly consider installing the PNG libraries.
WARNING: Otherwise certain images and glyphs may not display.
WARNING: (a copy may be found in <ftp://ftp.xemacs.org/pub/xemacs/aux> ftp://ftp.xemacs.org/pub/xemacs/aux)
--------------------------------------------------------------------
Compiling in support for (builtin) GIF image handling.
Compiling in support for DBM.
Compiling in support for proper session-management.
Using Lucid menubars.
Using Lucid scrollbars.
Using Motif dialog boxes.
Compiling in DLL support.
movemail will use "flock" for locking mail spool files.
_____
And there's the backtrace obtained with dbx:
_____
0 __kill(0x120056df4, 0x70000001406fc680, 0x120089cd0, 0x6, 0x120089d18) [0x3ff800e8a78]
1 fatal_error_signal(0x120089d18, 0x0, 0x3ff800d5124, 0xa000000140188928, 0x4000000140a39c98) [0x120089d90]
2 __kill(0x100000003, 0x1, 0x0, 0x11fff69b0, 0x20202e4200000008) [0x3ff800e8a78]
3 (unknown)() [0x3ff802061e8]
4 __tis_raise(0x20202e4200000008, 0x616c696d69732041, 0x3ff8013aae8, 0x4059000000000006, 0x3ff8019ea94) [0x3ff8013aae4]
5 raise(0x3ff8013aae8, 0x4059000000000006, 0x3ff8019ea94, 0x3ff0000000000000, 0x3ff801c1d24) [0x3ff8019ea90]
6 abort(0x12008d6a4, 0x14003cea8, 0x120089c90, 0x0, 0x600000000) [0x3ff801c1d20]
7 assert_failed(0x120089c90, 0x0, 0x600000000, 0x0, 0x1200910c4) [0x12008d6a0]
8 (unknown)() [0x1200910c0]
9 Fsignal(0x11fff6b10, 0x100000001, 0x4000000140a39c98, 0xa000000140188928, 0x120053cac) [0x120091680]
10 signal_error(0x120053cac, 0x3000000140635e00, 0x120071c58, 0x3000000140635e00, 0x140635e00) [0x1200916d8]
11 dead_wrong_type_argument(0x120071c58, 0x3000000140635e00, 0x140635e00, 0x4000000140a39ca8, 0x12012ff38) [0x120071c54]
12 (unknown)() [0x12012ff34]
13 kill_buffer_processes(0x140009430, 0x1403b9b70, 0x1000000000000000, 0xfffffffffffffff, 0x100000003) [0x120130d10]
14 (unknown)() [0x12008cec8]
15 fatal_error_signal(0xa000000140188808, 0x0, 0x3ff800d5124, 0x2000000100000003, 0x0) [0x120089d44]
16 (unknown)() [0x120056e00]
17 garbage_collect_1(0x11fff6f90, 0x1, 0x20000001405d5200, 0x1201528c8, 0x756f6d2f00000028) [0x12005917c]
18 funcall_recording_as(0x0, 0x0, 0x1200db2f4, 0x140048d74, 0x1200dc034) [0x1200941bc]
19 call3(0xa0000001401b3808, 0x600000014075f488, 0xa000000140188808, 0x11fff7208, 0x11fff7078) [0x120096474]
20 Fexpand_file_name(0x11fff7208, 0x11fff7120, 0x100000001, 0xa000000140188808, 0x600000014075f488) [0x1200dc060]
21 Ffile_symlink_p(0x1400491d8, 0x11fff7208, 0x1200e190c, 0x1409f16a8, 0x11fff73b0) [0x1200df11c]
22 Fwrite_region_internal(0x8, 0x8, 0x1200942c4, 0x11fff8510, 0x0) [0x1200e1b8c]
23 funcall_recording_as(0x1, 0x0, 0x39, 0x0, 0x39) [0x120094810]
24 Fbyte_code(0xa000000100000028, 0x1400ec168, 0x11fff8510, 0x100000026, 0x11fff8678) [0x120062798]
25 (unknown)() [0x1200959ac]
26 funcall_recording_as(0xa0000001401b3808, 0x600000014075f488, 0xa000000140188808, 0x600000014017e898, 0x120094400) [0x12009489c]
27 Fapply(0x11fff89a8, 0x100000002, 0x11fff89b8, 0x2, 0x20000001400ec1a8) [0x120095310]
More (n if no)?
28 funcall_recording_as(0x4000000140a39c58, 0x1405bf300, 0x120063484, 0x8, 0xa0000001407ea668) [0x1200943fc]
29 Fbyte_code(0x400000010000001f, 0x140889908, 0x11fff8910, 0x100000022, 0xa0000001402371e8) [0x120062798]
30 (unknown)() [0x1200959ac]
31 funcall_recording_as(0xa000000100000046, 0x11fff8b10, 0x0, 0x0, 0x14017af78) [0x12009489c]
32 call8(0x600000014075f488, 0xa000000140188808, 0xa000000140188838, 0x600000014075f290, 0xa000000140188808) [0x120096714]
33 Fwrite_region_internal(0x48, 0x140696b68, 0x1200942c4, 0x600000014075f488, 0xfffffffffffffffc) [0x1200e0f90]
34 funcall_recording_as(0x11fffa0e0, 0x11fffa1e8, 0x11fffa1f0, 0x1500000001, 0x120160000) [0x120094810]
35 Fbyte_code(0xa00000010000001d, 0x1400ec168, 0x11fff9fc0, 0x26, 0x140049130) [0x120062798]
36 (unknown)() [0x1200959ac]
37 funcall_recording_as(0xa000000140188808, 0x1405bf1f8, 0x1, 0x1, 0x1200981e0) [0x12009489c]
38 Fbyte_code(0x6000000100000014, 0x1400f5ff0, 0x11fffa230, 0x26, 0x1200db2f4) [0x120062798]
39 (unknown)() [0x1200959ac]
40 funcall_recording_as(0x140bbf400, 0x1402bed00, 0x120062644, 0xa0000001401e9da8, 0x2) [0x12009489c]
41 Fbyte_code(0x10000000f, 0x1400f6880, 0x11fffa500, 0x22, 0x0) [0x120062798]
42 (unknown)() [0x1200959ac]
43 funcall_recording_as(0xa000000140188808, 0x1405bf150, 0x120063ed0, 0x8b, 0x1405bf120) [0x12009489c]
44 Fbyte_code(0x8000000000000006, 0x1400f6348, 0x11fffaa80, 0x100000020, 0x120062ffc) [0x120062798]
45 (unknown)() [0x1200959ac]
46 funcall_recording_as(0x140049130, 0xfffffffffffffff, 0x73, 0x11fffb210, 0x11fffb0f0) [0x12009489c]
47 Fbyte_code(0x3, 0x1400f5c30, 0x11fffb0f0, 0x100000020, 0x11fffb668) [0x120062798]
48 (unknown)() [0x1200959ac]
49 funcall_recording_as(0xa000000140188808, 0x1405bf018, 0x100000001, 0xa000000140188808, 0x100000000) [0x12009489c]
50 Fcall_interactively(0x140293978, 0x140049130, 0x120092a54, 0x140049130, 0xfffffffffffffff) [0x120066480]
51 Fcommand_execute(0xa000000140293958, 0xa000000140188808, 0xa000000140188808, 0xa000000140188808, 0x1200c66f0) [0x120092c1c]
52 (unknown)() [0x1200c6734]
53 Fdispatch_event(0x140049578, 0x140049580, 0x1403bb100, 0x100000001, 0xa000000140188808) [0x1200c6f08]
54 Fcommand_loop_1(0x11fffb7f8, 0x100000001, 0xa000000140188808, 0x20000001407511d8, 0x100000000) [0x12006cc3c]
55 condition_case_1(0x1200c5cd8, 0x1400497c8, 0x140049130, 0x0, 0x0) [0x120090c8c]
56 (unknown)() [0x12006c148]
57 internal_catch(0x1, 0x60000001401aad30, 0x120055400, 0x0, 0x0) [0x1200907ac]
58 initial_command_loop(0xa000000140188808, 0x1, 0x11fffc018, 0x2, 0x1) [0x12006c444]
59 (unknown)() [0x12008be4c]
60 main(0x11fffbe90, 0x100000000, 0x12005255c, 0x200000000, 0x11fffc030) [0x12008cb48]
_____
Hope this helps in any manner,
--
Alexis Nikichine
Student,
Signalling Protocol Platform,
HP Technical Center, Valbonne, France
Phone: +33 (0)4 92 95 52 61 -- Fax: +33 (0)4 92 95 63 63
- 2 participants
- 1 comments
Re: [PATCH] [packages] Create pdepends.mk with per-package autoloads
21 years, 4 months
Jan Vroonhof
Jan Vroonhof
[cc'ed back to xemacs-beta to show signs of life :-(]
> > Ville> Seems that pdepends.mk still isn't
> > created by running a
> > Ville> "make autoloads" in a package dir,
> > Ville> ie. packages/xemacs-packages/<package>.
Is that necessary?
At the moment the pdepends.mk express the interdepencies between
the different packages, so they only make sense from the directory
one level above (i.e. from the Makefile in xemacs-packages).
For instance, say haskell-mode/pdepends.mk says
./haskell-mode/autoloads.target: ./dired/autoloads.target mail-lib/autoloads.target xemacs-base/autoloads.target edit-utils/autoloads.target
./haskell-mode/compile.target: ./dired/compile.target mail-lib/compile.target xemacs-base/compile.target edit-utils/compile.target
which says that dired, mail-lib, xemacs-base and edit-utils must be compiled
before haskell-mode.
This kind of information only makes sense from a directory that sees
all this packages. Ideally you want to this from the toplevel so you
can have dependencies between mule packages and normal packages
So you could argue that
instead of
cd xemacs-packages/haskell-mode
make compile
you should do
cd xemacs-packages
make haskell-mode/compile.target
as the latter rebuilds the dependencies if needed.
> > He's probably not reading xemacs-patches
>
> Not very closely, and not very often.
I am afraid so :-(
> > I suspect you should get rid of the pdepends.mk
> > rules in the other
> > Makefiles (== levels?). This should catch them all,
> > no? [But I don't
> > understand the pdepends.mk mechanism yet.] Steve,
> > what do you think?
>
> Jan is the better one to ask. I think what's needed
> is to ensure that all required pdepends.mk files are
> always built (and used) regardless of where make is
> invoked from.
It is important they get rebuild from the Makefiles that use them,
which is AFAICS the case. See this rule in iterate.rules
$(DEPENDS_FILES): %$(DEPENDS_FILE_NAME): %Makefile ../XEmacs.rules
$(MAKE) $(MFLAGS) -C $(*D) TARGET_BASE=$(dir $(*D)) \
$(DEPENDS_FILE_NAME)
The pdepend.mk stuff is there so that there is only one place that
contains the dependency information, which is the REQUIRES line in
the package Makefile.
This used to be hardcoded in multiple places, or the information would
be simply ignored.
Ideally in a package build you should NEVER see ".el file newer than
.elc" file warnings.
I agree this all very hacky, but it took quite a bit of effort to get
right. This way Make can figure out all the proper dependencies with
out relying on the fact that you called the toplevel make autoload before
make bytecompile etc...
For instance, this rule
$(BYTECOMPILE_TARGETS): %bytecompile.target: %autoloads.target
tells Make that autoloads must be made before bytecompiles, therefore
haskell-mode/byte-compile.target depends haskell-mode/autoload.target
depends on dired/autoload.target and on dired/bytecompile.target
ensuring that whatever happends, autoloads for the dependencies are
always generated first, and that dependencies are alwyas compiled
before the package.
I see that this line has recently been commented out.. Why? Was there
some problem.
This stuff is important to allow a clean bootstrap to work
i.e.
cvs checkout xemacs
cvs checkout packages
build xemacs (don't install any packages)
build packages with the xemacs just compiled above.
Similarly I always build with
VANILLA = -vanilla -no-autoloads
so that any existing autoloads from already installed packages don't
get used by accident. I think -no-autoloads should be the default.
Hopefully thus clears this up?
Merry christmas to you all,
I hope you will see more of me next year,
Jan
- 2 participants
- 1 comments
[bug report] last CVS unusable in console
21 years, 4 months
Giacomo Boffi
Giacomo Boffi
i'm not submitting a regular bug report as 21.5 is no mire usable in
console, and i have to use 21.4.10 to send this email
in short, following ms windows patch (nomen omen?) i was unable to use
xemacs 21.5 in console
it looks like it's idea of the dimensions of the terminal screen is
gettin wronger and wronger, and the windows are shrinked in a corner
of the screen... very funny, in a sense...
the bug recipe is
% xemacs -vanilla # no DISPLAY set
M-x set-var RET debug-on-error RET t RET
M-x vm RET
and i get the attached lisp backtrace
please note that setting debug-on-error to t, leaves 3 (three)
modelines on my screen, leaves me with a severely shrinked *Lisp
Interaction* buffer, and that when i do M-x vm the minibuffer is about
in the 3rd-4th line of the terminal screen...
i'm on debian linux, uname -a says
Linux boffi95 2.2.21 #1 Wed Jul 17 12:52:48 CEST 2002 i586 unknown unknown GNU/Linux
and this is the 21.5 "Installation" file
uname -a: Linux boffi95 2.2.21 #1 Wed Jul 17 12:52:48 CEST 2002 i586 unknown unknown GNU/Linux
./configure '--extra-verbose' '--with-widgets' '--with-athena=3d' '--debug' '--rel-alloc' '--pdump' '--with-sound=no'
XEmacs 21.5-b9 "brussels sprouts" (+CVS-20021217) configured for `i586-pc-linux'.
Compilation / Installation:
Source code location: /home/gb/src/xemacs
Installation prefix: /usr/local
Operating system description file: `s/linux.h'
Machine description file: `m/intel386.h'
Compiler: gcc -Wall -Wno-switch -Winline -Wmissing-prototypes -Wsign-compare -Wundef -Wstrict-prototypes -Wshadow -Wmissing-declarations -g -O3
Relocating allocator for buffers: yes
GNU version of malloc: yes
- Using Doug Lea's new malloc from the GNU C Library.
Window System:
Compiling in support for the X window system:
- X Windows headers location: /usr/X11R6/include
- X Windows libraries location: /usr/X11R6/lib
- Handling WM_COMMAND properly.
Compiling in support for the Athena widget set:
- Athena headers location: X11/Xaw3d
- Athena library to link: Xaw3d
Using Lucid menubars.
Using Lucid scrollbars.
Using Athena dialog boxes.
Using Athena native widgets.
TTY:
Compiling in support for ncurses.
Compiling in support for GPM (General Purpose Mouse).
Images:
Compiling in support for GIF images (builtin).
Compiling in support for XPM images.
Compiling in support for PNG images.
Compiling in support for JPEG images.
Compiling in support for TIFF images.
Compiling in support for X-Face message headers.
Sound:
Databases:
Compiling in support for Berkeley database.
Internationalization:
Mail:
Compiling in support for "dot-locking" mail spool file locking method.
Other Features:
Inhibiting IPv6 canonicalization at startup.
Compiling in support for dynamic shared object modules.
Using the new portable dumper.
Compiling in support for extra debugging code.
WARNING: ---------------------------------------------------------
WARNING: Compiling in support for runtime error checking.
WARNING: XEmacs will run noticeably more slowly as a result.
WARNING: Error checking is on by default for XEmacs beta releases.
WARNING: ---------------------------------------------------------
and, finally, this is the lisp backtrace
hth, ciao
- 2 participants
- 1 comments
RE: Re: union type is EVIL EVIL EVIL
21 years, 4 months
Ben Wing
Ben Wing
it's useful to compile with union type to catch problems, as stephen mentions, but it has such a propensity to create random crashes due to compiler bugs, which often appear like xemacs problems, that people who don't have a good idea of its uses should not use it.
it's similar with c++ but there are other advantages ... for example my recently-introduced bad-gcpro-catching code. note also that it's possible to catch insufficient gcproing using c++, but somewhat difficult. i put in a comment to this effect in my kkcc patch.
btw michael you're not compiling my kkcc patch with --use-union-type, are you? (sorry if this appears in another message as well. internet cafes suck.)
ben
------- Original Message -------
On
Tue, 17 Dec 2002 22:35:11 +0900 Stephen J. Turnbull?wrote:
>>>>> "Ville" == Ville Skytt <Ville> writes:
Ville> On Tue, 2002-12-17 at 04:20, Ben Wing wrote:
>> stephen -- while you're in the process of modifying PROBLEMS,
>> please add an entry about union type and its propensity to
>> cause crashes. here's some text that should get you started:
Ville> [...]
Ville> Uh, --use-union-type has been many times suggested on
Ville> xemacs-beta as a way to prevent crashes in something
Ville> related to aggressive compiler
Ville> What's correct?
To some extent, both. Sometimes you lose, and other times you lose
big. There's nothing we can do about compiler bugs except write them
up in PROBLEMS and code defensively. There are any number of
temporaries in XEmacs notated with "Compiler XYZ chokes without this."
This is more of the same. :-(
To me it's a pragmatic issue (if anything, union type is more
"righteous" than the int Lisp_Object type). GCC (and now VC++) has
historically had problems with unions.[1] OTOH unions have historically
been good at smoking out "if (lisp_object) ..." constructs and the
like, and to some extent aliasing issues.
I think if you look, you'll find that (a) it's often been me
recommending union type[2] and (b) --use-union-type typically doesn't
solve any problems. If better diagnosis tools are now available, then
there may be reason to avoid union type.
Footnotes:
[1] They've also had problems with std C++ ... but I doubt Ben would
argue that is EVIL EVIL EVIL ;-)
[2] Ie, you're really only citing one opinion.
--
Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.
- 2 participants
- 1 comments
21.5 with Ben's patch: window config anomoly
21 years, 4 months
Stephen J. Turnbull
Stephen J. Turnbull
The window on the scratch buffer is overwriting the toolbar, and in
turn being overwritten by the gutter (specifically, buffer tabs).
Note the position of the cursor in the upper left, and the tops of the
toolbar button dividers. I'm not sure what triggered it, but C-l
doesn't help, nor does iconify-and-restore. However, creating a new
frame did restore the correct configuration in the garbled frame.
This is with Ben's big patch (the one that breaks the build because
strupr and strlwr aren't #ifdef WINDOWS_NATIVE and was missing the
*-slots.h files, too). Installation for the record.
uname -a: Linux tleepslib 2.2.18 #1 SMP Tue Dec 26 11:36:10 JST 2000 i686 unknown unknown GNU/Linux
/coda/Software/XEmacs/21.5/configure '--with-mule' '--with-xim=xlib' '--with-xfs' '--with-widgets=athena' '--with-athena=3d' '--with-dialogs=athena' '--with-sound=noesd' '--external-widget' '--with-modules' '--use-kkcc' '--debug' '--error-checking=all' '--use-union-type'
XEmacs 21.5-b9 "brussels sprouts" (+CVS-20021218) configured for `i686-pc-linux'.
Compilation / Installation:
Source code location: /coda/Software/XEmacs/21.5
Installation prefix: /usr/local
Operating system description file: `s/linux.h'
Machine description file: `m/intel386.h'
Compiler: gcc -Wall -Wno-switch -Winline -Wmissing-prototypes -Wsign-compare -Wundef -Wstrict-prototypes -Wshadow -Wmissing-declarations -g -O3
Relocating allocator for buffers: no
GNU version of malloc: yes
- Using Doug Lea's new malloc from the GNU C Library.
Window System:
Compiling in support for the X window system:
- X Windows headers location: /usr/X11R6/include
- X Windows libraries location: /usr/X11R6/lib
- Handling WM_COMMAND properly.
Compiling in support for the Athena widget set:
- Athena headers location: X11/Xaw3d
- Athena library to link: Xaw3d
Using Lucid menubars.
Using Lucid scrollbars.
Using Athena dialog boxes.
Using Athena native widgets.
TTY:
Compiling in support for ncurses.
Compiling in support for GPM (General Purpose Mouse).
Images:
Compiling in support for GIF images (builtin).
Compiling in support for XPM images.
Compiling in support for PNG images.
Compiling in support for JPEG images.
Compiling in support for TIFF images.
Compiling in support for X-Face message headers.
Sound:
Compiling in support for sound (native).
Compiling in support for NAS (network audio system).
Databases:
Compiling in support for Berkeley database.
Compiling in support for PostgreSQL.
- Using PostgreSQL header file: postgresql/libpq-fe.h
- Using PostgreSQL V7 bindings.
Internationalization:
Compiling in support for Mule (multi-lingual Emacs).
Compiling in support for XIM (X11R5+ I18N input method).
- Using raw Xlib to provide XIM support.
- Using XFontSet to provide bilingual menubar.
Compiling in support for Canna on Mule.
Compiling in support for the WNN input method on Mule.
Mail:
Compiling in support for "dot-locking" mail spool file locking method.
Other Features:
Inhibiting IPv6 canonicalization at startup.
Compiling in support for dynamic shared object modules.
Using the union type for Lisp_Objects.
WARNING: ---------------------------------------------------------
WARNING: This tends to trigger compiler bugs, especially when
WARNING: combined with MULE and ERROR_CHECKING. Crashes have
WARNING: been seen with various versions of GCC, and recently
WARNING: with Visual C++ as well.
WARNING: ---------------------------------------------------------
WARNING: Use of the union type may cause crashes due to compiler bugs.
Using the new GC algorithms.
Using the new portable dumper.
Compiling in support for extra debugging code.
WARNING: ---------------------------------------------------------
WARNING: Compiling in support for runtime error checking.
WARNING: XEmacs will run noticeably more slowly as a result.
WARNING: Error checking is on by default for XEmacs beta releases.
WARNING: ---------------------------------------------------------
--
Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.
- 1 participants
- 0 comments
AW: [OT] to bell (was: why does M-w (kill-ring-save) hurt so bad? )
21 years, 4 months
Schmitt, Christian (ext.)
Schmitt, Christian (ext.)
Hi,
this is what dict.org returned for me (and it does make sense to me now :-)
bell the cat
v : take a risk; perform a daring act; "Who is going to bell the
cat?"
Cheers,
Christian Schmitt
> -----Ursprüngliche Nachricht-----
> Von: sperber(a)informatik.uni-tuebingen.de
> [mailto:sperber＠informatik.uni-tuebingen.de]
> Gesendet: Donnerstag, 19. Dezember 2002 11:28
> An: Norbert Koch
> Cc: Stephen J. Turnbull; xemacs-beta(a)xemacs.org
> Betreff: Re: [OT] to bell (was: why does M-w (kill-ring-save) hurt so
> bad?)
>
>
> >>>>> "viteno" == Norbert Koch <nk(a)viteno.net> writes:
>
> viteno> sperber(a)informatik.uni-tuebingen.de (Michael Sperber
> [Mr. Preprocessor]) writes:
>
> viteno> Hi!
>
> Stephen> So who's going to bell the cat?
> viteno> >
> >> This is beyond my understanding of English. :-) Could you rephrase?
>
> viteno> http://www.dict.org/ is your friend :-)
>
> viteno> >From Webster's Revised Unabridged Dictionary (1913) :
>
> viteno> Bell \Bell\, v. t. [imp. & p. p. Belled; p. pr. & vb. n.
> viteno> Belling.]
> viteno> To put a bell upon; as, to bell the cat.
>
> Not that this helps my understanding ... :-)
>
> --
> Cheers =8-} Mike
> Friede, Völkerverständigung und überhaupt blabla
>
- 1 participants
- 0 comments
50% decrease in Consumers Supply of Cash forecasted for the coming year
21 years, 4 months
margaret
margaret
The 50% decrease in Consumers cash in forcast. Decrease in money supply is based on less refinancing, raising interest rates, house-price appreciation slows, the number of potential borrowers shrinks, and consumers worry about their jobs. From Bloomberg News and Los Angeles Time
Jump Start your Sales now or possibly suffer layoffs or even lose your Business
E-Commerce within an eMail can generate 3x higher click-through rates From Internet World (Industry news resource)
eMail Marketing
The Average Customer Response time is 1-5 days. Compare this to 1-7 weeks with Postal advertisement.
Send 20 Targeted Interactive Advertisements to Customers that meet your targeted Demographics for the cost of 1 pieces of Direct Postal Mail
Targeted eMail marketing is a faster, better, and a more cost effective way to Reach your customers for less. Kick start your Sales today!
For less then the cost of a United States Postage Stamp DirectServices provides:
Custom Developed Customer list Targeting your Customers specific Demographics (such as Income, Location, Profession, etc...)
Designs your Dynamic and interactive Advertisement (HTML Design with pictures, Text, and HTML FORM [typing Fields] compatible with all Computer types)
Managed Delivery of Advertisements by Certified Engineers
Marketing Success Report, noting confirmed delivery time, Customers email address, and even when your advertisement was opened by the Customer (subject to availability)
To Start Advertising now, request more information, or to speak with a network engineer please call 310-937-6368 or Request on online:
Your Name:
E-mail Address:
Business Phone:
Company Name:
State: Choose One Alabama Alaska Arizona Arkansas California Colorado Connecticut Washington D.C. Delaware Florida Georgia Hawaii Idaho Illinois Indiana Iowa Kansas Kentucky Louisiana Maine Maryland Massachusetts Michigan Minnesota Mississippi Missouri Montana Nebraska Nevada New Hampshire New Jersey New Mexico New York North Carolina North Dakota Ohio Oklahoma Oregon Pennsylvania Puerto Rico Rhode Island South Carolina South Dakota Tennessee Texas Utah Vermont Virginia Washington West Virginia Wisconsin Wyoming
Best time to call: Please Choose Best Time Morning Afternoon Evening
Web Site:
Services of Interest:
Choose all that apply by holding your CONTROL key down, and clicking to select multiple items.
Marketing Service... Mortgage leads... Web Hosting Services Business eMail Accounts Meta Tag Generator URL Tranz Insurance Leads
In which states do
you do Business?
Hold your CONTROL key down, and click to select multiple states
All 50 States All 50 states and Abroad CA-California AK-Alaska AL-Alabama AR-Arkansas AZ-Arizona CO-Colorado CT-Connecticut DC-District of Columbia DE-Delaware FL-Florida GA-Georgia HI-Hawaii ID-Idaho IL-Illinois IN-Indiana IA-Iowa KS-Kansas KY-Kentucky LA-Louisiana MA-Massachusetts MD-Maryland ME-Maine MI-Michigan MN-Minnesota MO-Missouri MS-Mississippi MT-Montana NC-North Carolina ND-North Dakota NE-Nebraska NV-Nevada NH-New Hampshire NJ-New Jersey NM-New Mexico NY-New York OH-Ohio OK-Oklahoma OR-Oregon PA-Pennsylvania RI-Rhode Island SC-South Carolina SD-South Dakota TN-Tennessee TX-Texas UT-Utah VT-Vermont VA-Virginia WA-Washington WI-Wisconsin WV-West Virgina WY-Wyoming
Special Requirements? Comments?
Thank you! You will be contacted within 24 hours.
Clicking Submit will eMail this information to Direct Services
Information on Marketing is being sent to you as part of a free Business Development Service.
Please distribute this newsletter freely; however, we ask that you not change its contents.
To Continue to Subscribe: To be included in future newsletters, please Click here to send an eMail Confirmation with "subscribe" as the subject.
To Unsubscribe: To unsubscribe, please Click here to send an eMail Confirmation with "unsubscribe or remove" as the subject.
Customer Service: To eMail Customer Service Click here
- 1 participants
- 0 comments
Click on url doesn't work (intermittent)
21 years, 4 months
Laura Conrad
Laura Conrad
In gnus, I'm used to being able to click the right or middle mouse
button over a URL and have my browser of choice (currently mozilla,
with a link in /usr/bin named netscape) take me there.
In my debian xemacs, intermittently it gets into a state where either
button produces a message:
Buffer changed during mouse motion
and nothing is sent to a browser.
- 2 participants
- 1 comments