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 CFLAGS and LDFLAGS which work when
you edit the Makefiles manually.
This is what Apple specifies:
CFLAGS=-isysroot /Developer/SDKs/MacOSX10.5.sdk -arch x86_64
Any thoughts at all?
On Nov 10, 2007, at 9:43 AM, Jason Chodakowski wrote:
> 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
> Any help would be most welcome.
> J --
> On Nov 9, 2007, at 2:51 PM, Jason Chodakowski wrote:
>> I may have missed it if it went by already but has anyone run into
>> this yet? The standard configure-then-make on my Mac Pro builds a
>> module that will not load. I get this message:
>> ttpd: Syntax error on line 489 of /private/etc/apache2/httpd.conf:
>> Cannot load /usr/libexec/apache2/mod_caucho.so into server: dlopen(/
>> usr/libexec/apache2/mod_caucho.so, 10): no suitable image found. Did
>> find:\n\t/usr/libexec/apache2/mod_caucho.so: mach-o, but wrong
>> This is compiled with the latest from Apple as far as XCode and
>> associated compilers, headers, etc.
>> I've tried with the --enable-64bit flag but this seems to only affect
>> the resin binary and not the apache modules.
>> Any help would be most appreciated.
>> resin-interest mailing list
> resin-interest mailing list
resin-interest mailing list