Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <3EEF416E.4060309@ece.gatech.edu> Date: Tue, 17 Jun 2003 12:27:26 -0400 From: Charles Wilson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4a) Gecko/20030401 X-Accept-Language: en-us, en MIME-Version: 1.0 To: sds@gnu.org CC: cygwin@cygwin.com, Arseny Slobodjuck Subject: Re: libiconv package must be recompiled References: <3EEE549E.4040003@ece.gatech.edu> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sam Steingold wrote: >>I'm sorry, but while I have no objection to rebuilding the package per >>se, I need more than "stir in this magic powder and it works!" before >>I'm entirely comfortable with this. > > > as explains, > the apparent problem is that EILSEQ was conflated with ENOENT. > > I.e., both were defined to be the same number, which caused CLISP to > barf on innocuous errors. Ok, I misunderstood the original report -- I thought the problem was *solely* a cygwin kernel error. But, because EILSEQ/ENOENT are #defines, even after cygwin gets fixed, the compiled libiconv stays broken. libiconv was returning an EILSEQ error -- but because cygwin *at the time libiconv was compiled* defined EILSEQ == ENOENT, clisp was getting confused. So by recompiling libiconv against a newer cygwin that correctly defines EILSEQ, libiconv will return the correct error code and clisp will stop being confused. Got it. Look for a new release of libiconv soon. --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/