Hi Justin,
Justin Vassallo schrieb:
Hello Rainer,
Thank you.
I have deleted my Apache and connector, re-dlded and rebuilt from source.
Same issue. I am attaching a full output for reference.
I am using httpd-2.2.8, but the connector only has sub-folders for 1.3 and
2.0. Could this be an issue?
No, this is no problem. The 1.3 sub folder is the httpd 1.3 specific
part, the 2.0 sub folder for any 2.x.
From looking at the output, I have a couple of remarks:
1) You also get the no dlanme warning when building mod_ssl. So I guess
the problem is not mod_jk specific, but somewhere inside your build
environment.
Does your build produce a mod_ssl.so? Does it produce a mod_jk.so? If
so, what is the result of "file mod_something.so" (something=ssl, jk).
Can you load mod_ssl into your httpd?
2) Your httpd configure says:
checking whether to build shared libraries... no
It says "yes" for me. I used
MAKE=gmake
export MAKE
./configure --with-included-apr \
--prefix=/my/install/dir \
--enable-so \
--enable-modules=all \
--enable-mods-shared=all
to build httpd. The configure line you use seems a bit broken, since
obviously you want to build mod_rewrite, but configure says you are not
going to build it. Also you build mod_ssl as a dynamic module and all
other modules static. If you don't really want that, try to use the
above configure call.
3) You said you needed to install gnu make (into /usr/local). Usually
gnu make is just there, in /usr/sfw/bin/gmake. With the above MAKE env
var, configure should find it there, if you have /usr/sfw/bin in your
path (as you have). After configure you then do a "gmake" and "gmake
install".
Now you installed make into /usr/local, which means you've got
/usr/local/bin in your path. I don't know, what other tools you are
actually going to use from that path (gcc for instance?). I build fine
with the tools that Solaris 10 provides in /usr/sfw/bin.
4) The make output for mod_jk indicates, that it has nothing to build,
so it seems, that you didn't cleanup before running the make from which
you posted the output.
Regards,
Rainer
Rgds
Justin
-----Original Message-----
From: Rainer Jung [mailto:[EMAIL PROTECTED]
Sent: 10 March 2008 21:51
To: Tomcat Users List
Subject: Re: building mod_jk failing
Hi Justin,
Justin Vassallo schrieb:
Thank you that helped. I got gnumake installed and configure worked fine.
(had to chmod 700 configure and scripts/build/instdso.sh)
No, I think you are still using the wrong source download. In the tar.gz
download of mod_jk 1.2.26 configure is already executable.
Now getting this warning, otherwise .so being created ok:
Warning! dlname not found in
/local/home/ixops3/tomcat-connectors-1.2.26-src/tomcat-connectors-1.2.26-src
/native/apache-2.0/mod_jk.la.
I did the build myself too on Solaris 10 x86. I get no such warning.
My .la file conta9ins a dlname:
myhost% cat apache-2.0/mod_jk.la
# mod_jk.la - a libtool library file
# Generated by ltmain.sh - GNU libtool 1.5.22 (1.1220.2.365 2005/12/18
22:14:06)
#
# Please DO NOT delete this file!
# It is necessary for linking the library.
# The name that we can dlopen(3).
dlname='mod_jk.so'
...
However, apache is not liking it...
httpd: Syntax error on line 412 of
/local/apache/apache2.2.8/conf/httpd.conf: Cannot load
/local/apache/apache2.2.8/modules/mod_jk.so into server: ld.so.1: httpd:
fatal: /local/apache/apache2.2.8/modules/mod_jk.so: wrong ELF data format:
ELFDATA2MSB
It does load my file and the file command tells me, that m module is a
myhost% file apache-2.0/mod_jk.so
apache-2.0/mod_jk.so: ELF 32-bit LSB dynamic lib 80386 Version 1,
dynamically linked, not stripped
I first build httpd with
./configure --with-included-apr --prefix=/my/install/dir --enable-so
--enable-modules=all --enable-mods-shared=all
Before calling configure I set the env var MAKE to gmake.
After building and installing Apache httpd, I added the lib directory of
httpd and /usr/sfw/lib to LD_LIBRARY_PATH:
LD_LIBRARY_PATH=/my/install/dir/lib:/usr/sfw/lib
export LD_LIBRARY_PATH
and then I do
./configure --with-apxs=/my/install/dir/bin/apxs
inside the mod_jk native directory and then gmake and gmake install.
That's it. No errors.
Thanks - j
PS - it was Re since I had posted this before I became a user, and
forwarded
once I joined
Regards,
Rainer
-----Original Message-----
From: Rainer Jung [mailto:[EMAIL PROTECTED]
Sent: 10 March 2008 17:53
To: Tomcat Users List
Subject: Re: building mod_jk failing
Justin Vassallo wrote:
Hello,
I am trying to build mod_jk on Solaris 10 x86, which unfortunately is not
available in binary form.
I dlded Apache source and built using:
$ PATH=$PATH:/usr/sfw/bin:/usr/ccs/bin
$ export PATH SH_LIBS
$ ./configure --with-included-apr
--prefix=/usr/local/apache/httpd-2.2.8 --enable-so --enable-mods
-shared=ssl
--enable-ssl --enable-module=rewrite --enable-shared=rewrite
I then dlded mod_jk source, cd native, then tried to build using the apxs
from the Apache i just built from source. I am getting a general error
which
is not helping me to identify the problem.
Where can i look to get more information? thanks
# ./configure --with-apxs=/local/apache/apache2.2.8/bin/apxs
: bad interpreter: No such file or directory
Not sure, why your mail subject starts with "Re:", I couldn't find any
previous mails in this thread.
configure is a shell script. From the error I would guess, that you
downloaded the zip source and not the tarball format. The zip file
contains DOS files, so configure and many other files have DOS line
endings and using those shell scripts gives an error, because /bin/sh^M
is not an existing shell.
If I'm right about the zip download, simply choose the .tar.gz download,
which should work. Are we talking about mod_jk 1.2.26?
Please also make sure, that you are using the make/gmake in /usr/sfw/bin
and not the Solaris make in /usr/ccs/bin.
Regards,
Rainer
---------------------------------------------------------------------
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]
