I had koctave working on my ibook, but know when I load it I get the  
following fatal error message with:

Konsole is unable to open a PTY (pseudo teletype).  It is likely that  
this is due to an incorrect configuration of the PTY devices.  Konsole  
needs to have read/write access to the PTY devices.

Koctave then quits when I click ok on the error dialog window.  Of  
course I can use octave from the command line, but I would like to get  
to the bottom of this.  Does anyone know what I need to do to fix  
this?  Perhaps it is some config file, or do I need to reinstall  
something? Konsole runs fine by itself.

The only thing I know that happened on my ibook between koctave  
working and then this error message is that pth2-dev-2.0.7-1021 hangs  
when it began the first test.  I closed Terminal, removed the fink- 
buildlock, restarted my machine in case something was wrong in  
memory,  and tried to install pth2-shlibs and pth2-dev again.  The  
terminal again was hung during first test.  I don't have a crash log  
as I had to close Terminal again.  I still have the /sw/scr/fink.build  
file though.  Does anyone have any idea why compiling and installing  
this could be a problem?  By the way, I had not problem installing  
these files on my iMac G5. Thanks for the help.

My kit consists of:

Package manager version: 0.28.6
Distribution version: selfupdate-rsync Wed Nov 26 10:06:22 2008, 10.5,  
powerpc
OSX 10.5.5
XTools 3.11
powerpc-apple-darwin9-gcc-4.0.1 (GCC) 4.0.1 (Apple Inc. build 5488)

Gary K Olson

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Fink-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fink-users

Reply via email to