Problems with byte compiled startup files
Stephen J. Turnbull
stephen at xemacs.org
Tue Oct 28 12:19:11 EDT 2008
Mike FABIAN writes:
> I found now that it indeed happens only on 64-bit.
> I cannot see any warnings which seem to be related. bytecode.c compiles
> without warnings.
Comparing the 64-bit/32-bit attachments, pretty clearly it's not
directly a 64-bit problem as such. The 32-bit-compiled file is OK,
but for some reason the 64-bit-compiled file is being saved in UTF-8.
Which is *not* supposed to happen, ever. Byte-compiled files are
supposed to be saved in binary or a special escape-quoted encoding.
Why 64-bit-ness would affect this, I don't know. These are both the
same SuSE sources, right?
I don't have a patch, yet, since I don't know why this is happening.
buffer-file-coding-system is forced to raw-text or escape-quoted in
byte-compile-insert-header (lisp/bytecomp.el). Apparently something
is overriding that. You could try putting a Lisp debugger breakpoint
on write-region before byte-compiling, then checking the value of that
Is latin-unity active? I notice that -vanilla seems to help. Do you
have anything in the site-start or default.el files? (Those don't
seem to be available directly on build.opensuse.org.) I can't think
of anything else offhand that would override buffer-file-coding-system.
More information about the XEmacs-Beta