That said, this is not an easy documentation problem to resolve. To
illustrate this, here's a mod_perl page that works:
#!/usr/bin/perl
use Apache2::RequestUtil ();
my $r = Apache2::RequestUtil->request;
$r->content_type("text/plain");
$r->print("works?");
And here is one that fails with the apreq module not loaded:
#!/usr/bin/perl
use Apache2::RequestUtil ();
use Apache2::Upload;
use IO::Handle;
open DBG, ">/tmp/dbg";
DBG->autoflush();
print DBG 1;
my $r = Apache2::RequestUtil->request;
print DBG 2;
my $req = Apache2::Request->new($r);
print DBG 3;
$r->content_type("text/plain");
print DBG 4;
$r->print("works?");
print DBG 5;
The failing program needs those print statements since nothing shows up
even in the apache error log for this failure mode.
Probably perldoc Apache2::Upload should document the apreq issue, and
the upstream perl developers should get a polite request for a more
informative failure mode for this case (for webmin users).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318134
Title:
Apache2.so: undefined symbol: modperl_xs_sv2request_rec
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libapreq2/+bug/1318134/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
