i would have said that the errors were coming from a failure to link Apache::Request to libapreq. in a diffident, mumbled sort of a way.
But Apache::Request is a part of libapreq.
ah. i dimly grasp the wrongness of this end of the stick and let go of it as if burnt.
i assumed that libapreq was the name of the C library - what the apache site refers to as a 'Generic Apache Request Library for manipulating request data via the apache api', and that Apache::Request was a wrapper around that to expose those functions in perl. from what you're saying i glean that actually libapreq is just the name of the whole thing? oops.
No it's not, libapreq is a C library, and then there are Perl (XS) interfaces to
libapqreq: Apache::Request, Apache::Cookie and Apache::Upload.
Granted it's a tad confusing since the whole thing is packaged under
the name libapreq as a CPAN distro.
-- Eric Cholet
