Package: closure-compiler Version: 20130227+dfsg1-6 Severity: important Hi,
suppose, the file "out.js" is empty then the following will happen on architectures without openjdk but gcj (hurd-i386, kfreebsd-any, sparc): $ closure-compiler --js out.js java.lang.RuntimeException: java.lang.LinkageError: loading constraint violated at com.google.javascript.jscomp.Compiler.runInCompilerThread(Compiler.java:712) at com.google.javascript.jscomp.Compiler.compile(Compiler.java:644) at com.google.javascript.jscomp.Compiler.compile(Compiler.java:600) at com.google.javascript.jscomp.AbstractCommandLineRunner.doRun(AbstractCommandLineRunner.java:784) at com.google.javascript.jscomp.AbstractCommandLineRunner.run(AbstractCommandLineRunner.java:380) at com.google.javascript.jscomp.CommandLineRunner.main(CommandLineRunner.java:980) Caused by: java.lang.LinkageError: loading constraint violated at java.lang.VMClassLoader.defineClass(libgcj.so.15) at java.lang.ClassLoader.defineClass(libgcj.so.15) at java.security.SecureClassLoader.defineClass(libgcj.so.15) at java.net.URLClassLoader.findClass(libgcj.so.15) at java.lang.ClassLoader.loadClass(libgcj.so.15) at java.lang.ClassLoader.loadClass(libgcj.so.15) at com.google.javascript.jscomp.Result.<init>(Result.java:54) at com.google.javascript.jscomp.Compiler.getResult(Compiler.java:981) at com.google.javascript.jscomp.Compiler$2.call(Compiler.java:648) at com.google.javascript.jscomp.Compiler$2.call(Compiler.java:644) at com.google.javascript.jscomp.Compiler$3.call(Compiler.java:674) at java.util.concurrent.FutureTask$Sync.innerRun(libgcj.so.15) at java.util.concurrent.FutureTask.run(libgcj.so.15) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(libgcj.so.15) at java.util.concurrent.ThreadPoolExecutor$Worker.run(libgcj.so.15) at java.lang.Thread.run(libgcj.so.15) This renders closure-compiler useless on hurd-i386, kfreebsd-any and sparc. cheers, josch __ This is the maintainer address of Debian's Java team <http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers>. Please use [email protected] for discussions and questions.
