On doing more investigation, it seems the culprit is definitely the
included libtool script which is crushing my 64-bit intermediate
products (mod_caucho.o, etc) into 32-bit libraries.
Libtool seems somewhat(?) auto-generated (says so in the comments) and
as such doesn't seem to pick up the
Am willing to offer up a shell account and access in case no xeon-
based mac with 10.5 is available.
Thanks,
J --
On Nov 11, 2007, at 8:57 AM, Jason Chodakowski wrote:
Also... the test in the configure script does not properly detect the
64-bit-ness of the JVM. I noticed this and by default
Also... the test in the configure script does not properly detect the
64-bit-ness of the JVM. I noticed this and by default the JAVA_HOME
version is not 64 bit, but the SDK version is so a quick change in the
sybolic links leaves you with this:
jupiter2:Versions root# file /usr/bin/java
As an update to my previous post, I am actually able to build a 64 bit
module, but the install process using libtool turns it into a 32 bit
module.
Any help would be most welcome.
Cheers,
J --
On Nov 9, 2007, at 2:51 PM, Jason Chodakowski wrote:
I may have missed it if it went by already
