On Monday 06 April 2009 01:06:11 am Adriaan de Groot wrote: > So up until recently it did work. You don't say what the nature of "behave" > is though -- does it not compile? Not run?
To repeat David Naylor, it builds fine, but all glyphs at runtime are square boxes. > > > So which one is implemented incorrectly, libiconv or glibc? If Qt > > > assumes glibc, which almost by definition means Linux only, then a bug > > > should be filed with Nokia to turn off iconv support for all non-Linux > > > systems. > > The traditional difference is > > size_t iconv(iconv_t cd, > char **inbuf, size_t *inbytesleft, > char **outbuf, size_t *outbytesleft); > > in some implementations (UNIX98 standard?), inbuf is a const char **. The libiconv manpage shows that it's using const char** inbuf. The odd thing is that libiconv is a GNU implementation, so it should have the same behavior as the glibc version. I notice in the libiconv docs, it says: "On systems other than GNU/Linux, the iconv program will be internationalized only if GNU gettext has been built and installed before GNU libiconv. This means that the first time GNU libiconv is installed, we have a circular dependency between the GNU libiconv and GNU gettext packages..." <http://www.gnu.org/software/libiconv/> Perhaps this is the source of the problem. Real life has been intruding on my FreeBSD playtime, so I don't know when I can get a chance to poke around in this area. -- David Johnson _______________________________________________ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
