Current CVS Mule 21.2 crashes (on X only?)

I WILL NOT APPLY without support from someone who knows what's going on here. Stephen> In CVS current, Mule on X crashes immediately. This may Stephen> be related to Japanese hardware; the keysym that blows up Stephen> is 1223 decimal, which puts it in the KATAKANA_JISX0201 Stephen> range. (Cf x_keysym_to_character(), src/event-Xt.c:211.) This seems to fix but I don't understand why. x_keysym_to_character() from src/events-Xt.c should call this macro with a value that was originally an enum constant (ie, int) LEADING_BYTE_KATAKANA_JISX0201 == 0x89 from src/mule-charset.h. This should fit into a Bufbyte (typedef for unsigned char), right? GCC bug, maybe? $ gcc --version 2.95.2 # debian woody (unstable) $ dpkg -l gcc ||/ Name Version Description +++-==============-==============-============================================ ii gcc 2.95.2-14 The GNU C compiler. src/ChangeLog: 2000-11-04 Stephen J. Turnbull <stephen(a)xemacs.org&gt; * mule-charset.h: Change type of argument of CHARSET_BY_LEADING_BYTE back to int (fixes <14851.51148.36400.105153(a)turnbull.sk.tsukuba.ac.jp>) Index: src/mule-charset.h =================================================================== RCS file: /usr/CVSroot/XEmacs/xemacs/src/mule-charset.h,v retrieving revision 1.7.2.16 diff -u -r1.7.2.16 mule-charset.h --- mule-charset.h 2000/10/12 04:59:05 1.7.2.16 +++ mule-charset.h 2000/11/04 08:43:26 ＠＠ -560,9 +560,9 ＠＠ Bufbyte next_allocated_2_byte_leading_byte; }; -INLINE_HEADER Lisp_Object CHARSET_BY_LEADING_BYTE (Bufbyte lb); +INLINE_HEADER Lisp_Object CHARSET_BY_LEADING_BYTE (int lb); INLINE_HEADER Lisp_Object -CHARSET_BY_LEADING_BYTE (Bufbyte lb) +CHARSET_BY_LEADING_BYTE (int lb) { extern struct charset_lookup *chlook; -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 _________________ _________________ _________________ _________________ What are those straight lines for? "XEmacs rules."