Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Wed, 3 Sep 2003 18:22:54 -0700 From: "David A. Case" To: cygwin AT cygwin DOT com Subject: apparent conflict between mutt-1.4-1 and libiconv-1.9.1-3 Message-ID: <20030904012254.GA3880@scripps.edu> References: <136-1786434247 DOT 20030816134218 AT familiehaase DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <136-1786434247.20030816134218@familiehaase.de> User-Agent: Mutt/1.4i It looks like a recent update to libiconv generates a conflict with mutt (version 1.4-1). Here is at least one symptom: if you reply to a message that contains international characters, mutt aborts with the following message: assertion "errno == E2BIG || (BUGGY_ICONV && (errno == EILSEQ || errno == ENOENT))" failed: file "../mutt-1.4-1/sendlib.c", line 743 Line 743 in sendlib.c is checking the return status of an iconv() call, although I don't know exactly what it is doing. Reverting to an earlier version (1.8-3) of libiconv solves this problem, but reverting causes lots of other problems for me: e.g. "ls" can't find the symbols it in cygiconv-2.dll. I recompiled mutt from sources, linking to the latest libiconv package, and the problem cited above went away; so it may be that all that is needed is a simple recompile. But someone familiar with iconv might be able to tell more quickly than I could what could be causing the assertion failure listed above (e.g. is BUGGY_ICONV now set to something different than before?) cygcheck.out is attached. ..thanks...dave case -- 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/