Revision 12844 added a patch to glib2 that moves glib-2.0.pc's -liconv from Libs.private to Libs. The change causes a problem with applications that may not expect the requirement for libiconv (there is no reason that they should, see https://bugzilla.gnome.org/show_bug.cgi?id=534319#c2). Specifically, the patched glib-2.0.pc causes an application to build with -liconv. But, libiconv installs in a non-standard location, /usr/lib/libiconv/lib/, and the build process can not find it without -L... Glib-2.0.pc does not provide -L...
This can be fixed by making the application aware of libiconv using iconv.m4, but this defeats the purpose of glib-2.0.pc. Namely, using pkg-config should ensure an application builds against glib2 and all of its dependencies. When I remove the patch from glib2, my application fails to build due to missing iconv symbols. On one hand, this is expected. But, on the other, it makes me wonder what the purpose of Libs.private is. Does anyone know what is going on? -- Mike :wq _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
