On 3/15/06, Tom Phoenix <[EMAIL PROTECTED]> wrote:
> On 3/15/06, Jerry Kemp <[EMAIL PROTECTED]> wrote:
>
> > # perl -MCPAN -e shell
> > cpan> reload index
> > Out of memory!
>
> Was your perl compiled to use your system's malloc(), or Perl's own?
> You can find out with a command like this one:
>
> perl -MConfig -lwe 'print $Config{usemymalloc}'
>
> Whichever you used, if you try recompiling with the other, your "Out
> of memory" problems may silently vanish. Then again, maybe not; but it
> seems worth a try at this point. Some systems only work properly with
> Perl's malloc(), others only with their own.
>
> Good luck with it!
>
> --Tom Phoenix
> Stonehenge Perl Training
Beat me to it. I was just thinking on the subway this morning, "I
wonder if Solaris has messed with their malloc()." But if that's the
case, shouldn't the problem be cropping up elsewhere, too? Why would
CPAN be the only module failing?
I had one more question for Jerry, too: is all of cpan dead, or just
the shell? What happens with something like:
perl -MCPAN -e 'install Bundle::CPAN'
-- j
--------------------------------------------------
This email and attachment(s): [ ] blogable; [ x ] ask first; [ ]
private and confidential
daggerquill [at] gmail [dot] com
http://www.tuaw.com http://www.dpguru.com http://www.engatiki.org
values of β will give rise to dom!
