Package: java-gcj-compat-dev Version: 1.0.30-4 Severity: wishlist Hi Matthias,
I tested tomcat5 with java-gcj-compat-dev and it works with one workaround. tomcat5 checks for JDK functionality by precense of the jdb tool. It's sufficient for startup if it is linked to /bin/true. However I would recommend to use a placeholder script explaining the meaning like I use in kaffe. #!/bin/sh # Placeholder script to fake a # JDK compatible JAVA_HOME directory. echo "This script is only a placeholder." echo "Some programs need a JDK rather than only a JRE to work." echo "They test for this tool to detect a JDK installation, but" echo "don't really need its functionality to work correctly." Regards, Wolfgang -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12.2 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Versions of packages java-gcj-compat-dev depends on: ii ecj-bootstrap [ecj] 3.1.1-1 bootstrap version of the Eclipse J ii gjdoc 0.7.5-5 documentation generation framework ii java-gcj-compat 1.0.30-4 Java runtime environment using GIJ ii libgcj6-dev 4.0.2-2 Java development headers and stati Versions of packages java-gcj-compat-dev recommends: pn libgcj6-src <none> (no description available) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]