Date: Mon, 17 Feb 2014 09:27:22 -0800 (PST) From: Robert_Burmeister <robert.burmeister@utoledo.edu> To: freebsd-gnome@freebsd.org Subject: Re: FreeBSD Port: devel/glib20 Message-ID: <1392658042024-5886734.post@n5.nabble.com> In-Reply-To: <CAN6yY1ttGAovcJwA3udUU0X8v-WYWR-vj_k8Y2_tJXAivOTcGw@mail.gmail.com> References: <53012DEB.9020208@UToledo.edu> <CAN6yY1ttGAovcJwA3udUU0X8v-WYWR-vj_k8Y2_tJXAivOTcGw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Kevin Oberman-4 wrote >> Was the 16 Feb 2014 change to glib20 2.36.3_2 to now require >> converters/libiconv on FreeBSD 10 deliberate? >> > "Add back depend on libiconv. This is needed because our base iconv > doesn't > do utf-8 -> wchar_t apparently. [2] wchar_t is used by glibmm." > > So it was clearly deliberate. I am a bit surprised as I have had no issues > with glib20 and no iconv. I also have glibmm and no iconv. But I use > en.US.UTF-8, so I may not hit the relevant code path. But I was certainly > able to build both without having iconv installed from ports. I have not had any problems either with glib20 nor glibmm without libiconv installed. It would make sense that problems only show up when using double wide encodings. Perhaps whether to use base iconv or converters/libiconv should have a configuration option. Converting my whole system back to libiconv is no small task. -- View this message in context: http://freebsd.1045724.n5.nabble.com/FreeBSD-Port-devel-glib20-tp5886489p5886734.html Sent from the freebsd-gnome mailing list archive at Nabble.com.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1392658042024-5886734.post>