Mail Archives: cygwin/2003/06/17/12:30:37
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 <http://article.gmane.org/gmane.lisp.clisp.general/6767> 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/
- Raw text -