Hi All,
Thanks to the hard work of those who have gone before me, I've managed to
get all the Perl-oriented tools I need working under Mac OS X. I was
spending a lot of effort on documenting what I needed to do, so I went the
extra mile and wrote up an article on what I did and how I did it. And
At 11:55 AM -0700 4/11/2002, Alex S wrote:
>
>My real point is not a matter of technical savviness. It's more that
>something Apple pushed out broke something I, and others have setup. I
>might even have been more cautious about the update IF they listed it as
>something being updated, which
On 4/11/02 9:46 AM, "Rick Frankel" <[EMAIL PROTECTED]> claimed:
> Tangential to the mod_perl issue, has anyone else noticed that
> ~/.MacOSX/environment.plist is no longer being parsed on login after
> the security update?
Seems to be working for me.
Regards,
David
--
David Wheeler
PK, here, stands to represent the opposite of myself... he represents
the "bulk" that I was referring to that would have the knowledge to do a
very simple CPAN install/update, and even cut'n'pasting commands for a
manual recompile (which are easy to find with a quick google search),
but wouldn
On 4/11/02 1:31 PM, "PK Eidesis" <[EMAIL PROTECTED]> wrote:
>
> But this whole Perl 5.6.1, mod_perl crapola has left me very befuddled. In
> some ways I have myself to blame because I dicked with Apple's stock 5.6.0
> install... I never should have done that. Otoh, Perl/CPAN/mod_perl install
> sh
On Thursday, April 11, 2002, at 01:28 PM, Alex S wrote:
> Well, since Apple is the one pushing out the update to Apache (and
> related modules), they know what they're changing (including libraries).
It's true that Apple knows what *they're* changing, but the problem is
that they have no way o
Oh... and despite the "shoulds" and "shouldn'ts"... I hope this thread
will help enlighten and educate those who need to know, and solve their
problems. That's why I summarized my solution about the linking of
libraries in the first place.
It's often VERY annoying when I have a problem, and
Sherm Pendley wrote:
> No need to wonder about what it's doing - just watch the output when
> you configure and make Perl, and then you'll know for certain.
>
> The answer to your question is, no, the Perl compile/installation does
> not do any relinking for things that were linked against libp
On Thursday, April 11, 2002, at 12:42 PM, Alex S wrote:
> I wonder if the Perl compile/installation does the relinking for
> things that were dependent on it (would be a good thing, making things
> simple, and catching everything).
No need to wonder about what it's doing - just watch the outp
Tangential to the mod_perl issue, has anyone else noticed that
~/.MacOSX/environment.plist is no longer being parsed on login after
the security update?
rick
Chris Devers wrote:
>>>But isn't it supposed to not work unless it offers error messages?
>>>
>>You would think so
>>
>
>I was having fun with the [snipped] double negative earlier... :)
>
Yeah, I kinda figured... just covering the bases. ;)
>>Well, the thing is, I don't think it even gets tha
Sherm Pendley wrote:
>> wondering if the mod_perl library was reinstalled with the new Apache
>> (probably), which had some dynamic linking done, designed for perl 5.6.0
>> (or possibly vice-versa), and the updated copy got "out of sync" with
>> the
>> newer perl.
>
>
> Of course it got out of s
On Thu, 11 Apr 2002, BeardedDragon.org wrote:
> On Thu, 11 Apr 2002 10:05:46 -0400 (EDT), Chris Devers wrote:
>
> > But isn't it supposed to not work unless it offers error messages?
>
> You would think so
I was having fun with the [snipped] double negative earlier... :)
> > It's only a partial
On Thursday, April 11, 2002, at 11:32 AM, BeardedDragon.org wrote:
> wondering if the mod_perl library was reinstalled with the new Apache
> (probably), which had some dynamic linking done, designed for perl 5.6.0
> (or possibly vice-versa), and the updated copy got "out of sync" with
> the
> ne
On Thursday, April 11, 2002, at 09:51 AM, Sherm Pendley wrote:
> On Thursday, April 11, 2002, at 10:34 AM, Puneet Kishor wrote:
>
>> I have started experiencing these problems on my iBook ever since I
>> upgraded Perl to 5.6.1.
>
> When you did that, did you also recompile mod_perl, or at leas
On Thursday, April 11, 2002, at 10:34 AM, Puneet Kishor wrote:
> I have started experiencing these problems on my iBook ever since I
> upgraded Perl to 5.6.1.
When you did that, did you also recompile mod_perl, or at least install
a version of mod_perl that's compiled against Perl 5.6.1? If yo
On Thu, 11 Apr 2002 09:34:09 -0500, Puneet Kishor wrote:
> if it is a general mod_perl issue then it should be happening to, and be
> well documented for, a lot of other users. I have done some bg search on
> this, and not found anyone else experiencing the same symptoms. That is,
> until Alex
obviously, right the load and add module lines for mod_erl are commented
out. But, the rigmarole is the same...
1. I start the computer; Apache is not working.
2. Try to restart it; it doesn't work (no errors).
3. I comment out the lines (as below), start Apache; it works.
4. I uncomment the lin
On Thu, 11 Apr 2002 19:20:00 +1000, Ken Williams wrote:
> > However, I figured it out. I had updated perl to 5.6.1 when
> > installing a module through CPAN.
>
> Don't you hate it when that happens?
Yeah, although I don't think it does it automatically in OS X. The
compile fails, due to HFS
Chris, (Alex),
On Thursday, April 11, 2002, at 09:05 AM, Chris Devers wrote:
>
> It's only a partial remedy, but are your mod_perl related config
> statments
> wrapped in an appropriate block?
>
>
> PerlSendHeader On
> PerlHandler Apache::Registry
> AddHandler perl
On Thu, 11 Apr 2002 10:05:46 -0400 (EDT), Chris Devers wrote:
> But isn't it supposed to not work unless it offers error messages?
You would think so, but there are no error messages pertaining to a
problem. And Apache ends up not running. I think that is the most
disturbing thing.
> It's onl
On Thu, 11 Apr 2002, Puneet Kishor wrote:
> I think I wrote too soon... my Apache/mod_perl combo is back to the same
> as it was... that is, not working without any error messages.
But isn't it supposed to not work unless it offers error messages?
;)
It's only a partial remedy, but are your mo
Alex,
I think I wrote too soon... my Apache/mod_perl combo is back to the same
as it was... that is, not working without any error messages.
I am really getting sick of this.
On Thursday, April 11, 2002, at 02:48 AM, Alex S wrote:
> Alex S wrote:
>
>>> I know this doesn't help you much, but
On Thursday, April 11, 2002, at 05:48 PM, Alex S wrote:
>
> However, I figured it out. I had updated perl to 5.6.1 when
> installing a module through CPAN.
Don't you hate it when that happens?
> My other Mac that was working still had 5.6.0. So, I decided to
> downgrade perl back to 5.6.0.
Alex S wrote:
>> I know this doesn't help you much, but maybe it will give some insights.
>
>
> Thanks for the response. I think my next step will be to download the
> update and try to rerun it manually. Maybe the update had some minor,
> unreported failure when I ran it.
Okay.. well, the
25 matches
Mail list logo
