Re: mod_jk for OS X PPC

[BuildSmart]

On Oct 30, 2007, at 13:34:36, Richard Doust wrote:

Dale,

Richard

So what are you saying? It's working with that compile. Should I build it with some other set of options?

What I said was IT IS NOT RECOMMENDED TO BUILD FOR ppc64 ONLY.

Without the ADE the chances that you could build for more than the 4 basics and have a module that will work are pretty much non-existant unless you managed to obtain the /AppleInternal development tree (you know, the files your missing when you try to build one of the Apple source packages). According to the developer documentation, "./configure CFLAGS='arch ppc64' APXSLDFLAGS='arch ppc64' --with-apxs=/usr/sbin/apxs" format is not recommended and often times will yield a binary that is over inflated and non-functional. And that wont work anyways cause there a typo... it's "-arch" not "arch", also, using precompiled headers for ppc on other architectures isn't recommended either so it's wise to add "-no-cpp- precomp" if you're building for more than ppc in your case. One of the following will yield the results you need (I build at Apple in the real ADE so I don't have your build issues). MACOSX_DEPLOYMENT_TARGET=10.4 APXSLDFLAGS="-arch ppc -arch ppc64 - bind_at_load " CFLAGS="-arch ppc -arch ppc64 -g -Os -pipe -no-cpp- precomp" CCFLAGS="-arch ppc -arch ppc64 -g -Os -pipe " CXXFLAGS="- arch ppc -arch ppc64 -g -Os -pipe " LDFLAGS="-arch ppc -arch ppc64 - bind_at_load " ./configure --with-apxs=/usr/sbin/apxs MACOSX_DEPLOYMENT_TARGET=10.4 APXSLDFLAGS="-arch ppc -arch ppc64 - arch i386 -arch x86_64 -bind_at_load " CFLAGS="-arch ppc -arch ppc64 -arch i386 -arch x86_64 -g -Os -pipe -no-cpp-precomp" CCFLAGS="-arch ppc -arch ppc64 -arch i386 -arch x86_64 -g -Os -pipe " CXXFLAGS="- arch ppc -arch ppc64 -arch i386 -arch x86_64 -g -Os -pipe " LDFLAGS="-arch ppc -arch ppc64 -arch i386 -arch x86_64 -bind_at_load " ./configure --with-apxs=/usr/sbin/apxs If you actually have the headers required for all 4 architectures and can make the module for 4 then I would suggest while you're still at 10.5.0 you make the module and then give it to someone at tomcat to provide as a binary. If you have a small 20-80gb drive, install it in the machine, format as case sensitive journaled and name it DO_NOT_FINDER_BROWSE and I'll send you instruction off-list on how to populate it so that it can be used as a home-brewed ADE that you can use to build stuff on that will be environmentally compliant, work for everyone and always work if you want to go this route.

On Oct 30, 2007, at 12:28 PM, BuildSmart wrote:

On Oct 30, 2007, at 10:37:13, Richard Doust wrote:

Alex,



.
.
.
checking for gcc... gcc

See `config.log' for more details.

I also tried ppc_64. I'm looking for the right value now.






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


Thanks an awful lot for the help!

QuadG5:native jboss$ ./configure CFLAGS='arch ppc64' APXSLDFLAGS='arch ppc64' --with-apxs=/usr/sbin/apxs checking for C compiler default output file name... configure: error: C compiler cannot create executables 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 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. 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.

Not likely, that isn't how it works, apache isn't compiled for ppc64 only and it's not recommended to generate a ppc64 only module unless you strip all of the 32bit architecture from all of the binaries and force it to run in 64bit only which wont happen if you examine some of the libraries in /usr/lib.

Richard

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

Alex Fuller wrote:

it should come back with (for a G5):


bundle ppc64

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


bundle ppc

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

architecture key.... :-/

Alex
--

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

-- Dale

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

-- Dale

PGP.sig
Description: This is a digitally signed message part