Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Make Failure on SunOS-4.1
- X-seq: zsh-workers 14094
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxxxxxxxxx>
- To: Peter Stephenson <pws@xxxxxxx>, zsh-workers@xxxxxxxxxx (Zsh hackers list)
- Subject: Re: Make Failure on SunOS-4.1
- Date: Wed, 25 Apr 2001 14:41:52 +0000
- In-reply-to: <Tc0a88d015321834e70@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <Tc0a88d015321834e70@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
On Apr 25, 10:55am, Peter Stephenson wrote:
} Subject: Re: Make Failure on SunOS-4.1
}
} I don't want to produce a `final' pre-release until the termcap problems
} have gone. Is there something else to back out?
We could back out the `termcap' parameter entirely, and we could back out
the ability to use ${(k)terminfo} -- those were the changes that started
requiring the ncurses header files to be included even on systems that
have the old termcap as well.
Or we could change the termcap-search-order in configure.in to always try
to find ncurses first, and skip defining HAVE_TERMCAP_H when we find the
ncurses headers. (My understanding is that in the distant past of zsh,
there were some who objected to linking the shell against curses when it
would be sufficient to link against termcap, because curses is bloated.)
Or we could add another --enable flag, which switches between the two
states described above (in which case it should probably disable the
terminfo parameter entirely rather than just crippling it).
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
Messages sorted by:
Reverse Date,
Date,
Thread,
Author