Thank you, Doug. This turned out to be the solution. A complicating factor was that I was building from .deb files, since I run Debian, and the mod_perl source .deb blows up. I wanted to do things in such a way that I ended up with good .debs, to make it easier to deinstall, replace, etc.
I did manage to build an Apache deb file with statically linked mod_perl. This works. If anyone is interested in the deb, let me know. If there is a good common place to post it, let me know that, too. Otherwise, I can stick it up on my web site. I'd like to make a source deb, too, with the extra stuff needed for static mod_perl, but I'm not too sure about how to go about that. By the way, I've noticed that folks are having the same problem with RPMs from RedHat. I hope the developers just get it all fixed soon. ;-) (I have filed a bug report with Debian). Doug MacEachern wrote: > > one solution is to build Apache and mod_perl from source, and linking > mod_perl static instead of a dso. > > -Doug > > On Wed, 29 Sep 1999, Keith G. Murphy wrote: > > > I'm having a strange problem where apache is segfaulting when I start > > it. The only time I get the segfault is when DynaLoader.pm loads an > > ".so" file, for example, DBI.so, resulting from "use DBI" or "use > > Apache::DBI" in startup.pl. But "use Apache::Status", resulting in > > loads of Request.so, et al, also causes the segfault. > > > > I'm running Debian Linux, Slink, kernel 2.0.36. > > The relevant Debian packages are: > > apache-1.3.9-8 > > libapache-mod-perl-1.21-5 > > libc6-2.1.2-5 > > libdbi-perl_1.12-1 (that's where the DBI.so comes from) > > > > I've tried compiling and using the packages from CPAN also, but get the > > same thing. I don't feel at this point it's the .so files themselves, > > but a problem with apache or mod-perl. > > > > I should mention, though, that this problem seemed to go away Friday > > upon an Apache reinstall, only to start recurring, which made me suspect > > hardware problems. Memory tests show nothing, though, and the problem > > is consistent and isolated to this situation. > > > > Anyone else have problems with this configuration or have any clue where > > to look next? > > > > TIA. > >
