Your message dated Tue, 02 Jun 2015 11:19:02 +0200 with message-id <[email protected]> and subject line closing bugs reported against ancient emacs versions has caused the Debian Bug report #319358, regarding emacs21-common: compile-mode fails with error 129 on some ant compilations to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 319358: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=319358 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: emacs21-common Version: 21.4a-1 Severity: normal When I use Mx-compile with a compile command of "ant -emacs", the compilation sometimes fails with this message: Compilation exited abnormally with code 129 at Thu Jul 21 15:46:25 This occurs mainly when the task involves running a Java application, like for example unit textings with the <junit> task. Here are two sample files that reproduce the problem, put them in an empty directory and try M-x compile with "ant -emacs" as the compile command. ----- file build.xml ---- <?xml version="1.0"?> <project name="emacs-bash-ant" basedir="." default="all"> <target name="all" > <javac srcdir="." destdir="."/> <java fork="yes" classname="Main" classpath="."/> </target> </project> ---- file build.xml --- ---- file Main.java ---- public class Main { public static void main(String[] args) { System.exit(0); } } ---- file Main.java ---- The problem does *not* occur if I run the compilation myself with the command: ant -emacs However, I tried to "strace -p xxxx -f -F" the running emacs and think I found that one of the threads in the bash interpeter performed a system call like "exit_group(129)". So I suspected bash was responsible for this, so I tried to launch the compilation almost as emacs did: /bin/bash -c "ant -emacs" < /dev/null There was no problem and the compilation performed successfully. Another test I tried was to customize the shell-file-name variable for the current emacs session only to /bin/ksh. This removed the problem. So I think the problem is either somewhere in the way emacs launches bash (the call-process builtin function seems to do weird things with pseudo terminals before the shell is executed) or in the bash code itself. I register this bugs with emacs as launching the command directly from a terminal with bash does not triggers the problem. The bash version I have installed is 2.05b-26 and the ksh version is pdksh is 5.2.14-18. I use the SUN jdk 1.4.2_08-b03. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.8lehrin4 Locale: LANG=fr_FR, LC_CTYPE=fr_FR (charmap=ISO-8859-1)
--- End Message ---
--- Begin Message ---This bug has been reported against an ancient version of emacs (emacs21, emacs22) that is no longer supported. It is assumed to be fixed (or no longer relevant) in newer releases and therefore I'm closing this report now. If the problem is still reproducible in the current version (emacs24), feel free to provide more information and reopen this bug report. Andreas
--- End Message ---
