Changeset 4204 for trunk/etc/PROBLEMS
- Timestamp:
- 05/01/07 18:04:59 (2 years ago)
- Files:
-
- trunk/etc/PROBLEMS (modified) (14 diffs)
Legend:
- Unmodified
- Added
- Removed
- Modified
- Copied
- Moved
trunk/etc/PROBLEMS
r4200 r4204 214 214 http://bugzilla.gnome.org/show_bug.cgi?id=85715. 215 215 216 ** Emacs compiled with Gtk+ crashes on startup on cygwin.216 ** Emacs compiled with Gtk+ crashes on startup on Cygwin. 217 217 218 218 A typical error message is … … 221 221 222 222 Emacs supplies its own malloc, but glib (part of Gtk+) calls memalign and on 223 cygwin that becomes the cygwin supplied memalign. As malloc is not the224 cygwin malloc, the cygwin memalign always returns ENOSYS. A fix for this223 Cygwin, that becomes the Cygwin supplied memalign. As malloc is not the 224 Cygwin malloc, the Cygwin memalign always returns ENOSYS. A fix for this 225 225 problem would be welcome. 226 226 … … 387 387 *** Emacs does not know your host's fully-qualified domain name. 388 388 389 For example, (system-name) returns some variation on 390 "localhost.localdomain", rather the name you were expecting. 391 389 392 You need to configure your machine with a fully qualified domain name, 390 either in /etc/hosts, /etc/hostname, the NIS, or wherever your system 391 calls for specifying this. 393 (i.e. a name with at least one ".") either in /etc/hosts, 394 /etc/hostname, the NIS, or wherever your system calls for specifying 395 this. 392 396 393 397 If you cannot fix the configuration, you can set the Lisp variable … … 1199 1203 1200 1204 Only the Motif 1.2 emulation seems to be stable enough in LessTif. 1201 Less tif 0.92-17's Motif 1.2 emulation seems to work okay on FreeBSD.1205 LessTif 0.92-17's Motif 1.2 emulation seems to work okay on FreeBSD. 1202 1206 On GNU/Linux systems, lesstif-0.92.6 configured with "./configure 1203 1207 --enable-build-12 --enable-default-12" is reported to be the most … … 1296 1300 of the X protocol. lbxproxy acheives the performance gain by grouping 1297 1301 several X requests in one TCP packet and sending them off together, 1298 instead of requiring a round-trip for each X request in a sep erate1302 instead of requiring a round-trip for each X request in a separate 1299 1303 packet. The switches that seem to work best for emacs are: 1300 1304 -noatomsfile -nowinattr -cheaterrors -cheatevents … … 1402 1406 in your site-init.el file. 1403 1407 1404 * Runtime problems on character term unals1408 * Runtime problems on character terminals 1405 1409 1406 1410 ** Emacs spontaneously displays "I-search: " at the bottom of the screen. … … 2103 2107 for menus. Help text is only available in later versions of Windows. 2104 2108 2109 When "ClearType" method is selected as the "method to smooth edges of 2110 screen fonts" (in Display Properties, Appearance tab, under 2111 "Effects"), there are various problems related to display of 2112 characters: 2-pixel trace is left behind when moving overlays, bold 2113 fonts can be hard to read, small portions of some characters could 2114 appear chopped, etc. This happens because, under ClearType, 2115 characters are drawn outside their advertised bounding box. Emacs 21 2116 disabled the use of ClearType, whereas Emacs 22 allows it and has some 2117 code to enlarge the width of the bounding box. Apparently, this 2118 display feature needs more changes to get it 100% right. A workaround 2119 is to disable ClearType. 2120 2105 2121 There are problems with display if mouse-tracking is enabled and the 2106 2122 mouse is moved off a frame, over another frame then back over the first … … 2114 2130 Manager driven switch of the focus, until a key is pressed. 2115 2131 2116 Windows input methods are not recognized by Emacs. Some2132 Windows input methods are not recognized by Emacs. However, some 2117 2133 of these input methods cause the keyboard to send characters encoded 2118 2134 in the appropriate coding system (e.g., ISO 8859-1 for Latin-1 2119 characters, ISO 8859-8 for Hebrew characters, etc.). To make this 2120 work, set the keyboard coding system to the appropriate value after 2121 you activate the Windows input method. For example, if you activate 2122 the Hebrew input method, type "C-x RET k iso-8859-8 RET". (Emacs 2123 ought to recognize the Windows language-change event and set up the 2124 appropriate keyboard encoding automatically, but it doesn't do that 2125 yet.) 2135 characters, ISO 8859-8 for Hebrew characters, etc.). To make these 2136 input methods work with Emacs, set the keyboard coding system to the 2137 appropriate value after you activate the Windows input method. For 2138 example, if you activate the Hebrew input method, type this: 2139 2140 C-x RET k hebrew-iso-8bit RET 2141 2142 (Emacs ought to recognize the Windows language-change event and set up 2143 the appropriate keyboard encoding automatically, but it doesn't do 2144 that yet.) In addition, to use these Windows input methods, you 2145 should set your "Language for non-Unicode programs" (on Windows XP, 2146 this is on the Advanced tab of Regional Settings) to the language of 2147 the input method. 2126 2148 2127 2149 To bind keys that produce non-ASCII characters with modifiers, you … … 2139 2161 of Windows. This is caused by a deficiency in the underlying system 2140 2162 library function. 2163 2164 Files larger than 4GB cause overflow in the size (represented as a 2165 32-bit integer) reported by `file-attributes'. This affects Dired as 2166 well, since the Windows port uses a Lisp emulation of `ls' that relies 2167 on `file-attributes'. 2141 2168 2142 2169 ** Typing Alt-Shift has strange effects on MS-Windows. … … 2307 2334 2308 2335 This was reported to happen when building Emacs on a GNU/Linux system 2309 (Red Hat Linux 6.2) using a build directory automounted from Solaris2336 (Red Hat Linux 6.2) using a build directory automounted from Solaris 2310 2337 (SunOS 5.6) file server, but it might not be limited to that 2311 2338 configuration alone. Presumably, the NFS server doesn't commit the … … 2394 2421 (using the location of the 32-bit X libraries on your system). 2395 2422 2396 *** Building the Cygwin port for MS-Windows can fail with some GCC version 2423 *** Building the Cygwin port for MS-Windows can fail with some GCC versions 2397 2424 2398 2425 Building Emacs 22 with Cygwin builds of GCC 3.4.4-1 and 3.4.4-2 is … … 2400 2427 addition, the Cygwin GCC 3.4.4-2 has problems with generating debug 2401 2428 info. Cygwin users are advised not to use these versions of GCC for 2402 compiling Emacs. GCC versions 4.0.3, 4. 1.1, and 4.1.2 reportedly2403 build a working Cygwin binary of Emacs, so we recommend these GCC 2404 versions. Note that these three versions of GCC, 4.0.3, 4.1.1, and 2405 4.1. 2, are currently the _only_ versions known to succeed in building2406 Emacs (as of v22.1).2429 compiling Emacs. GCC versions 4.0.3, 4.0.4, 4.1.1, and 4.1.2 2430 reportedly build a working Cygwin binary of Emacs, so we recommend 2431 these GCC versions. Note that these versions of GCC, 4.0.3, 4.0.4, 2432 4.1.1, and 4.1.2, are currently the _only_ versions known to succeed 2433 in building Emacs (as of v22.1). 2407 2434 2408 2435 *** Building the native MS-Windows port with Cygwin GCC can fail. … … 2555 2582 *** Linux: Segfault during `make bootstrap' under certain recent versions of the Linux kernel. 2556 2583 2557 With certain recent Linux kernels (like the one of Red hat Fedora Core2584 With certain recent Linux kernels (like the one of Red Hat Fedora Core 2558 2585 1 and newer), the new "Exec-shield" functionality is enabled by default, which 2559 2586 creates a different memory layout that breaks the emacs dumper. Emacs tries … … 2731 2758 Using directory paths with spaces is not supported at this time: you 2732 2759 must re-configure without using spaces. 2760 2761 *** On Solaris, use GNU Make when installing an out-of-tree build 2762 2763 The Emacs configuration process allows you to configure the 2764 build environment so that you can build emacs in a directory 2765 outside of the distribution tree. When installing Emacs from an 2766 out-of-tree build directory on Solaris, you may need to use GNU 2767 make. The make programs bundled with Solaris support the VPATH 2768 macro but use it differently from the way the VPATH macro is 2769 used by GNU make. The differences will cause the "make install" 2770 step to fail, leaving you with an incomplete emacs 2771 installation. GNU make is available in /usr/sfw/bin on Solaris 2772 10 and can be installed as /opt/sfw/bin/gmake from the Solaris 9 2773 Software Companion CDROM. 2774 2775 The problems due to the VPATH processing differences affect only 2776 out of tree builds so, if you are on a Solaris installation 2777 without GNU make, you can install Emacs completely by installing 2778 from a build environment using the original emacs distribution tree. 2733 2779 2734 2780 ** First execution
