On Wednesday, July 24, 2002, at 07:36 PM, Steve Linberg wrote:
> So here's the question, in which I reveal my ignorance of mod_perl
> internals: does mod_perl use whichever Perl is on the machine when the
> server starts at runtime, or does Perl get wired into it when it's
> built?
To confirm:
On 25/7/02 at 14:07, [EMAIL PROTECTED] (Scott Brown) wrote:
> Maybe I am slow, but I still cant get the dyld undefined symbols to
> fix
> itself. I installed all default (ie overwrote the existing
> installation)
> Any help would be great!
I actually followed the `rm -rf /Library/Perl' route
Maybe I am slow, but I still cant get the dyld undefined symbols to fix
itself. I installed all default (ie overwrote the existing installation)
Any help would be great!
thanks
Scott Brown
- Original Message -
From: "Geoffrey F. Green" <[EMAIL PROTECTED]>
To: "David Wheeler" <[EMAIL PRO
After a good bunch of hours trying and retrying to get everything going
again, I did succeed in rebuilding apache and mod_perl (and Apache::ePerl,
which was a nice bonus). I used a combination of Randal's, David
Wheeler's, and some of my own configs, and this is what finally gave me
joy.
(All of
> "Chris" == Chris Reinhardt <[EMAIL PROTECTED]> writes:
Chris> Does anyone know why the paths are set as they are on OS X. Is it just
Chris> following the apple install? Or are their deeper reasons?
Here's what I use for my perlsnap builds:
./Configure -des -Dusedevel -Uversiononly -Dp
On Wed, 24 Jul 2002, Steve Linberg wrote:
> I installed 5.8.0 tonight from source and it was pure joy - smooth
> install, and amazingly smooth install of modules with CPAN afterwards. I
> encountered the dyld problems as documented on the list, and the solutions
> seemed to work, rebuilding the