I was able to resolve the make by doing the last compile step manually. As far as why a 32 bit JVM or a 64 bit machine, that only applies to my development system (which is my desktop). Our production servers are 32 bit systems. The problem with a 64 bit JVM on my development box is that MyEclipse (unless it's changed and I'm unaware) does not behave dependably in 64 bit. Using 32 bit, my Java development is rock-solid, so why change.

-- Rob

Markus Schönhaber said the following on 10/10/2007 02:01 PM:
Rob Tanner wrote:

I downloaded it and also applied the patch to eliminate the "Cannot execute JSVC executor process" error.

Why didn't you use the sources you already had?

But here's the catch, and maybe you know the answer. The machine and the OS (Fedora) are 64bit but the Java runtime is 32bit. In order for jsvc to make use of the shared libs, it has to be 32 bit as well. So, I build it like this:
And I end up with an ELF 64-bit LSB executable that gets an immediate segmentation fault.

Any ideas how to build it right.

You could set up a cross-compiler/cross-toolchain that is able to create
32-bit binaries or compile it on a 32-bit machine. Either way, you'll
have to install the 32-bit versions of the dependent libraries as well
(or create a static binary).

But first and foremost: what's the point in running Tomcat in a 32-bit
JVM on 64-bit machine?
Use a 64-bit JVM and save yourself a lot of trouble.


To start a new topic, e-mail:
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to