I think that ant is updated in my system as a dependancy for eclipse. The update fails building ant due to some deprecated APIs Possibly anyone out there now's what's going wrong here ? Maybe this is a package dependancy quirk. Trying to update some java packages manually now ... Reproducible: Always Steps to Reproduce: 1. 2. 3. This is the complete transcript: >>> emerge (8 of 43) dev-java/ant-1.6.2-r1 to / >>> md5 src_uri ;-) apache-ant-1.6.2-src.tar.bz2 >>> Unpacking source... >>> Unpacking apache-ant-1.6.2-src.tar.bz2 to /var/tmp/portage/ant-1.6.2-r1/worktar: A lone zero block at 34226 * Applying build.sh-exit-fix.patch.gz... [ ok ]>>> Source unpacked. . ... Bootstrapping Ant Distribution ... Compiling Ant Classes Note: Some input files use or override a deprecated API. Note: Recompile with -deprecation for details. ./bootstrap.sh: line 135: 30131 Killed "${JAVAC}" $BOOTJAVAC_OPTS -d ${CLASSDIR} ${TOOLS}/bzip2/*.java ${TOOLS}/tar/*.java ${TOOLS}/zip/*.java ${TOOLS}/ant/util/regexp/RegexpMatcher.java ${TOOLS}/ant/util/regexp/RegexpMatcherFactory.java ${TOOLS}/ant/types/*.java ${TOOLS}/ant/*.java ${TOOLS}/ant/taskdefs/*.java ${TOOLS}/ant/taskdefs/compilers/*.java ${TOOLS}/ant/taskdefs/condition/*.java ... Failed compiling Ant classes ! Bootstrap FAILED !!! ERROR: dev-java/ant-1.6.2-r1 failed. !!! Function src_compile, Line 62, Exitcode 1 !!! (no error message)
which jdk are you useing? source /etc/profile && java-config -O
My JDK is /opt/blackdown-jdk-1.4.2_rc1
Are you running grsecurity or other strange kernel patches? Your problem has nothing to do with the deprecation warnings. I would guess there's an hidden NPE or sig11 going on somewhere.
No I don't think my kernel options are strange. I run a simple vanilla development kernel 2.6.7 I don't use patches on it, nor I switched on security options that strike some system features. Very strange. I also cannot find any other hints whats happening here. An strace doesn't seem to work upon the java command. Such that I cannot find the signal happening. At least there seems to be no NPE or SIG11.
I saw that you changed something installing a new bash-3 but the problem still exists. It seem to exist in other java packages too, but ant is the first that gets compiled.
The signal seems to be a simple kill. This is a really annoying problem I think. It seems that the internal process kills itself by SIGKILL ... FROM STRACE: open("src/main/org/apache/tools/ant/taskdefs/condition/", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = 3 fstat64(3, {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 fcntl64(3, F_SETFD, FD_CLOEXEC) = 0 getdents64(3, /* 17 entries */, 4096) = 568 getdents64(3, /* 0 entries */, 4096) = 0 close(3) = 0 rt_sigprocmask(SIG_BLOCK, [INT CHLD], [RTMIN], 8) = 0 _llseek(255, -740, [3637], SEEK_CUR) = 0 fork() = 17808 rt_sigprocmask(SIG_SETMASK, [RTMIN], NULL, 8) = 0 rt_sigprocmask(SIG_BLOCK, [CHLD], [RTMIN], 8) = 0 rt_sigprocmask(SIG_SETMASK, [RTMIN], NULL, 8) = 0 rt_sigprocmask(SIG_BLOCK, [CHLD], [RTMIN], 8) = 0 rt_sigaction(SIGINT, {0x8077bf0, [], 0}, {SIG_DFL}, 8) = 0 waitpid(-1, Note: Some input files use or override a deprecated API. Note: Recompile with -deprecation for details. [WIFSIGNALED(s) && WTERMSIG(s) == SIGKILL], 0) = 17808 fstat64(2, {st_mode=S_IFREG|0644, st_size=18047, ...}) = 0 old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40019000 uname({sys="Linux", node="ask.home.org", ...}) = 0 write(2, "./bootstrap.sh: line 135: 17808 "..., 408./bootstrap.sh: line 135: 17808 Killed "${JAVAC}" $BOOTJAVAC_OPTS -d ${CLASSDIR} ${TOOLS}/bzip2/*.java ${TOOLS}/tar/*.java ${TOOLS}/zip/*.java ${TOOLS}/ant/util/regexp/RegexpMatcher.java ${TOOLS}/ant/util/regexp/RegexpMatcherFactory.java ${TOOLS}/ant/types/*.java ${TOOLS}/ant/*.java ${TOOLS}/ant/taskdefs/*.java ${TOOLS}/ant/taskdefs/compilers/*.java ${TOOLS}/ant/taskdefs/condition/*.java ) = 408
Please try another kernel than the vanilla 2.6.7. Try, a random 2.4 kernel, or a random 2.6 gentoo kernel. From cursory testing, it appears to be a problem with the 2.6.7 series of vanilla kernels.
i was also having this problem, with vanilla 2.6.8-rc1 it's fixed in 2.6.8-rc2 http://seclists.org/lists/linux-kernel/2004/Jul/2336.html
Agreed. I yesterday updated to kernel-2.6.8-rc2 and now the java machine works again. I would say it's the time to close this bug
