[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Emacs-diffs] Changes to emacs/etc/PROBLEMS [lexbind]
From: |
Miles Bader |
Subject: |
[Emacs-diffs] Changes to emacs/etc/PROBLEMS [lexbind] |
Date: |
Wed, 15 Sep 2004 20:42:38 -0400 |
Index: emacs/etc/PROBLEMS
diff -c emacs/etc/PROBLEMS:1.129.2.10 emacs/etc/PROBLEMS:1.129.2.11
*** emacs/etc/PROBLEMS:1.129.2.10 Sat Sep 4 09:26:20 2004
--- emacs/etc/PROBLEMS Thu Sep 16 00:12:17 2004
***************
*** 1,5 ****
This file describes various problems that have been encountered
! in compiling, installing and running GNU Emacs. Try doing Ctl t
and browsing through the outline headers.
* Emacs startup failures
--- 1,5 ----
This file describes various problems that have been encountered
! in compiling, installing and running GNU Emacs. Try doing Ctl-C Ctl-t
and browsing through the outline headers.
* Emacs startup failures
***************
*** 156,185 ****
Patches to raise the stack size limit automatically in `main'
(src/emacs.c) on various systems would be greatly appreciated.
- ** Emacs crashes with SIGBUS or SIGSEGV on HPUX 9 after you delete a frame.
-
- We think this is due to a bug in the X libraries provided by HP. With
- the alternative X libraries in /usr/contrib/mitX11R5/lib, the problem
- does not happen.
-
- ** Emacs crashes with SIGBUS or SIGSEGV on Solaris after you delete a frame.
-
- We suspect that this is a similar bug in the X libraries provided by
- Sun. There is a report that one of these patches fixes the bug and
- makes the problem stop:
-
- 105216-01 105393-01 105518-01 105621-01 105665-01 105615-02 105216-02
- 105667-01 105401-08 105615-03 105621-02 105686-02 105736-01 105755-03
- 106033-01 105379-01 105786-01 105181-04 105379-03 105786-04 105845-01
- 105284-05 105669-02 105837-01 105837-02 105558-01 106125-02 105407-01
-
- Another person using a newer system (kernel patch level Generic_105181-06)
- suspects that the bug was fixed by one of these more recent patches:
-
- 106040-07 SunOS 5.6: X Input & Output Method patch
- 106222-01 OpenWindows 3.6: filemgr (ff.core) fixes
- 105284-12 Motif 1.2.7: sparc Runtime library patch
-
** Error message `Symbol's value as variable is void: x', followed by
a segmentation fault and core dump.
--- 156,161 ----
***************
*** 1272,1286 ****
-query' to see what resources the X server records, and also look at
the user's ~/.Xdefaults and ~/.Xdefaults-* files.
- *** --with-x-toolkit version crashes when used with shared libraries.
-
- On some systems, including Sunos 4 and DGUX 5.4.2 and perhaps others,
- unexec doesn't work properly with the shared library for the X
- toolkit. You might be able to work around this by using a nonshared
- libXt.a library. The real fix is to upgrade the various versions of
- unexec and/or ralloc. We think this has been fixed on Sunos 4
- and Solaris in version 19.29.
-
*** Emacs running under X Windows does not handle mouse clicks.
*** `emacs -geometry 80x20' finds a file named `80x20'.
--- 1248,1253 ----
***************
*** 1794,1808 ****
If this happens to you, extend the timeout period.
- *** HP/UX: Emacs is slow using X11R5.
-
- This happens if you use the MIT versions of the X libraries--it
- doesn't run as fast as HP's version. People sometimes use the version
- because they see the HP version doesn't have the libraries libXaw.a,
- libXmu.a, libXext.a and others. HP/UX normally doesn't come with
- those libraries installed. To get good performance, you need to
- install them and rebuild Emacs.
-
*** HP/UX: The right Alt key works wrong on German HP keyboards (and perhaps
other non-English HP keyboards too).
--- 1761,1766 ----
***************
*** 1849,1858 ****
EOF
--------------------------------
- *** HP/UX: Large file support is disabled.
-
- See the comments in src/s/hpux10.h.
-
*** HP/UX 11.0: Emacs makes HP/UX 11.0 crash.
This is a bug in HPUX; HPUX patch PHKL_16260 is said to fix it.
--- 1807,1812 ----
***************
*** 1873,1909 ****
This makes your Backspace key send DEL (ASCII 127).
- *** AIX: You get this message when running Emacs:
-
- Could not load program emacs
- Symbol smtcheckinit in csh is undefined
- Error was: Exec format error
-
- or this one:
-
- Could not load program .emacs
- Symbol _system_con in csh is undefined
- Symbol _fp_trapsta in csh is undefined
- Error was: Exec format error
-
- These can happen when you try to run on AIX 3.2.5 a program that was
- compiled with 3.2.4. The fix is to recompile.
-
- *** AIX 3.2.4: Releasing Ctrl/Act key has no effect, if Shift is down.
-
- Due to a feature of AIX, pressing or releasing the Ctrl/Act key is
- ignored when the Shift, Alt or AltGr keys are held down. This can
- lead to the keyboard being "control-locked"--ordinary letters are
- treated as control characters.
-
- You can get out of this "control-locked" state by pressing and
- releasing Ctrl/Act while not pressing or holding any other keys.
-
- *** AIX 4.2: Emacs gets a segmentation fault at startup.
-
- If you are using IBM's xlc compiler, compile emacs.c
- without optimization; that should avoid the problem.
-
*** AIX: If linking fails because libXbsd isn't found, check if you
are compiling with the system's `cc' and CFLAGS containing `-O5'. If
so, you have hit a compiler bug. Please make sure to re-configure
--- 1827,1832 ----
***************
*** 1940,1966 ****
is because the unshared libraries fail to use YP for host name lookup.
As a result, the host name you specify may not be recognized.
! *** Emacs reports a BadAtom error (from X) running on Solaris 7 or 8.
!
! This happens when Emacs was built on some other version of Solaris.
! Rebuild it on Solaris 8.
!
! *** On Solaris, CTRL-t is ignored by Emacs when you use
! the fr.ISO-8859-15 locale (and maybe other related locales).
!
! You can fix this by editing the file:
! /usr/openwin/lib/locale/iso8859-15/Compose
! Near the bottom there is a line that reads:
! Ctrl<t> <quotedbl> <Y> : "\276" threequarters
! that should read:
! Ctrl<T> <quotedbl> <Y> : "\276" threequarters
! Note the lower case <t>. Changing this line should make C-t work.
*** When using M-x dbx with the SparcWorks debugger, the `up' and `down'
commands do not move the arrow in Emacs.
--- 1863,1890 ----
is because the unshared libraries fail to use YP for host name lookup.
As a result, the host name you specify may not be recognized.
! *** Solaris 2,6: Emacs crashes with SIGBUS or SIGSEGV on Solaris after you
delete a frame.
! We suspect that this is a bug in the X libraries provided by
! Sun. There is a report that one of these patches fixes the bug and
! makes the problem stop:
! 105216-01 105393-01 105518-01 105621-01 105665-01 105615-02 105216-02
! 105667-01 105401-08 105615-03 105621-02 105686-02 105736-01 105755-03
! 106033-01 105379-01 105786-01 105181-04 105379-03 105786-04 105845-01
! 105284-05 105669-02 105837-01 105837-02 105558-01 106125-02 105407-01
! Another person using a newer system (kernel patch level Generic_105181-06)
! suspects that the bug was fixed by one of these more recent patches:
! 106040-07 SunOS 5.6: X Input & Output Method patch
! 106222-01 OpenWindows 3.6: filemgr (ff.core) fixes
! 105284-12 Motif 1.2.7: sparc Runtime library patch
! *** Solaris 7 or 8: Emacs reports a BadAtom error (from X)
! This happens when Emacs was built on some other version of Solaris.
! Rebuild it on Solaris 8.
*** When using M-x dbx with the SparcWorks debugger, the `up' and `down'
commands do not move the arrow in Emacs.
***************
*** 1969,2108 ****
dbxenv output_short_file_name off
! ** Irix
!
! *** Irix 5.2: unexelfsgi.c can't find cmplrs/stsupport.h.
!
! The file cmplrs/stsupport.h was included in the wrong file set in the
! Irix 5.2 distribution. You can find it in the optional fileset
! compiler_dev, or copy it from some other Irix 5.2 system. A kludgy
! workaround is to change unexelfsgi.c to include sym.h instead of
! syms.h.
!
! *** Irix 5.3: "out of virtual swap space".
!
! This message occurs when the system runs out of swap space due to too
! many large programs running. The solution is either to provide more
! swap space or to reduce the number of large programs being run. You
! can check the current status of the swap space by executing the
! command `swap -l'.
!
! You can increase swap space by changing the file /etc/fstab. Adding a
! line like this:
!
! /usr/swap/swap.more swap swap pri=3 0 0
!
! where /usr/swap/swap.more is a file previously created (for instance
! by using /etc/mkfile), will increase the swap space by the size of
! that file. Execute `swap -m' or reboot the machine to activate the
! new swap area. See the manpages for `swap' and `fstab' for further
! information.
! The objectserver daemon can use up lots of memory because it can be
! swamped with NIS information. It collects information about all users
! on the network that can log on to the host.
! If you want to disable the objectserver completely, you can execute
! the command `chkconfig objectserver off' and reboot. That may disable
! some of the window system functionality, such as responding CDROM
! icons.
! You can also remove NIS support from the objectserver. The SGI `admin'
! FAQ has a detailed description on how to do that; see question 35
! ("Why isn't the objectserver working?"). The admin FAQ can be found at
! ftp://viz.tamu.edu/pub/sgi/faq/.
! *** Irix 5.3: Emacs crashes in utmpname.
! This problem is fixed in Patch 3175 for Irix 5.3.
! It is also fixed in Irix versions 6.2 and up.
! *** Irix 6.0: Make tries (and fails) to build a program named unexelfsgi.
! A compiler bug inserts spaces into the string "unexelfsgi . o"
! in src/Makefile. Edit src/Makefile, after configure is run,
! find that string, and take out the spaces.
! Compiler fixes in Irix 6.0.1 should eliminate this problem.
*** Irix 6.5: Emacs crashes on the SGI R10K, when compiled with GCC.
This seems to be fixed in GCC 2.95.
! *** Trouble using ptys on IRIX, or running out of ptys.
The program mkpts (which may be in `/usr/adm' or `/usr/sbin') needs to
be set-UID to root, or non-root programs like Emacs will not be able
to allocate ptys reliably.
- ** SCO Unix and UnixWare
-
- *** SCO 3.2v4: Unusable default font.
-
- The Open Desktop environment comes with default X resource settings
- that tell Emacs to use a variable-width font. Emacs cannot use such
- fonts, so it does not work.
-
- This is caused by the file /usr/lib/X11/app-defaults/ScoTerm, which is
- the application-specific resource file for the `scoterm' terminal
- emulator program. It contains several extremely general X resources
- that affect other programs besides `scoterm'. In particular, these
- resources affect Emacs also:
-
- *Font: -*-helvetica-medium-r-*--12-*-p-*
- *Background: scoBackground
- *Foreground: scoForeground
-
- The best solution is to create an application-specific resource file for
- Emacs, /usr/lib/X11/sco/startup/Emacs, with the following contents:
-
- Emacs*Font: -*-courier-medium-r-*-*-*-120-*-*-*-*-iso8859-1
- Emacs*Background: white
- Emacs*Foreground: black
-
- (These settings mimic the Emacs defaults, but you can change them to
- suit your needs.) This resource file is only read when the X server
- starts up, so you should restart it by logging out of the Open Desktop
- environment or by running `scologin stop; scologin start` from the shell
- as root. Alternatively, you can put these settings in the
- /usr/lib/X11/app-defaults/Emacs resource file and simply restart Emacs,
- but then they will not affect remote invocations of Emacs that use the
- Open Desktop display.
-
- These resource files are not normally shared across a network of SCO
- machines; you must create the file on each machine individually.
-
- *** Regular expressions matching bugs on SCO systems.
-
- On SCO, there are problems in regexp matching when Emacs is compiled
- with the system compiler. The compiler version is "Microsoft C
- version 6", SCO 4.2.0h Dev Sys Maintenance Supplement 01/06/93; Quick
- C Compiler Version 1.00.46 (Beta). The solution is to compile with
- GCC.
-
- *** UnixWare 2.1: Error 12 (virtual memory exceeded) when dumping Emacs.
-
- Paul Abrahams (address@hidden) reports that with the installed
- virtual memory settings for UnixWare 2.1.2, an Error 12 occurs during
- the "make" that builds Emacs, when running temacs to dump emacs. That
- error indicates that the per-process virtual memory limit has been
- exceeded. The default limit is probably 32MB. Raising the virtual
- memory limit to 40MB should make it possible to finish building Emacs.
-
- You can do this with the command `ulimit' (sh) or `limit' (csh).
- But you have to be root to do it.
-
- According to Martin Sohnius, you can also retune this in the kernel:
-
- # /etc/conf/bin/idtune SDATLIM 33554432 ## soft data size limit
- # /etc/conf/bin/idtune HDATLIM 33554432 ## hard "
- # /etc/conf/bin/idtune SVMMSIZE unlimited ## soft process size limit
- # /etc/conf/bin/idtune HVMMSIZE unlimited ## hard "
- # /etc/conf/bin/idbuild -B
-
- (He recommends you not change the stack limit, though.)
- These changes take effect when you reboot.
-
* Runtime problems specific to MS-Windows
** Emacs exits with "X protocol error" when run with an X server for
MS-Windows.
--- 1893,1927 ----
dbxenv output_short_file_name off
! *** On Solaris, CTRL-t is ignored by Emacs when you use
! the fr.ISO-8859-15 locale (and maybe other related locales).
! You can fix this by editing the file:
! /usr/openwin/lib/locale/iso8859-15/Compose
! Near the bottom there is a line that reads:
! Ctrl<t> <quotedbl> <Y> : "\276" threequarters
! that should read:
! Ctrl<T> <quotedbl> <Y> : "\276" threequarters
! Note the lower case <t>. Changing this line should make C-t work.
! ** Irix
*** Irix 6.5: Emacs crashes on the SGI R10K, when compiled with GCC.
This seems to be fixed in GCC 2.95.
! *** Irix: Trouble using ptys, or running out of ptys.
The program mkpts (which may be in `/usr/adm' or `/usr/sbin') needs to
be set-UID to root, or non-root programs like Emacs will not be able
to allocate ptys reliably.
* Runtime problems specific to MS-Windows
** Emacs exits with "X protocol error" when run with an X server for
MS-Windows.
***************
*** 2153,2257 ****
of Windows. This is caused by a deficiency in the underlying system
library function.
! ** Problems running Perl under Emacs on MS-Windows NT/95.
! `perl -de 0' just hangs when executed in an Emacs subshell.
! The fault lies with Perl (indirectly with Windows NT/95).
! The problem is that the Perl debugger explicitly opens a connection to
! "CON", which is the DOS/NT equivalent of "/dev/tty", for interacting
! with the user.
! On Unix, this is okay, because Emacs (or the shell?) creates a
! pseudo-tty so that /dev/tty is really the pipe Emacs is using to
! communicate with the subprocess.
! On NT, this fails because CON always refers to the handle for the
! relevant console (approximately equivalent to a tty), and cannot be
! redirected to refer to the pipe Emacs assigned to the subprocess as
! stdin.
! A workaround is to modify perldb.pl to use STDIN/STDOUT instead of CON.
! For Perl 4:
!
! *** PERL/LIB/PERLDB.PL.orig Wed May 26 08:24:18 1993
! --- PERL/LIB/PERLDB.PL Mon Jul 01 15:28:16 1996
! ***************
! *** 68,74 ****
! $rcfile=".perldb";
! }
! else {
! ! $console = "con";
! $rcfile="perldb.ini";
! }
!
! --- 68,74 ----
! $rcfile=".perldb";
! }
! else {
! ! $console = "";
! $rcfile="perldb.ini";
! }
!
!
! For Perl 5:
! *** perl/5.001/lib/perl5db.pl.orig Sun Jun 04 21:13:40 1995
! --- perl/5.001/lib/perl5db.pl Mon Jul 01 17:00:08 1996
! ***************
! *** 22,28 ****
! $rcfile=".perldb";
! }
! elsif (-e "con") {
! ! $console = "con";
! $rcfile="perldb.ini";
! }
! else {
! --- 22,28 ----
! $rcfile=".perldb";
! }
! elsif (-e "con") {
! ! $console = "";
! $rcfile="perldb.ini";
! }
! else {
!
! ** On MS-Windows 95, Alt-f6 does not get through to Emacs.
!
! This character seems to be trapped by the kernel in Windows 95.
! You can enter M-f6 by typing ESC f6.
!
! ** Typing Alt-Shift has strange effects on MS-Windows.
!
! This combination of keys is a command to change keyboard layout. If
! you proceed to type another non-modifier key before you let go of Alt
! and Shift, the Alt and Shift act as modifiers in the usual way. A
! more permanent work around is to change it to another key combination,
! or disable it in the keyboard control panel.
!
! ** Interrupting Cygwin port of Bash from Emacs doesn't work.
!
! Cygwin 1.x builds of the ported Bash cannot be interrupted from the
! MS-Windows version of Emacs. This is due to some change in the Bash
! port or in the Cygwin library which apparently make Bash ignore the
! keyboard interrupt event sent by Emacs to Bash. (Older Cygwin ports
! of Bash, up to b20.1, did receive SIGINT from Emacs.)
!
! ** Accessing remote files with ange-ftp hangs the MS-Windows version of Emacs.
!
! If the FTP client is the Cygwin port of GNU `ftp', this appears to be
! due to some bug in the Cygwin DLL or some incompatibility between it
! and the implementation of asynchronous subprocesses in the Windows
! port of Emacs. Specifically, some parts of the FTP server responses
! are not flushed out, apparently due to buffering issues, which
! confuses ange-ftp.
!
! The solution is to downgrade to an older version of the Cygwin DLL
! (version 1.3.2 was reported to solve the problem), or use the stock
! Windows FTP client, usually found in the `C:\WINDOWS' or 'C:\WINNT'
! directory. To force ange-ftp use the stock Windows client, set the
! variable `ange-ftp-ftp-program-name' to the absolute file name of the
! client's executable. For example:
(setq ange-ftp-ftp-program-name "c:/windows/ftp.exe")
--- 1972,2008 ----
of Windows. This is caused by a deficiency in the underlying system
library function.
! ** Typing Alt-Shift has strange effects on MS-Windows.
! This combination of keys is a command to change keyboard layout. If
! you proceed to type another non-modifier key before you let go of Alt
! and Shift, the Alt and Shift act as modifiers in the usual way. A
! more permanent work around is to change it to another key combination,
! or disable it in the keyboard control panel.
! ** Interrupting Cygwin port of Bash from Emacs doesn't work.
! Cygwin 1.x builds of the ported Bash cannot be interrupted from the
! MS-Windows version of Emacs. This is due to some change in the Bash
! port or in the Cygwin library which apparently make Bash ignore the
! keyboard interrupt event sent by Emacs to Bash. (Older Cygwin ports
! of Bash, up to b20.1, did receive SIGINT from Emacs.)
! ** Accessing remote files with ange-ftp hangs the MS-Windows version of Emacs.
! If the FTP client is the Cygwin port of GNU `ftp', this appears to be
! due to some bug in the Cygwin DLL or some incompatibility between it
! and the implementation of asynchronous subprocesses in the Windows
! port of Emacs. Specifically, some parts of the FTP server responses
! are not flushed out, apparently due to buffering issues, which
! confuses ange-ftp.
! The solution is to downgrade to an older version of the Cygwin DLL
! (version 1.3.2 was reported to solve the problem), or use the stock
! Windows FTP client, usually found in the `C:\WINDOWS' or 'C:\WINNT'
! directory. To force ange-ftp use the stock Windows client, set the
! variable `ange-ftp-ftp-program-name' to the absolute file name of the
! client's executable. For example:
(setq ange-ftp-ftp-program-name "c:/windows/ftp.exe")
***************
*** 2287,2307 ****
mode (e.g., disable the ``auto-protect'' feature), or even uninstall
or disable it entirely.
- ** On MS-Windows 95/98/ME, subprocesses do not terminate properly.
-
- This is a limitation of the Operating System, and can cause problems
- when shutting down Windows. Ensure that all subprocesses are exited
- cleanly before exiting Emacs. For more details, see the FAQ at
- http://www.gnu.org/software/emacs/windows/.
-
- ** MS-Windows 95/98/ME crashes when Emacs invokes non-existent programs.
-
- When a program you are trying to run is not found on the PATH,
- Windows might respond by crashing or locking up your system. In
- particular, this has been reported when trying to compile a Java
- program in JDEE when javac.exe is installed, but not on the system
- PATH.
-
** Pressing the mouse button on MS-Windows does not give a mouse-2 event.
This is usually a problem with the mouse driver. Because most Windows
--- 2038,2043 ----
***************
*** 2374,2388 ****
Alternatively, modify the generated src/Makefile to link the .a file
explicitly, and edit src/config.h to define HAVE_JPEG.
- *** AIX: You get this compiler error message:
-
- Processing include file ./XMenuInt.h
- 1501-106: (S) Include file X11/Xlib.h not found.
-
- This means your system was installed with only the X11 runtime i.d
- libraries. You have to find your sipo (bootable tape) and install
- X11Dev... with smit.
-
** Compilation
*** Building Emacs over NFS fails with ``Text file busy''.
--- 2110,2115 ----
***************
*** 2739,2748 ****
the file, and then reconfigure and rebuild Emacs. The dumping process
should now succeed.
- *** HPUX 10.20: Emacs crashes during dumping on the HPPA machine.
-
- This seems to be due to a GCC bug; it is fixed in GCC 2.8.1.
-
** Installation
*** Installing Emacs gets an error running `install-info'.
--- 2466,2471 ----
***************
*** 2798,2803 ****
--- 2521,2570 ----
** Ancient operating systems
+ AIX 4.2 was end-of-lifed on Dec 31st, 1999.
+
+ *** AIX: You get this compiler error message:
+
+ Processing include file ./XMenuInt.h
+ 1501-106: (S) Include file X11/Xlib.h not found.
+
+ This means your system was installed with only the X11 runtime i.d
+ libraries. You have to find your sipo (bootable tape) and install
+ X11Dev... with smit.
+
+ (This report must be ancient. Bootable tapes are long dead.)
+
+ *** AIX 3.2.4: Releasing Ctrl/Act key has no effect, if Shift is down.
+
+ Due to a feature of AIX, pressing or releasing the Ctrl/Act key is
+ ignored when the Shift, Alt or AltGr keys are held down. This can
+ lead to the keyboard being "control-locked"--ordinary letters are
+ treated as control characters.
+
+ You can get out of this "control-locked" state by pressing and
+ releasing Ctrl/Act while not pressing or holding any other keys.
+
+ *** AIX 3.2.5: You get this message when running Emacs:
+
+ Could not load program emacs
+ Symbol smtcheckinit in csh is undefined
+ Error was: Exec format error
+
+ or this one:
+
+ Could not load program .emacs
+ Symbol _system_con in csh is undefined
+ Symbol _fp_trapsta in csh is undefined
+ Error was: Exec format error
+
+ These can happen when you try to run on AIX 3.2.5 a program that was
+ compiled with 3.2.4. The fix is to recompile.
+
+ *** AIX 4.2: Emacs gets a segmentation fault at startup.
+
+ If you are using IBM's xlc compiler, compile emacs.c
+ without optimization; that should avoid the problem.
+
*** ISC Unix
**** ISC: display-time causes kernel problems on ISC systems.
***************
*** 2815,2820 ****
--- 2582,2594 ----
*** SunOS
+ SunOS 4.1.4 stopped shipping on Sep 30 1998.
+
+ **** SunOS: You get linker errors
+ ld: Undefined symbol
+ _get_wmShellWidgetClass
+ _get_applicationShellWidgetClass
+
**** Sun 4.0.x: M-x shell persistently reports "Process shell exited
abnormally with code 1".
This happened on Suns as a result of what is said to be a bug in Sunos
***************
*** 2847,2859 ****
IDA sendmail on vixen.cso.uiuc.edu in /pub:
sendmail-5.67b+IDA-1.5.tar.gz
- **** Sunos 5.3: Subprocesses remain, hanging but not zombies.
-
- A bug in Sunos 5.3 causes Emacs subprocesses to remain after Emacs
- exits. Sun patch # 101415-02 is part of the fix for this, but it only
- applies to ptys, and doesn't fix the problem with subprocesses
- communicating through pipes.
-
**** Sunos 4: You get the error ld: Undefined symbol __lib_version.
This is the result of using cc or gcc with the shared library meant
--- 2621,2626 ----
***************
*** 2886,2899 ****
Someone reported that recompiling with GCC 2.7.0 fixed this problem.
- **** SunOS: You get linker errors
- ld: Undefined symbol
- _get_wmShellWidgetClass
- _get_applicationShellWidgetClass
-
The fix to this is to install patch 100573 for OpenWindows 3.0
or link libXmu statically.
*** Apollo Domain
**** Shell mode ignores interrupts on Apollo Domain.
--- 2653,2668 ----
Someone reported that recompiling with GCC 2.7.0 fixed this problem.
The fix to this is to install patch 100573 for OpenWindows 3.0
or link libXmu statically.
+ **** Sunos 5.3: Subprocesses remain, hanging but not zombies.
+
+ A bug in Sunos 5.3 causes Emacs subprocesses to remain after Emacs
+ exits. Sun patch # 101415-02 is part of the fix for this, but it only
+ applies to ptys, and doesn't fix the problem with subprocesses
+ communicating through pipes.
+
*** Apollo Domain
**** Shell mode ignores interrupts on Apollo Domain.
***************
*** 3074,3080 ****
105284-12 is installed, but fail when 105284-15 is installed.
105284-18 might fix it again.
! *** Solaris 2.6 and 7: the Compose key does not work.
This is a bug in Motif in Solaris. Supposedly it has been fixed for
the next major release of Solaris. However, if someone with Sun
--- 2843,2849 ----
105284-12 is installed, but fail when 105284-15 is installed.
105284-18 might fix it again.
! **** Solaris 2.6 and 7: the Compose key does not work.
This is a bug in Motif in Solaris. Supposedly it has been fixed for
the next major release of Solaris. However, if someone with Sun
***************
*** 3091,3096 ****
--- 2860,2889 ----
if you link with the MIT X11 libraries instead of the Solaris X11
libraries.
+ *** HP/UX versions before 11.0
+
+ HP/UX 9 was end-of-lifed in December 1998.
+ HP/UX 10 was end-of-lifed in May 1999.
+
+ **** HP/UX 9: Emacs crashes with SIGBUS or SIGSEGV after you delete a frame.
+
+ We think this is due to a bug in the X libraries provided by HP. With
+ the alternative X libraries in /usr/contrib/mitX11R5/lib, the problem
+ does not happen.
+
+ *** HP/UX 10: Large file support is disabled.
+
+ See the comments in src/s/hpux10.h.
+
+ *** HP/UX: Emacs is slow using X11R5.
+
+ This happens if you use the MIT versions of the X libraries--it
+ doesn't run as fast as HP's version. People sometimes use the version
+ because they see the HP version doesn't have the libraries libXaw.a,
+ libXmu.a, libXext.a and others. HP/UX normally doesn't come with
+ those libraries installed. To get good performance, you need to
+ install them and rebuild Emacs.
+
*** Ultrix and Digital Unix
**** Ultrix 4.2: `make install' fails on install-doc with `Error 141'.
***************
*** 3145,3150 ****
--- 2938,3070 ----
This makes Emacs use memory less efficiently, but seems to work around
the kernel bug.
+ *** Irix 5 and earlier
+
+ Exactly when Irix-5 end-of-lifed is obscure. But since Irix 6.0
+ shipped in 1994, it has been some years.
+
+ **** Irix 5.2: unexelfsgi.c can't find cmplrs/stsupport.h.
+
+ The file cmplrs/stsupport.h was included in the wrong file set in the
+ Irix 5.2 distribution. You can find it in the optional fileset
+ compiler_dev, or copy it from some other Irix 5.2 system. A kludgy
+ workaround is to change unexelfsgi.c to include sym.h instead of
+ syms.h.
+
+ **** Irix 5.3: "out of virtual swap space".
+
+ This message occurs when the system runs out of swap space due to too
+ many large programs running. The solution is either to provide more
+ swap space or to reduce the number of large programs being run. You
+ can check the current status of the swap space by executing the
+ command `swap -l'.
+
+ You can increase swap space by changing the file /etc/fstab. Adding a
+ line like this:
+
+ /usr/swap/swap.more swap swap pri=3 0 0
+
+ where /usr/swap/swap.more is a file previously created (for instance
+ by using /etc/mkfile), will increase the swap space by the size of
+ that file. Execute `swap -m' or reboot the machine to activate the
+ new swap area. See the manpages for `swap' and `fstab' for further
+ information.
+
+ The objectserver daemon can use up lots of memory because it can be
+ swamped with NIS information. It collects information about all users
+ on the network that can log on to the host.
+
+ If you want to disable the objectserver completely, you can execute
+ the command `chkconfig objectserver off' and reboot. That may disable
+ some of the window system functionality, such as responding CDROM
+ icons.
+
+ You can also remove NIS support from the objectserver. The SGI `admin'
+ FAQ has a detailed description on how to do that; see question 35
+ ("Why isn't the objectserver working?"). The admin FAQ can be found at
+ ftp://viz.tamu.edu/pub/sgi/faq/.
+
+ **** Irix 5.3: Emacs crashes in utmpname.
+
+ This problem is fixed in Patch 3175 for Irix 5.3.
+ It is also fixed in Irix versions 6.2 and up.
+
+ **** Irix 6.0: Make tries (and fails) to build a program named unexelfsgi.
+
+ A compiler bug inserts spaces into the string "unexelfsgi . o"
+ in src/Makefile. Edit src/Makefile, after configure is run,
+ find that string, and take out the spaces.
+
+ Compiler fixes in Irix 6.0.1 should eliminate this problem.
+
+ *** SCO Unix and UnixWare
+
+ **** SCO 3.2v4: Unusable default font.
+
+ The Open Desktop environment comes with default X resource settings
+ that tell Emacs to use a variable-width font. Emacs cannot use such
+ fonts, so it does not work.
+
+ This is caused by the file /usr/lib/X11/app-defaults/ScoTerm, which is
+ the application-specific resource file for the `scoterm' terminal
+ emulator program. It contains several extremely general X resources
+ that affect other programs besides `scoterm'. In particular, these
+ resources affect Emacs also:
+
+ *Font: -*-helvetica-medium-r-*--12-*-p-*
+ *Background: scoBackground
+ *Foreground: scoForeground
+
+ The best solution is to create an application-specific resource file for
+ Emacs, /usr/lib/X11/sco/startup/Emacs, with the following contents:
+
+ Emacs*Font: -*-courier-medium-r-*-*-*-120-*-*-*-*-iso8859-1
+ Emacs*Background: white
+ Emacs*Foreground: black
+
+ (These settings mimic the Emacs defaults, but you can change them to
+ suit your needs.) This resource file is only read when the X server
+ starts up, so you should restart it by logging out of the Open Desktop
+ environment or by running `scologin stop; scologin start` from the shell
+ as root. Alternatively, you can put these settings in the
+ /usr/lib/X11/app-defaults/Emacs resource file and simply restart Emacs,
+ but then they will not affect remote invocations of Emacs that use the
+ Open Desktop display.
+
+ These resource files are not normally shared across a network of SCO
+ machines; you must create the file on each machine individually.
+
+ **** SCO 4.2.0: Regular expressions matching bugs on SCO systems.
+
+ On SCO, there are problems in regexp matching when Emacs is compiled
+ with the system compiler. The compiler version is "Microsoft C
+ version 6", SCO 4.2.0h Dev Sys Maintenance Supplement 01/06/93; Quick
+ C Compiler Version 1.00.46 (Beta). The solution is to compile with
+ GCC.
+
+ **** UnixWare 2.1: Error 12 (virtual memory exceeded) when dumping Emacs.
+
+ Paul Abrahams (address@hidden) reports that with the installed
+ virtual memory settings for UnixWare 2.1.2, an Error 12 occurs during
+ the "make" that builds Emacs, when running temacs to dump emacs. That
+ error indicates that the per-process virtual memory limit has been
+ exceeded. The default limit is probably 32MB. Raising the virtual
+ memory limit to 40MB should make it possible to finish building Emacs.
+
+ You can do this with the command `ulimit' (sh) or `limit' (csh).
+ But you have to be root to do it.
+
+ According to Martin Sohnius, you can also retune this in the kernel:
+
+ # /etc/conf/bin/idtune SDATLIM 33554432 ## soft data size limit
+ # /etc/conf/bin/idtune HDATLIM 33554432 ## hard "
+ # /etc/conf/bin/idtune SVMMSIZE unlimited ## soft process size limit
+ # /etc/conf/bin/idtune HVMMSIZE unlimited ## hard "
+ # /etc/conf/bin/idbuild -B
+
+ (He recommends you not change the stack limit, though.)
+ These changes take effect when you reboot.
+
*** Linux 1.x
**** Linux 1.0-1.04: Typing C-c C-c in Shell mode kills your X server.
***************
*** 3159,3164 ****
--- 3079,3169 ----
This is due to a kernel bug which seems to be fixed in Linux version
1.3.75.
+ ** Windows 3.1, 95, 98, and ME
+
+ *** MS-Windows NT/95: Problems running Perl under Emacs
+
+ `perl -de 0' just hangs when executed in an Emacs subshell.
+ The fault lies with Perl (indirectly with Windows NT/95).
+
+ The problem is that the Perl debugger explicitly opens a connection to
+ "CON", which is the DOS/NT equivalent of "/dev/tty", for interacting
+ with the user.
+
+ On Unix, this is okay, because Emacs (or the shell?) creates a
+ pseudo-tty so that /dev/tty is really the pipe Emacs is using to
+ communicate with the subprocess.
+
+ On NT, this fails because CON always refers to the handle for the
+ relevant console (approximately equivalent to a tty), and cannot be
+ redirected to refer to the pipe Emacs assigned to the subprocess as
+ stdin.
+
+ A workaround is to modify perldb.pl to use STDIN/STDOUT instead of CON.
+
+ For Perl 4:
+
+ *** PERL/LIB/PERLDB.PL.orig Wed May 26 08:24:18 1993
+ --- PERL/LIB/PERLDB.PL Mon Jul 01 15:28:16 1996
+ ***************
+ *** 68,74 ****
+ $rcfile=".perldb";
+ }
+ else {
+ ! $console = "con";
+ $rcfile="perldb.ini";
+ }
+
+ --- 68,74 ----
+ $rcfile=".perldb";
+ }
+ else {
+ ! $console = "";
+ $rcfile="perldb.ini";
+ }
+
+
+ For Perl 5:
+ *** perl/5.001/lib/perl5db.pl.orig Sun Jun 04 21:13:40 1995
+ --- perl/5.001/lib/perl5db.pl Mon Jul 01 17:00:08 1996
+ ***************
+ *** 22,28 ****
+ $rcfile=".perldb";
+ }
+ elsif (-e "con") {
+ ! $console = "con";
+ $rcfile="perldb.ini";
+ }
+ else {
+ --- 22,28 ----
+ $rcfile=".perldb";
+ }
+ elsif (-e "con") {
+ ! $console = "";
+ $rcfile="perldb.ini";
+ }
+ else {
+
+ *** MS-Windows 95: Alt-f6 does not get through to Emacs.
+
+ This character seems to be trapped by the kernel in Windows 95.
+ You can enter M-f6 by typing ESC f6.
+
+ *** MS-Windows 95/98/ME: subprocesses do not terminate properly.
+
+ This is a limitation of the Operating System, and can cause problems
+ when shutting down Windows. Ensure that all subprocesses are exited
+ cleanly before exiting Emacs. For more details, see the FAQ at
+ http://www.gnu.org/software/emacs/windows/.
+
+ *** MS-Windows 95/98/ME: crashes when Emacs invokes non-existent programs.
+
+ When a program you are trying to run is not found on the PATH,
+ Windows might respond by crashing or locking up your system. In
+ particular, this has been reported when trying to compile a Java
+ program in JDEE when javac.exe is installed, but not on the system
+ PATH.
+
** MS-DOS
*** When compiling with DJGPP on MS-Windows NT, "config msdos" fails.
***************
*** 3374,3379 ****
--- 3379,3397 ----
lib_version.o, try extracting it from X11/usr/lib/X11/libvim.a in
X11R4, then use it in the link.
+ ** SunOS4, DGUX 5.4.2: --with-x-toolkit version crashes when used with shared
libraries.
+
+ On some systems, including Sunos 4 and DGUX 5.4.2 and perhaps others,
+ unexec doesn't work properly with the shared library for the X
+ toolkit. You might be able to work around this by using a nonshared
+ libXt.a library. The real fix is to upgrade the various versions of
+ unexec and/or ralloc. We think this has been fixed on Sunos 4
+ and Solaris in version 19.29.
+
+ ** HPUX 10.20: Emacs crashes during dumping on the HPPA machine.
+
+ This seems to be due to a GCC bug; it is fixed in GCC 2.8.1.
+
** VMS: Compilation errors on VMS.
You will get warnings when compiling on VMS because there are