This is the mail archive of the cygwin@sources.redhat.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: KSH is pdksh


For what it's worth, I started taking a stab at compiling AT&T's ksh.  Man,
they certainly do use some wacky packaging tools.  At any rate, here are
some of the problems that I encountered, and what I did about them.

1) The 'package' script wants to see getopts.  Thus, I made sh a link to
bash to work around this.

2) The 'package' script always seemed to fail, complaining about not being
in the package root (when it was).  I solved this by editing the package
script to not exit if that particular error happened.

3) I made a link from gcc->cc for convenience sake (read: laziness).

At this point the 'mamake' utility seems to start configuring/making things.
However, it spits out the following errors:

/home/matts/att/src/lib/libast/include/ast_std.h:672: conflicting types for
`rea
d'
/usr/include/sys/unistd.h:72: previous declaration of `read'
/home/matts/att/src/lib/libast/include/ast_std.h:690: conflicting types for
`wri
te'
/usr/include/sys/unistd.h:99: previous declaration of `write'

Can anyone suggest an elegant way around this?

thanks,
-Matt Smith


> >
> >It would sure be nice to bring a maintainable ksh into the Cygwin
> >fold, just for the sake of increased Unix compatibility.
>
>
> Volunteers welcome!:-)
>



--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]