Re: libiconv

[Sam S. <sd...@gn...>]

> * In message <266...@ic...>
> * On the subject of "Re[2]: symbol SYSTEM::*COMPILING-FROM-FILE* has no value"
> * Sent on Fri, 11 Jan 2002 11:02:18 +1000
> * Honorable Arseny Slobodjuck <am...@ic...> writes:
>
> Hello, Raymond,
> 
> Friday, January 11, 2002, 7:39:35 AM, you wrote:
> 
> Raymond> I checked.  unix.d says:
> Raymond>     extern_C size_t iconv (iconv_t cd, ICONV_CONST char * *inbuf,
> Raymond>     size_t *inbytesleft, char * *outbuf, size_t* outbytesleft);
> Raymond> but <iconv.h> on Solaris 7 says:
> Raymond> extern size_t   iconv(iconv_t, const char **, size_t *, char **, size_t *);
> Raymond> So configure must be getting ICONV_CONST wrong.
> 
> I'm still digging that iconv stuff when having the time (not much).
> I'am not unix expert at all. But I've partially understood what happen
> with iconvs. And there is a questions:
> 
>   1. Should clisp use system installed iconv where it's available or
>   it should build it's own iconv ?

the only adequate iconv is in glibc 2.2 (right, Bruno?)

>   1.1. Currently, buid of internal libiconv taking place at configure
>   stage. Should it be installed on system in process of configure ?
>   Shouldn't it being built in the build directory instead of original
>   source location ?

right.

>   2. main (root) confilgure builds libiconv _after_ it executes
>   src/configure, so if you have no libiconv installed, checks for it in
>   src/configure having no sense.

libiconv is built for the benefit of gettext, not the main CLISP (right,
Bruno?)

-- 
Sam Steingold (http://www.podval.org/~sds)
Keep Jerusalem united! <http://www.onejerusalem.org/Petition.asp>
Read, think and remember! <http://www.iris.org.il> <http://www.memri.org/>
Daddy, why doesn't this magnet pick up this floppy disk?