On Saturday, October 20, 2001, at 02:50 AM, Jim Cooper wrote: > Now we can get back to perl.
Speaking of which, I just spent another late night trying to get a mod_perl to work on OS X. On the bright side, following Ray Zimmerman's excellent instructions posted to this list earlier (but substituting apache 1.3.22 for 1.3.20): --- From: Ray Zimmerman <[EMAIL PROTECTED]> Date: Wed Oct 03, 2001 10:35:10 AM US/Eastern To: [EMAIL PROTECTED] Subject: SUMMARY: installing perl-5.6.1 on Mac OS X 10.1 From: Ray Zimmerman <[EMAIL PROTECTED]> Date: Wed Oct 03, 2001 05:03:39 PM US/Eastern To: [EMAIL PROTECTED], modperl List <[EMAIL PROTECTED]> Subject: Re: OT: secure mod_perl enabled apache on MacOSX 10.1 --- I was able to create a working, statically linked mod_perl httpd. The down side is that attempting to load Apache::Request or Apache::Cookie causes errors on startup: --- localhost [apache]# bin/apachectl start dyld: /usr/local/apache/bin/httpd Undefined symbols: _ap_clear_pool _ap_day_snames _ap_find_path_info _ap_get_client_block _ap_getword _ap_getword_conf _ap_getword_nc _ap_hard_timeout _ap_ind _ap_kill_timeout _ap_log_rerror _ap_make_array _ap_make_dirstr_parent _ap_make_sub_pool _ap_make_table _ap_month_snames _ap_note_cleanups_for_file _ap_os_escape_path _ap_palloc _ap_pcalloc _ap_psprintf _ap_pstrcat _ap_pstrdup _ap_pstrndup _ap_push_array _ap_reset_timeout _ap_setup_client_block _ap_should_client_block _ap_table_add _ap_table_do _ap_table_get _ap_unescape_url _perl_request_rec _sv2request_rec bin/apachectl start: httpd could not be started --- As far as my work is concerned, a mod_perl httpd that can't load both Apache::Request and Apache::Cookie is useless :( So, 6 months into OS X's life, and I still can't do one of the biggest things I was looking forward to doing in my new Unix-based OS. Bleh, this is very depressing... -John
