Alex,

QuadG5:native jboss$ ./configure CFLAGS='arch ppc64' APXSLDFLAGS='arch ppc64' --with-apxs=/usr/sbin/apxs

.
.
.
checking for gcc... gcc
checking for C compiler default output file name... configure: error: C compiler cannot create executables
See `config.log' for more details.

I also tried ppc_64. I'm looking for the right value now.
I looked in the configure.log file and did a man on gcc and came to the understanding that:

Ah, okay, -arch ppc64 is a valid parameter to the compiler, so I did:

./configure cflags='-arch ppc64' APXSLDFLAGS='-arch ppc64' --with- apxs=/usr/sbin/apxs

and that made some makefiles which I then used to compile mod_jk.so.

Now I'm dealing with some apache configuration parameters in my old config that are apparently no longer valid (AddModule). I'll take it from here.
Thanks an awful lot for the help!

This also explains why the old mod_jk.so generated the same error. It's looking at 32-bit vs. 64-bit before it gets to the api.

Richard

On Oct 30, 2007, at 9:44 AM, Alex Fuller wrote:




Alex Fuller wrote:


it should come back with (for a G5):

/usr/libexec/apache2/mod_alias.so (for architecture ppc64): Mach-O 64-bit
bundle ppc64

Whereas I suspect on the one you're currently building you'd get:

/usr/libexec/apache2/mod_alias.so (for architecture ppc7400):   Mach-O
bundle ppc




Ha ha - obviously you would see a different path to the mod_jk.so file, I was using the Apple-built mod_alias.so as an example to check the reported
architecture key.... :-/

Alex
--
View this message in context: 
http://www.nabble.com/mod_jk-for-OS-X-PPC-tf4712890.html#a13488683
Sent from the Tomcat - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to