Message-ID: <6910a60802111113w4b39c20aye683104e4dcbaf63@mail.gmail.com>
Date: Mon, 11 Feb 2008 20:13:24 +0100
From: "Reini Urban" <rurban@x-ray.at>
To: cygwin@cygwin.com
Subject: Re: iconv vs. libiconv confusion
In-Reply-To: <002b01c86cdf$ddb20f40$2e08a8c0@CAM.ARTIMI.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <002b01c86cdf$ddb20f40$2e08a8c0@CAM.ARTIMI.COM>
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

2008/2/11, Dave Korn <dave.korn@artimi.com>:
>   Does anyone understand the difference between iconv_open and libiconv_open,
> and why the libiconv package supplies a header that declares only iconv_XXX
> and a library that defines only libiconv_XXXX?  I find this confusing, and so
> does ./configure and friends.

libiconv_xxx was used for a seperate and probably newer libiconv installed,
while iconv_xxx usually comes with glibc.
Is libiconv from me? I'll have to check these mistakes then.

clisp, where iconv is coming from, never used libiconv_*,
its iconv.m4 just tests for the main iconv_open, _close functions.

I mostly see these errors in php libs.
-- 
Reini

--
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/