Geoffrey Young wrote:

Stas Bekman wrote:

Geoffrey Young wrote:


I haven't run my nightly builds in a while, but I get the following
failures
against 2.0.46 at the moment:

t/apr-ext/table.........................ok
42/52/perl/perl-5.8.4/bin/perl:
relocation error:
/src/mod_perl-2.0/blib/arch/Apache2/auto/APR/Table/Table.so: undefined
symbol: apr_table_compress


That sounds familiar. We provide the backcompat layer for that function,
remember? I think you added it. :)


yes, I remember.  IIRC it is in modperl_apache_compat, but only so that I
can use apr_table_compress in mod_perl internally.  the proper solution here
is to only support apr_table_compress in APR if APR itself supports it.  I'm
not familiar enough with what you guys are doing in the separation process
to know how to go about that.

ah, now it's clear. it's implemented in 2.0.47, right?
Hmm, 2.0.47 was released a year ago. Do you think we may be should just drop 2.0.46? I wonder how many 2.0.46 users are out there. Poll the list?


If not we need to add the C compat layer object to the APR.so linking, which shouldn't be too hard to do.

t/api/request_rec.t has a handful of failures but looks like it is
autogenerated, which may be the cause of the error - right now it's under
cvs control so it may be out of date.


Yes, it's no longer autogenerated. You didn't check the output of 'cvs
up', you had collisions which you needed to resolve by removing
t/api/request_rec.t


yes, I saw the collisions, and I removed the file.  your other suggestion
made things work.  thanks.

Excellent!

--
__________________________________________________________________
Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/     mod_perl Guide ---> http://perl.apache.org
mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to