Re: 21.0.63 crash in xlw_menubar init for bad locale
"Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes:
In XEmacs 21.0 "Pyrenean63" [Lucid] (i586-pc-linux, Mule)
of Fri Feb 5 1999 on tanko
configured using `configure --prefix=/playpen/gnu --exec-prefix=/playpen/gnu/plat
--with-mule --with-xim=xlib --with-xfs --with-sound=both --use-union-type=yes --debug
--gung-ho=yes '--cflags=-g -O3 -fno-caller-saves -Wall -Wno-switch''
There's something wrong with my Debian `unstable' system, and it
doesn't seem to have a C/POSIX locale. !! This results in "X doesn't
even support C locale" message, of course, and the following crash and
backtrace. This is probably an Xlib or Xt bug in the current
development tree, but maybe XEmacs can work around it? Broken locales
are going to be common on Linux systems (Japanese, anyway) as glibc is
looking like it might finally support widechar locales properly in the
near future. I'm not particularly confident that the various
distributions will get this right in the first releases....
In my environment, setting LC_ALL=<any available locale> works fine.
I will try to rebuild without XFS since the code in input-method-xfs.c
seems to be duplicated in input-method-xlib.c, and maybe this causes
some weirdness.
Yes, the a part of code is duplicated (Initialize_Locale).
The input-method-xfs is prepared for a people who never want to use X
input method but egg or canna.
If you'd like to use X input method, please set --with-xim=xlib only.
By the way, the object code in xemacs won't be duplicated because
whenever you specified both xlib and xfs, the input-method-xlib.c will
be compiled and linked with, and input-method-xfs.c won't.
Actually, the Installation file says it will use XFontSet feature, but
the resulting src/Makefile won't include input-method-xfs.o in
$extra_objs I believe.
This will make people confusing so the configure need to be fixed.
steve＠tanko:/playpen$ xemacs
X Windows does not support locale `C'
Using C Locale instead
X Windows does not even support locale `C'!
Warning: XOpenIM() failed...no input server available
Warning: Unable to load any usable fontset
Fatal error (11).
Your files have been auto-saved.
Use `M-x recover-session' to recover them.
How about that when you did not specify --with-xim=xlib but just
--with-xfs?
....
Compiling in support for ncurses.
Compiling in Mule (multi-lingual) support.
Compiling in XIM (X11R5+ I18N input method) support.
Using raw Xlib to provide XIM support.
Using XFontSet to provide bilingual menubar.
Compiling in support for Canna on Mule.
Compiling in support for proper session-management.