On Sat, 20 Mar 2004, Randy Kobes wrote: > On Fri, 19 Mar 2004, Geoffrey Young wrote: > > > the most recent mod_perl CVS snapshot throws these errors at me: > > > > modperl.def : error LNK2001: unresolved external symbol > > modperl_cmd_send_header > > > > same for modperl_cmd_setup_env, modperl_cmd_taint_check, > > and modperl_cmd_warn. > > > > at this point lots of files have compiled ok - modperl_flags, > > modperl_directives, etc but it croaks on mod_perl.so. I'm so close I can > > feel it :) > > > > anyway, all of those functions have been around for a while and they are in > > the function tables, so I don't know. if it matters, I'm using this > > makepl_args.modperl > > > > MP_DEBUG=1 > > MP_TRACE=1 > > MP_PROMPT_DEFAULT=1 > > MP_INST_APACHE2=1 > > MP_COMPAT_1X=0 > > > > with MP_AP_PREFIX on the command line. my perl is activeperl 5.8.3 build > > 809 installed direct from activestate. other than apache and VC++ it's a > > fresh win2k install, updated to the latest service pack only (sp4?) - no > > other security patches or upgrades (or software, really). > > Unfortunately, also with the cvs mp2, activeperl 5.8.3 and > Apache/2.0.49, I don't see those errors.
I spoke too soon - I think this is due to using MP_COMPAT_1X=0 (without it, it links fine). In src/modules/perl/modperl_cmd.c, taint_check, warn, send_header, and setup_env are defined if MP_COMPAT_1X is defined, and otherwise not, so I guess what's happening is that these symbols are in the .def file, and without MP_COMPAT_1X they're not being found. Perhaps what could be done is if MP_COMPAT_1X isn't defined that these symbols could be just noops? Otherwise, it should be possible within ModPerl::WrapXS to change how the def file is written, depending on the flags being passed in, but this would be messier. -- best regards, randy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
