>Huh? >It tells you EXACTLY what is wrong.
No, not really. One reason is that it's not immediately clear (to me) which file can't be loaded. Is it Request.so or libapreq.so.1 that can't be loaded? This ambiguity is further blurred when you know both files are installed. And of course the other reason is that if the solution to the problem was so obvious from the error message, somebody would have posted a solution before I figured it out (with help from you guys). Searching the mailing list archives indicates that method name resolution is not exacly a new problem with mod_perl. Just ask this guy => http://lists.fsck.com/pipermail/rt-users/2002-September.txt. It's the exact same problem with the exact same error message, only in different clothing (he's having trouble with the Apache::Cookie object rather than the Apache::Request object). In the interest of full disclosure, other possible solutions include resetting /etc/ld.so.conf or the LD_LIBRARY_PATH variable to include more places to look for shared object files (only recently figured this out). But again, unless you're somewhat experienced or have encountered this class of bug before, this won't necessarily be the obvious place to look at first. Anyway enough of my babbling. Now that the answer is out there, hopefully it'll help out the poor souls who run into this issue in the future. Later, DeAngelo -----Original Message----- From: Ged Haywood [mailto:ged@;www2.jubileegroup.co.uk] Sent: Thursday, November 07, 2002 10:01 PM To: DeAngelo Lampkin Cc: mod_perl Mailing List Subject: RE: Can't locate object method "new" via package "Apache::Request" (via Mason)...SOLVED Hi there, On Thu, 7 Nov 2002, DeAngelo Lampkin wrote: > A file called libapreq.so.1 was located in /usr/local/lib > (should have been in /usr/lib) [snip] I ended up getting this thing: > > Syntax error on line 362 of /usr/local/apache/conf/httpd.conf: > Can't load >'/usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi/auto/Apache/Request/Request.so'\ > for module Apache::Request: libapreq.so.1: cannot open shared object file:\ > No such file or directory [snip] > > This isn't the most helpful error message in the world. Huh? It tells you EXACTLY what is wrong. 73, Ged.
