Re: Probs using compile-command on Aix

[culliton@xxxxxx]

One more thing.

diff -rw jed-0.99-18.orig/src/pty.c jed-0.99-18/src/pty.c
22c22
< # if !defined (__linux__) && !defined(__CYGWIN__) && !defined(__FreeBSD__)
---
> # if !defined (__linux__) && !defined(__CYGWIN__) &&
!defined(__FreeBSD__) && !defined(_AIX)


This now seems to be working correctly for me...

> Whoopsie...
>
>> Aha.  Looks like AIX has "sys/pty.h" rather than "pty.h".  The changes
>> to
>> configure and src/pty.c look pretty simple:
>>
>> diff -c jed-0.99-18.orig/configure jed-0.99-18/configure
>> *** jed-0.99-18.orig/configure  Mon Feb 13 11:51:58 2006
>> --- jed-0.99-18/configure       Mon Oct 16 13:40:17 2006
>> ***************
>> *** 5148,5153 ****
>> --- 5148,5154 ----
>>   fcntl.h \
>>   sys/fcntl.h \
>>   pty.h \
>> + sys/pty.h \
>>
>>   do
>>   as_ac_Header=`echo "ac_cv_header_$ac_header" | $as_tr_sh`
>>
>> diff -c jed-0.99-18.orig/src/pty.c jed-0.99-18/src/pty.c
>> *** jed-0.99-18.orig/src/pty.c  Mon Feb 13 11:51:58 2006
>> --- jed-0.99-18/src/pty.c       Mon Oct 16 13:41:37 2006
>> ***************
>> *** 28,33 ****
>> --- 28,37 ----
>>
>>   #ifdef HAVE_PTY_H
>>   # include <pty.h>
>> + #else
>> + # ifdef HAVE_SYS_PTY_H
>> + #  include <pty.h>
>
> Should be "<sys/.pty.h>" sigh...
>
>> + # endif
>>   #endif
>>
>>   static int pty_setup_slave_term (int slave, int raw)
>>
>>
>> I'm still in the process of testing these, but independent confirmation
>> would be a good thing.
>>
>>> I'm pretty sure that's it.  I just encountered the same problem with
>>> the
>>> most recent version of jed on a new AIX 5.3 system I'm setting up at
>>> work,
>>> although I haven't had time to go poke at it yet.  I seem to remember
>>> encountering and solving this problem before, so a search of the
>>> mailing
>>> list archives might turn up the answer.
>>>
>>>> Hagemann, Robert <rhagemann@xxxxxxxxxxxx> wrote:
>>>>>On both versions I can't use the command 'compile'.
>>>>>All I got is 'unable to open /usr/bin/ksh process.
>>>>
>>>> Do you have access to the config.h file generated when compiling jed?
>>>> I suspect the problem is that jed does not know how to properly create
>>>> or interact with ptys on your system.  The config.h file may provide
>>>> some additional insight.
>>>>
>>>> Thanks,
>>>> --John
>>>>
>>>> --------------------------
>>>> To unsubscribe send email to <jed-users-request@xxxxxxxxxxx> with
>>>> the word "unsubscribe" in the message body.
>>>> Need help? Email <jed-users-owner@xxxxxxxxxxx>.
>>>>
>>>
>>>
>>>
>>> --------------------------
>>> To unsubscribe send email to <jed-users-request@xxxxxxxxxxx> with
>>> the word "unsubscribe" in the message body.
>>> Need help? Email <jed-users-owner@xxxxxxxxxxx>.
>>>
>>
>>
>
>
>
> --------------------------
> To unsubscribe send email to <jed-users-request@xxxxxxxxxxx> with
> the word "unsubscribe" in the message body.
> Need help? Email <jed-users-owner@xxxxxxxxxxx>.
>