iconv related failure
| From: | Cynic | Date: | Wed, 18 Jul 2001 19:19:35 +0000 |
| Subject: | iconv related failure | ||
| Groups: | php.dev | ||
| Request: | Send a blank email to php-dev+get-60230@lists.php.net to get a copy of this message | ||
Hi there,
seems like I've just tracked the iconv failure to a dbeu's
commit.
I'm not sure if ./configure should be looking for libiconv_open
at all: looks like the function is actually called iconv_open.
Now, I know nothing about the buildconf|autoconf|etc stuff,
but it looks like it was triggered this behavior w/ the following
commit:
http://marc.theaimsgroup.com/?l=php-cvs&m=98096027003970&w=2
specifically:
+#if HAVE_LIBICONV
+#define icv_open(a,b) libiconv_open(a,b)
+#define icv_close(a) libiconv_close(a)
+#define icv(a,b,c,d,e) libiconv(a,b,c,d,e)
+#else
+#define icv_open(a,b) iconv_open(a,b)
+#define icv_close(a) iconv_close(a)
+#define icv(a,b,c,d,e) iconv(a,b,c,d,e)
+#endif
can anyone tell me if this is actually right? I cannot test it
right now, but I'll try to build the snapshot with only the "else"
branch of the if and report tomorrow.
cynic@mail.cz
-------------
And the eyes of them both were opened and they saw that their files
were world readable and writable, so they chmoded 600 their files.
- Book of Installation chapt 3 sec 7