view BUGS @ 109732:470bed744331

Use autoconf determined WORDS_BIGENDIAN instead of hardcoded definition. * m/alpha.h: Don't define/undef WORDS_BIG_ENDIAN. * m/amdx86-64.h: Likewise. * m/arm.h: Likewise. * m/hp800.h: Likewise. * m/ia64.h: Likewise. * m/ibmrs6000.h: Likewise. * m/ibms390.h: Likewise. * m/intel386.h: Likewise. * m/iris4d.h: Likewise. * m/m68k.h: Likewise. * m/macppc.h: Likewise. * m/mips.h: Likewise. * m/sh3.h: Likewise. * m/sparc.h: Likewise. * m/template.h: Likewise. * m/vax.h: Likewise. * m/xtensa.h: Likewise. * fringe.c (init_fringe_bitmap): Test WORDS_BIGENDIAN instead of WORDS_BIG_ENDIAN. * lisp.h: Likewise. * md5.c: Likewise. * sound.c (le2hl, le2hs, be2hl, be2hs): Likewise. * CPP-DEFINES (WORDS_BIG_ENDIAN): Remove. * configure.in: Add AC_C_BIGENDIAN.
author Andreas Schwab <schwab@linux-m68k.org>
date Mon, 09 Aug 2010 21:25:41 +0200
parents fb8bf24d2eb9
children ac52af4a044c
line wrap: on
line source

If you think you may have found a bug in GNU Emacs, please
read the Bugs section of the Emacs manual for advice on
(1) how to tell when to report a bug, and
(2) how to write a useful bug report and what information
it needs to have.

There are three ways to read the Bugs section.

(1) In a printed copy of the Emacs manual.
You can order one from the Free Software Foundation;
see the file etc/ORDERS.  But if you don't have a copy on
hand and you think you have found a bug, you shouldn't wait
to get a printed manual; you should read the section right away
as described below.

(2) With Info.  Start Emacs, do C-h i to enter Info,
then m Emacs RET to get to the Emacs manual, then m Bugs RET
to get to the section on bugs.  Or use standalone Info in
a like manner.  (Standalone Info is part of the Texinfo distribution,
not part of the Emacs distribution.)

(3) By hand.  Do
    cat info/emacs* | more "+/^File: emacs,  Node: Bugs,"

Please first check the file etc/PROBLEMS (e.g. with C-h C-p in Emacs) to
make sure it isn't a known issue.