It appears that the startup.sh script misuses catalina.sh. But digging deeper, it appears that emerge did not compile the binaries at all. There is no jsvc binary to be found on the system. The $CATALINA_HOME/bin folder contains a tarball that was never unpacked. So I unpacked it manually, and ran autoconf (as per the Tomcat install guide). The results of that were:

The discussion forums have recommended running export WANT_AUTOCONF_2_5=1 to resolve this, and it works. Autoconf executes without error after setting that variable. However, the next step is to run ./configure, and that errors as follows:

This script, last modified 2001-04-20, has failed to recognize
the operating system you are using. It is advised that you
download the most up to date version of the config scripts from

ftp://ftp.gnu.org/pub/gnu/config/

If the version you run (./support/config.guess) is already up to date, please
send the following data and any information you think might be
pertinent to <config-patches@gnu.org> in order to provide the needed
information to handle your system.

uname -m returns "ppc64," so my suspicion is that the installer cannot yet handle it. I would like know how to make uname lie, and just say that it's a "ppc." I think bruda had to do this with some installs. Is this possible? How do I do it?

How I did it is outlined towards the end of the thread https://forums.gentoo.org/viewtopic.php?t=198684 and is really ugly but it works. I renamed /bin/uname to /bin/uname64. I then created a /bin/uname32 as a shell script (make it executable, of course) containing the following:

Quote:

#!/bin/sh
/bin/uname64 $1 $2 $3 $4 $5 $6 | sed -e s/ppc64/ppc/

Finally, I would symlink /bin/uname to point to /bin/uname32. Once the hack is no longer needed (e.g., tomcat is compiled and installed) the symlink would be changed to point to the real uname (/bin/uname64). Same goes for /bin/arch._________________Quid latine dictum sit altum videtur

I first tried to be somewhat clean about it, and edited the Tomcat ./configure script. I was able to manipulate it so that the here-document it builds contains "ppc" for its architecture, but at some point the script does its own uname, and ignores its own here-document.

So I applied your hack and it worked.

I have a (probably working) binary, but this does not resolve the original problem. Running /etc/init.d/tomcat5 start still results in a display of the catalina.sh command syntax.

Last edited by jgombos on Tue Aug 10, 2004 4:07 pm; edited 1 time in total