On Tue, 21 Aug 2001, Ben Wing wrote:
I'm looking for testers. There is a complete and fast
implementation
in C of Unicode conversion, translations for almost all of the
standardly-defined charsets that load up automatically and
instantaneously at runtime, coding systems supporting the common
external representations of Unicode [utf-16, ucs-4, utf-8,
little-endian versions of utf-16 and ucs-4; utf-7 is sitting there
with abort[]s where the coding routines should go, just waiting for
somebody to implement], and a nice set of primitives for translating
characters<->codepoints and setting the priority lists used to control
codepoint->char lookup.
[...]
Ben, the build fails for me with a segfault in temacs. I made a few
changes to make it compile at all under my Linux installation; the diff
against CVS is attached.
The various bits and pieces of output, including the build logs and the
gdb backtrace of the error, are included. If I can do anything further
to assist in the testing, let me know.
Oh, it's worth noting that I bumped the beta version up to 200 for this
testing; I didn't want to tromp my working XEmacs when I installed... :)
One point of note, at a user level, is that you seem to define the
coding system `utf8'. Gnus, the one real user of UTF-8 coding that I
know of, looks for coding systems named either `mule-utf-8' or `utf-8'.
It would be good to ensure that, at the least, XEmacs and GNU Emacs were
in sync on this; I believe (but can't verify) that the `utf-8' style is
used there...
So, the differences between the version I used, which builds as far as
temacs, and your branch in CVS:
The Installation file:
The output of the make process:
The gdb output showing the stack when the failure occurred:
Daniel
--
I read about an Eskimo hunter who asked the local missionary priest, "If I did
not know about God and sin, would I go to hell? 'No,' said the priest, 'not
if
you did not know.' 'Then why,' asked the Eskimo earnestly, 'did you tell
me?
-- Annie Dillard