X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-2.7 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_54,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By:	sourceware.org
Message-ID:	<49A76B15.9070703@cwilson.fastmail.fm>
Date:	Thu, 26 Feb 2009 23:24:53 -0500
From:	Charles Wilson <cygwin AT cwilson DOT fastmail DOT fm>
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.19) Gecko/20081209 Thunderbird/2.0.0.19 Mnenhy/0.7.6.666
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: lynx seems broken (Attn: ncurses maintainer)
References:	<d922b6650902241349k1f296641jcf58cfb19d3c29b9 AT mail DOT gmail DOT com> <49A5CFFB DOT 30001 AT cygwin DOT com> <d922b6650902251526w7f07c0ex51600f9bc7e916bc AT mail DOT gmail DOT com> <49A5D4AC DOT 4030700 AT cygwin DOT com> <utz6h2idk DOT fsf AT gmail DOT com> <49A6E198 DOT 7090507 AT acm DOT org>
In-Reply-To:	<49A6E198.7090507@acm.org>
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

David Rothenberger wrote:
> 
> Rolling back libncurses8 and terminfo to the previous release solves the
> problem for me. Recompiling lynx from source with the new libncurses8
> and terminfo packages also fixes the problem.
> 

Confirmed bug.  I've pulled the release.

Upstream has silently changed the API, but only for "broken linkers" --
in other words, if you are not ELF, you are "broken".  And apparently we
don't care about API compatibility for "broken" linkers.

It's not just cur_term. There are 43 symbols that were exported by
ncurses-5.5's cygncurses-8.dll but are missing from ncurses-5.7's
cygncurses-8 (with no changes in how the two packages were ./configured).

_nc_cap_hash_table
_nc_capalias_table
_nc_capcmp
_nc_captoinfo
_nc_check_termtype
_nc_check_termtype2
_nc_comment_end
_nc_comment_start
_nc_copy_entry
_nc_curr_file_pos
_nc_curr_token
_nc_disable_period
_nc_do_xmc_glitch
_nc_entry_match
_nc_find_entry
_nc_find_type_entry
_nc_get_hash_table
_nc_get_table
_nc_get_token
_nc_info_hash_table
_nc_infoalias_table
_nc_infotocap
_nc_init_entry
_nc_key_names
_nc_merge_entry
_nc_panic_mode
_nc_parse_entry
_nc_push_token
_nc_read_entry_source
_nc_reset_input
_nc_resolve_uses
_nc_resolve_uses2
_nc_save_str
_nc_set_writedir
_nc_slk_format
_nc_start_line
_nc_syntax
_nc_tic_expand
_nc_tic_written
_nc_trans_string
_nc_wrap_entry
_nc_write_entry
cur_term

Given that lack of consistency, I also worry if some existing symbols
have had their signatures changed. Sheesh.


OK. So, no problem: I'll just release ncurses-5.7-[2,11] with a dll
version bump to -9 (and a new libncurses9 package).  But how do I get
everyone's libncurses8 package back to the original API?

I guess I can modify libncurses8's setup.hint to explicitly declare that
the 5.5-3 version is current, thus superseding the bad -5.7-1 version...

I was really trying to avoid a DLL version bump with this release, but
it looks like that is not possible, due to poor API management upstream.

This also means that I must also roll back the terminfo database layout
change. Sigh.

--
Chuck

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -