Unfortunately, our AIX 4.3.3 box is not loaded with gcc.
After I moved files to ../jk/.
I ran
bdvdc14i:xv042b:> apxs -c -o mod_jk.so *.o
-o mod_jk.so jk_ajp12_worker.o jk_ajp13.o jk_ajp13_worker.o jk_connect.o
jk_jni_worker.o jk_lb_worker.o jk_map.o jk_msg_buff.o jk_pool.o jk_sockbuf.o
jk_uri_worker_map.o jk_util.o jk_worker.o mod_jk.o
apxs:Break: Command failed with rc=255
or
bdvdc14i:xv042b:> apxs -c -o mod_jk.so ../jk/*.o
-o mod_jk.so ../jk/jk_ajp12_worker.o ../jk/jk_ajp13.o ../jk/jk_ajp13_worker.o
../jk/jk_connect.o ../jk/jk_jni_worker.o ../jk/jk_lb_worker.o ../jk/jk_map.o
../jk/jk_msg_buff.o ../jk/jk_nwmain.o ../jk/jk_pool.o ../jk/jk_sockbuf.o
../jk/jk_uri_worker_map.o ../jk/jk_util.o ../jk/jk_worker.o ../jk/mod_jk.o
apxs:Break: Command failed with rc=255
It always came back with "apxs:Break: Command failed with rc=255"
Any cludes ???
> ----------
> From: Mark Johnson[SMTP:[EMAIL PROTECTED]]
> Reply To: [EMAIL PROTECTED]
> Sent: Thursday, April 19, 2001 1:19 PM
> To: [EMAIL PROTECTED]
> Subject: Re: creating mod_jk.so on AIX
>
> I ran into what may be a similar problem on a linux machine. When I ran
> apxs to create mod_jk.so, I got a similar message.
>
> The problem: ld was looking for *.o in ../jk/, but running apxs had
> placed *.o in . (ie, the current directory). Note: I was using an apxs
> from an earlier install of apache in a /usr/src rather than
> /usr/local/src, which I suspect is the problem.
>
> Search for jk_jni_worker.o. If it's in the current directory, here's a
> quick (dumb) solution:
> # mv *.o ../jk/.
> then rerun apxs.
>
