So I decided to "make install", then added the load module statement to
httpd.conf
and reran the make test.
Here is what resulted:
Use of uninitialized value in open at
/Library/Perl/5.8.1/darwin-thread-multi-2level/Apache/TestServer.pm
line 315.
make[1]: *** [run_tests] Error 255
make: *** [module_test] Error 2
As well as a lot of [debug] statements. Here is a sample:
[ debug] using httpd.conf inherited ServerRoot to resolve
modules/mod_apreq2.so
[ debug] modules/mod_apreq2.so successfully resolved to existing file
/usr/local/apache2/modules/mod_apreq2.so
[ debug] Found: apreq_module => mod_apreq2.c
[ debug] Skipping LoadModule of mod_apreq2.c
[ debug] Matched Apache revision Apache/2.0.55 2
Does it seem like I'm going to have problems with this, or am I good to
go?
I received no errors during make install...
Thanks,
Boysenberry
boysenberrys.com | habitatlife.com | selfgnosis.com
On Feb 24, 2006, at 7:21 AM, Joe Schaefer wrote:
Boysenberry Payne <[EMAIL PROTECTED]> writes:
When I do make test I get the following error:
waiting 60 seconds for server to start: .Syntax error on line 168 of
/Users/boysie/src/libapreq2-2.07/module/t/conf/httpd.conf:
Cannot load
/Users/boysie/src/libapreq2-2.07/module/apache2/.libs/mod_apreq2.so
into server: dyld: /usr/local/apache2/bin/httpd can't open library:
/usr/local/apache2/lib/libapreq2.2.dylib (No such file or directory,
errno =
2)\n
Any ideas?
We've seen that bug before. IMO it's a libtool bug on OS-X:
during compilation the linker should link mod_apreq2.so to the
locally built (not yet installed) libapreq2.2.dylib in library/.libs.
Then during "make install" libtool is supposed to massage mod_apreq2.so
so that the linkage path of the installed mod_apreq2.so points at the
installation path for libapreq2.2.dylib (/usr/local/apache2/lib).
But for some reason, on OSX it just always uses the installation path,
even during "make".
I don't think there's anything we can do about that, other
than point out the bug somewhere in our docs. Otherwise you
can install everything first and then run the tests.
--
Joe Schaefer
