On 21 Nov 2003, at 22:15, Chris Nandor wrote:
At 22:01 +0000 2003.11.21, william ross wrote:On 21 Nov 2003, at 20:54, Chris Nandor wrote:
In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED] (William Ross) wrote:
<snip>
In your case it looks like a broken link to libapreq. i had similar
errors with libapreq built through CPAN.pm, but I vaguely recall that
rebuilding it by hand seemed to work. It wasn't a new apache, though:
just the standard one, and i was so beset with error messages at the
time that it's hard to remember what worked.
But ... libapreq is what I am building/testing. I can't link libapreq
to
itself ... so I have no idea what to do here. Here's the complete
error:
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.
beg your pardon.
will
