CC: | bugs-TermReadKey [...] rt.cpan.org |
Subject: | Re: problem with Term::ReadKey on one special linux box |
Date: | Fri, 24 Mar 2006 14:01:04 +0000 |
To: | Daniel Schroeer <Daniel.Schroeer [...] Physik.Uni-Muenchen.DE> |
From: | Jonathan Stowe <jns [...] gellyfish.com> |
On Fri, 2006-03-24 at 12:19, Daniel Schroeer wrote:
Show quoted text
Yeah but you're probably only going to like it a bit better than my
previous (as it turns out incorrect) advice: it appears that the problem
happens with Perl version 5.8.0 on any platform and it works fine with
perl 5.8.1 on a similar platform to yours. The 5.8.0 release of perl
had multiple problems not limited to this one (as is is common with .0
releases it seems) and you really will need to use a newer Perl if you
want Term::ReadKey to work. If you are unable to upgrade the perl
provided with the distribution then you should install one side-by-side
with the existing one by using a different PREFIX when you install it.
I don't think that there will be anything I can do in Term::ReadKey to
fix this (except noting the problem in the README.)
/J\
--
This e-mail is sponsored by http://www.integration-house.com/
> > No, I'm as lost as you are. I have never had a report similar to this
> > and I can't think of any reason why this should happen.
> >
> > Can you send me the output from:
> >
> > perl -V
> > stty --all
> > perl -Mblib -e' use Term::ReadKey; print &Term::ReadKey::blockoptions() '
> > perl -Mblib -e' use Term::ReadKey; print &Term::ReadKey::termoptions() '
> >
> > the cchars.h from your TermReadKey directory.
>
> Thanks for your interest. I have attached this information.
>
> > I think in the end of the day that the fix will be to upgrade your OS
>
> Usually I would, but with this computer I run measurements here in the lab
> (with my Lab::VISA module). For this I need a kernel module that is still
> only available for kernel 2.4. So at this point an upgrade is not an
> option for me.
>
> I will be really happy if you can read something from the tea leaves.