On Friday, December 27, 2002, at 12:28 PM, Ken Williams wrote:
Well, it's still a no go on OS X 10.1.5.
I used:
Apache 1.3.27
mod_perl 1.27
perl 5.6.1
libapreq 1.1_rc2
I followed the instructions in INSTALL.MacOSX up through installing Apache & mod_perl, with the patches from httpd-apreq-1.1 . All seemed fine, the mod_perl test suite completed successfully. Note that I had also modified apache's src/Configuration script to add mod_rewrite and mod_proxy, and that I used 'perl Makefile.PL EVERYTHING=1' for the mod_perl install.
One more thing that had to happen in the libapreq compile:
* set PERL5LIB to /Library/Perl so that the mod_perl modules I've just installed are preferred to the ones in /System/Library/Perl (this is really an error on Apple's part to have the @INC directories in the wrong order).
Okay, I can add that to the INSTALL.MacOSX file.
That gets me past libapreq's 'make', but I get the following upon 'make test':Strange. I've used Joe's 1.0 patch numerous times on 10.1x and 10.2.x, never with a problem.
[kw-009:~/Downloads/perl/httpd-apreq-1.1] ken% make test
t/httpd -f `pwd`/t/httpd.conf
dyld: t/httpd Undefined symbols:
_ApacheRequest___parse
_ApacheRequest_expires
_ApacheRequest_new
_ApacheRequest_script_name
_ApacheRequest_tmpfile
_ApacheUpload_find
make: *** [start_httpd] Error 67
[kw-009:~/Downloads/perl/httpd-apreq-1.1] ken%
So it looks like Apache::Request (and Apache::Cookie) aren't finding libapreq in the httpd binary. What's a good way to verify that it's actually compiled in there?Well, I know that during Apache's configure, it prints something to the terminal like "Statically compiling apreq support".
What's the compiler hint I can use on Jaguar to make it behave like it does on 10.1, Ken?
David
--
David Wheeler AIM: dwTheory
[EMAIL PROTECTED] ICQ: 15726394
http://david.wheeler.net/ Yahoo!: dew7e
Jabber: [EMAIL PROTECTED]
