On 18.12.2008 17:22, Pieter Temmerman wrote:
Hi André,
From my experience I can tell you this partly works, but!..
You need to make sure that the glibc version is the same (or older,
glibc should be backwards compatible).
I usually compile my linux multiplatform binaries in a RH7 machine,
which creates binaries that magically seem to be working in other Linux
systems (because of the older glibc version).
Also, make sure that there are no dependencies to system libraries (as
they might not be present on the target machine). The best thing to do
to avoid this is to compile your binary in a stripped chroot (only
containing the least necessary libraries for linux to run, thus no
openssl.so and stuff like that). Now let's say that your binary depends
on openssl, then you will need to compile openssl yourself as well, and
bundle that library with the binaries that you are going to ship (or
statically link them). Later you can use LD_LIBRARY_PATH to hook them
into your compiled binary.
Anyway..maybe you're better off installing Suse and just compile it :)
On Thu, 2008-12-18 at 16:50 +0100, André Warnier wrote:
Rainer Jung wrote:
On 18.12.2008 13:07, André Warnier wrote:
Rainer Jung wrote:
You can get the patched sources at:
http://people.apache.org/~rjung/mod_jk-dev/
but not the binaries ;)
Oh well, I'll have to ask the guy who compiled the original from source,
if he can deal with this too.
;-)
The internals of this dev version are exactly packaged in the form of an
official release. So the build process works exactly the same (configure
and make), no additional tools needed.
The version will identify itself as 1.2.28-dev, so you can't hide it's
not the official release :)
Just one more question : assuming (just assuming) that I would like to
have a try myself, just for memory's sake, but I don't have the exact
customer system. (I have a Debian Linux 2.6.18 32-bit system)
Does that work, and can I use the result on the customer's Suse Linux
system ?
Respecting the above mentioned experience using older systems to build,
for production use I would also advice to use the target platform to
build. You could though use your customers httpd/mod_jk configuration on
your own system, reproduce the problem with the official 1.2.27 release
on your system and then test, whether it's gone there using the dev
snapshot.
Regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
