GNOME Bugzilla – Bug 89635
libgnomevfs requires bind_textdomain_codeset
Last modified: 2004-12-22 21:47:04 UTC
When making gnome-vfs-2.0.1, I got an error "reference to libgnomevfs not resolved" while linking. In contrast, e.g. GConf checks whether this function is available at configure, and doesn't call it when it isn't there. Commenting out the offending line (gnome-vfs-init.c:85) seems to be a temporary fix; presumably the permanent fix is to add the check to configure.
Seth?
Created attachment 13661 [details] [review] one liner which checks if bind_textdomain_codeset exists
It seems that "something" in gnome already detects if bind_textdomain_codeset exists or not (gconf doesn't have a specific check for it in its configure, and gnome-vfs already had a HAVE_BIND_TEXT_DOMAIN_CODESET define), so this patch only checks if this is defined or not. Still, I'm not sure that GNOME supports platform where bind_textdomain_codeset doesn't exits (weird things will happen when trying to display translated content imo)
I was told that it is possible to pass some configure flags to build some stuff containing bind_textdomain_codeset on platforms without it (?).
This function is provided by GNU Gettext, and according to http://mail.gnome.org/archives/gtk-devel-list/2003-April/msg00066.html we can assume it is available. I'm not sure i18n will work at all if this bind_textdomain_codeset call isn't here