Can anyone provide me with assistance in building an _OLD_ version (v2.2) of the module with the latest 1.X line of Apache HTTP?
I have some legacy code that uses it that doesnt' seem to be compatible with v3.0 of the module, and I'm not having any luck getting current instructions to work.
When I do a ./configure and a make on v2.2 of the module, I get the .c files...then I do a
like for v3.0... and when I try to load it in apache I get:
Syntax error on line 22 of /var/shc/apache/conf/httpsd.conf:
Cannot load /var/shc/apache/libexec/mod_auth_mysql.so into server: /var/shc/apac
he/libexec/mod_auth_mysql.so: Undefined symbol "register_cleanup"
Any help would be appreciated!!!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm not sure you're using our version of mod_auth_mysql 2.2. As far as I know, there's never been a ./configure command for our version. But that was before my time, so I really can't say.
I'm concerned about why register_cleanup wasn't found in your current version of Apache. I checked the Apache docs and I can't find anything relating to this function being removed in Apache 1.3.x, and we need to call it to clean up when the pool is destroyed. And this part of the code hasn't changed for several versions.
Can you tell me exactly which version of Apache you're running? Also, if possible, what configuration parameters you used to build Apache? That would help us duplicate your problem.
Thanks,
Jerry
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm not familiar with that version; it sounds like you need to contact the author for assistance.
We only support the recent versions in this project.
PHP shouldn't affect it - it makes no changes to the Apache code.. However, I don't know what your SSL patch did.
Your Apache config parameters look good, but I'll have to dig around some to see if there's something special needed. But the main one should be --enable-module=so, and you have that.
Generally, Apache doesn't change the API's when changing minor releases - only major releases and versions. Minor ones are generally bug fixes.
Also, the fact you didn't get a compile error on mod_auth_mysql indicates the function should be there.
Is there any chance you have two versions of Apache on your system - and are compiling/linking against one but running on another? It's one possibility.
I have tested with 1.3.31 with no problems. Others have tested with 1.3.33 and I believe 1.3.34 with no problems such as you've described.
It's very strange.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Can anyone provide me with assistance in building an _OLD_ version (v2.2) of the module with the latest 1.X line of Apache HTTP?
I have some legacy code that uses it that doesnt' seem to be compatible with v3.0 of the module, and I'm not having any luck getting current instructions to work.
When I do a ./configure and a make on v2.2 of the module, I get the .c files...then I do a
/var/shc/apache.new/bin/apxs -c -L/var/shc/mysql/lib/mysql -I/var/shc/mysql/include -lmysqlclient -lm -lz mod_auth_mysql.c
like for v3.0... and when I try to load it in apache I get:
Syntax error on line 22 of /var/shc/apache/conf/httpsd.conf:
Cannot load /var/shc/apache/libexec/mod_auth_mysql.so into server: /var/shc/apac
he/libexec/mod_auth_mysql.so: Undefined symbol "register_cleanup"
Any help would be appreciated!!!
Don,
I'm not sure you're using our version of mod_auth_mysql 2.2. As far as I know, there's never been a ./configure command for our version. But that was before my time, so I really can't say.
I'm concerned about why register_cleanup wasn't found in your current version of Apache. I checked the Apache docs and I can't find anything relating to this function being removed in Apache 1.3.x, and we need to call it to clean up when the pool is destroyed. And this part of the code hasn't changed for several versions.
Can you tell me exactly which version of Apache you're running? Also, if possible, what configuration parameters you used to build Apache? That would help us duplicate your problem.
Thanks,
Jerry
The version I'm using shows:
Apache authentication module for MySQL v2.20
Maintainer: Zeev Suraski <bourbon@netvision.net.il>
Maybe it's an old old version, or maybe not....
In any case, I'm building Apache 1.3.4 (the latest sources), and the configure I'm using is:
./configure --prefix=/var/shc/apache --enable-module=rewrite --enable-module=info --enable-module=log_agent --enable-module=log_referer --enable-module=so --server-uid=shcapache --server-gid=shcapache
I've patched it for the latest SSL, and then built it normal.
I'm also building PHP along with it. Don't know if that is messing things up or not.
Maybe something has changed with the latest Apache? Perhaps I should try a slightly older version? What was the last version you built?
Thanks!!!!!
I'm not familiar with that version; it sounds like you need to contact the author for assistance.
We only support the recent versions in this project.
PHP shouldn't affect it - it makes no changes to the Apache code.. However, I don't know what your SSL patch did.
Your Apache config parameters look good, but I'll have to dig around some to see if there's something special needed. But the main one should be --enable-module=so, and you have that.
Generally, Apache doesn't change the API's when changing minor releases - only major releases and versions. Minor ones are generally bug fixes.
Also, the fact you didn't get a compile error on mod_auth_mysql indicates the function should be there.
Is there any chance you have two versions of Apache on your system - and are compiling/linking against one but running on another? It's one possibility.
I have tested with 1.3.31 with no problems. Others have tested with 1.3.33 and I believe 1.3.34 with no problems such as you've described.
It's very strange.