RE: [Expectperl-discuss] Problems with IO::Tty on HPUX

[Marco M. <Mar...@co...>]

Don,
	Yore a champion!! I have made the recommended changes and IO::Tty
now works!! Also, as expected, Expect.pm is now working!!

Thanks very much for your help and quick response to my problem.

The very much appreciative

Marco

-----Original Message-----
From: Don Simonetta [mailto:don...@te...]
Sent: Tuesday, 21 November 2000 9:50
To: 'Marco Marinelli'; 'exp...@li...'
Subject: RE: [Expectperl-discuss] Problems with IO::Tty on HPUX


Here are the changes (in diff format) I made to IO-Tty-0.04 to make it work
on hp-ux. The changes are to Makefile.PL & Tty.xs. I have emailed these to
Roland, so they should eventually make their way into the official release.

BTW: The changes here also fix problems on dec/compaq alpha OSF1.


diff Makefile.PL*
17,28d16
< my $ccflags  = $Config{ccflags};
< my $cppflags = $Config{cppflags};
< 
< if ($Config{osname} eq "dec_osf") {
<     $ccflags = $ccflags . ' -std1 -D_XOPEN_SOURCE_EXTENDED';
< }
< 
< if (($Config{osname} eq "hpux") && ($Config{archname} eq "PA-RISC2.0")) {
<     $ccflags  = $ccflags  . ' +DAportable';
<     $cppflags = $cppflags . ' +DAportable';
< }
< 
74c62
< if( system(split(/\s+/, $Config{'cc'}), split(' ',$cppflags) ,'tst.c')) {
---
> if( system(split(/\s+/, $Config{'cc'}), split('
',$Config{'cppflags'}),'tst.c')) {
145d132
<     'CCFLAGS'       => $ccflags,


diff Tty.xs*
103c103
< #if !defined(SVR4) && (defined(__svr4__) || defined(_HPUX_SOURCE) ||
defined(_PowerMAXOS))
---
> #if !defined(SVR4) && (defined(__svr4__) || defined(_PowerMAXOS))
231c231
< #if defined(VOIDSIG) || defined(__osf__) || defined(_HPUX_SOURCE)
---
> #ifdef VOIDSIG
615d614
< 
622,623d620
< 
< #if !defined(_HPUX_SOURCE)
626d622
< #endif


-----Original Message-----
From: Marco Marinelli [mailto:Mar...@co...]
Sent: Monday, 20 November 2000 10:45 PM
To: 'exp...@li...'
Subject: [Expectperl-discuss] Problems with IO::Tty on HPUX


I am experiencing problems with the  IO::Tty on HPUX 11.0 and 10.20.
The IO::Tty module seemed to compile, make & install okay for me but the
'try' program just hangs when run it (note: I experience the same hangs when
using Expect.pm) 
I have tried the sample script in the CPAN IO::Tty module doco and that also
hangs (when reading from a tty slave)
I am using perl 5.06, Expect 1.08 & IO::Tty 0.04
Here is my test script:
------
#!/usr/bin/perl
use IO::Pty;
$pty = new IO::Pty;
$slave = $pty->slave;
foreach $val (1..10) {
print $pty "$val\n";
$_ = <$slave>; # I know the script hangs here when trying to read from the
slave tty.
print "$_";
} 
close($slave);
##end of test script
The following is the end part of a system call trace of this program
executing (using tusc):
open("/dev/pts/9", O_RDWR|0x800, 0666) ........................... = 4
fstat64(4, 0x400193b0) ........................................... = 0
fcntl(4, F_SETFD, 1) ............................................. = 0
sigsetstatemask(0x17, NULL, 2139032768) .......................... = 0
ioctl(3, TCGETA, 0x7f7f1418) ..................................... ERR#22
EINVAL
write(3, "1 \n", 2) .............................................. = 2
ioctl(4, TCGETA, 0x7f7f2d58) .....................................
[sleeping]
##end of trace.

Has anyone got IO::Tty (or Expect.pm) running on HPUX???

Any assistance appreciated 
Marco

This email and any attachments may contain privileged and
confidential information and are intended for the named
addressee only.  If you have received this e-mail in error, 
please notify the sender and delete this e-mail immediately. 
Any confidentiality, privilege or copyright is not waived or 
lost because this e-mail has been sent to you in error.  It 
is your responsibility to check this e-mail and any 
attachments for viruses.
_______________________________________________
Expectperl-discuss mailing list
Exp...@li...
http://lists.sourceforge.net/mailman/listinfo/expectperl-discuss

This email and any attachments may contain privileged and
confidential information and are intended for the named
addressee only.  If you have received this e-mail in error, 
please notify the sender and delete this e-mail immediately. 
Any confidentiality, privilege or copyright is not waived or 
lost because this e-mail has been sent to you in error.  It 
is your responsibility to check this e-mail and any 
attachments for viruses.