Re: mod_jk for OS X PPC

[BuildSmart]

On Oct 30, 2007, at 24:51:24, Peter Rossbach wrote:

Hi,

I have build my own mod_jk 1.2.25 module at Leopard:

Rebuild the locate database and you'll be able to find both.

I just confirmed that two "apxs" exists, one for apache 1.3 and one for apache 2.2 so installing a third is a waste of time, energy and disk space, one obvious reasons will be aparent if you examine the module and see what shared objects are linked to it. (man otool) Of course you can use install_name_tool to fix it but you have to know what you're doing.

Install current Mac Ports

I guess any working solution is better than none.

sudo port install autoconf
sudo port install apr
sudo port install apr-util

# use gnu libtool

ln -s /opt/local/bin/glibtool /opt/local/bin/libtool
ln -s /opt/local/bin/glibtoolize /opt/local/bin/libtoolize

Thats wrong.

try: (in /etc/profile)
LIBTOOLIZE=glibtoolize
export LIBTOOLIZE

Now end and start a new terminal session and it will work as expected.

download/extract/goto apache 2.2.6


download/extract/goto mod_jk 1.2.25
.configure --with-apxs=/Users/xxx/server/apache226/bin/apxs
make
make install

./configure --prefix=/Users/xxx/server/apache226 --enable-so --with- mpm=worker ; make ; make install config mod_jk at apache226; start apache and volia mod_jk is up and runnig.

You do realize that it's linking to shared objects in your /Users/xxx/ server/apache226 tree and if you remove this tree the module is broken due to the loss of shared object dependancies.

I hope we can download the PPC binaries at Wednesday. I can check the mod_jk binaries with the standard Leopard apache 2.2.6 installation.

Then at least you'll have a binary worth distributing.

If you're going to build it and make it available for downloading then at least have the courtesy to build it natively as a universal binary, this does not require -syslibroot/-sysroot or even NEXT_ROOT. It's a matter of adding the appropriate build/link flags and of course it wouldn't hurt to make a binary that has backward compatability with 10.4 so you don't have a million modules. Since mod_jk comes with a configure script it should be easy for anyone with the 10.5 OS to do, something like: MACOSX_DEPLOYMENT_TARGET=10.4 CFLAGS="-arch ppc -arch i386 -g -Os - pipe -no-cpp-precomp" CCFLAGS="-arch ppc -arch i386 -g -Os -pipe " CXXFLAGS="-arch ppc -arch i386 -g -Os -pipe " LDFLAGS="-arch ppc - arch i386 -bind_at_load " ./configure --xxxx=XXXX --zzzz=ZZZZ You could also add " -arch ppc64 -arch x86_64" so that you can take advantage of the 64bit architectures on the machines that support it like your G5. If you want to make a dedicated 10.5.0 developer environment it's not that hard, it takes about 2gb of disk space and when you update your OS you'll be able to build for all 10.5.x in the environment and retain full 10.5 compatibility where if you resort to using your main OS install and you update the OS you effectively change the ability to be backwards compatible because you'll be linking to a specific version of the System library which probably wont have the ability to be backwards compatible. Then you can do away with MacPorts and the method in which it kills diskspace and taints your environment by providing multiple installations of the same software for different packages. Oh, and if you haven't figured out, install the X11 and use those libraries as dependancies whenever you can, they outperform anything that MacPorts can create and stay away from fink.

Regards
Peter


Am 29.10.2007 um 22:14 schrieb Christopher Schultz:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Richard,

Richard Doust wrote:

In case that image doesn't get through, (and to make this text
searchable) it says:

Thanks for posting the text: the image did not come through; mailing

lists rarely accept non-text attachments (and sometimes not even then).

Cannot load /usr/libexec/apache2/mod_jk.so into server:

find /usr/libexec/apache2/mod_jk.so: mach-o, but wrong architecture.

dlopen(/usr/libexec/apache2/mod_jk.so, 10): no suitable image found. Did

Can you run these on your system, please?

$ uname -a

$ file /path/to/mod_jk.so

??


version of your compiler would be helpful, too (usually 'cc -v' or
something similar).

That should give us some technical details that should help. Also, the

That's what I get.

Apache just for hahas and get the same error, so I'm not sure what's
going on.

I tried using the mod_jk.so that I had working with the 1.3 version of

That's a little odd... it seems that Apache is complaining about the

will certainly not work.

architecture, instead of the httpd API version mismatch. The 1.3 binary

I was hoping some kind soul might have a working version of mod_jk.so

for the PowerPC architecture.
Any light you can help shed on the subject would be appreciated.

it came with the new version of Apache.

Oh, the apxs file in /usr/sbin has a timestamp that leads me to believe

Good to know.

- -chris

-- Dale

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