On Oct 3, 2008, at 4:28 PM, Daniel Macks wrote: > On Fri, Oct 03, 2008 at 10:02:40PM +0200, Martin Costabel wrote: >> Alexander Hansen wrote: >> [] >>> c++ -prebind -dynamiclib -single_module -compatibility_version 4.4 - >>> current_version 4.4.1 -install_name /sw/lib/qt4-x11/lib/libQtCore. >>> 4.dylib -o libQtCore.4.4.1.dylib .obj/release-shared/qfuture.o .obj/ >> [] >>> moc_qtextcodecplugin.o -L/sw/lib/freetype219/lib -L/sw/lib/ >>> fontconfig2/lib -L/sw/lib -L/usr/X11R6/lib -L/sw/src/fink.build/qt4- >>> x11-4.4.1-1/qt-copy/lib -lz -lm -L/sw/lib -lgthread-2.0 -lglib-2.0 - >>> lintl >>> Undefined symbols: >>> "_libiconv", referenced from: >> >> It is clear that there is a "-liconv" missing on the linker line. I >> traced this back to /sw/lib/pkgconfig/glib-2.0.pc from glib2-dev, >> which >> in version 2.18.1-102 no longer contains -liconv, whereas version >> 2.14.6-103 from a few weeks ago still contained -liconv. >> >> This looks like a bug in glib2-dev, because /sw/lib/ >> libglib-2.0.0.dylib >> is linked with libiconv, so `pkg-config --libs glib-2.0` should >> provide >> -liconv, but it doesn't. > > Looking at more of the error message: > > Undefined symbols: > "_libiconv", referenced from: > QIconvCodec::convertFromUnicode(QChar const*, int, > QTextCodec::ConverterState*) constin qiconvcodec.o > QIconvCodec::convertToUnicode(char const*, int, > QTextCodec::ConverterState*) constin qiconvcodec.o > > it is something in qt4-x11 itself that wants libiconv not just "want > it because use glib2 and glib2 is what actually wants it", so it's up > to qt4-x11 to pass that linker flag itself. Until now, it just got > lucky that glib2 was sloppy and published all the libs it used, even > the ones that were only internal-implementation details. Now glib2 > finally stopped forcing inherited builddepends for libs that aren't > part of its public interface. > > pkg-config was also updated recently which itself handles inherited > dependency flags poorly on OS X (though I thought it hadn't changed > anything about it in new version). Could you do some differential > diagnosis by upgrading/downgrading and see if it's really new-glib2 or > if it's new pkg-config (or only the combination) that causes the > problem? > > dan > > -- > Daniel Macks > [EMAIL PROTECTED] > http://www.netspace.org/~dmacks > >
I tried the new pkgconfig with the old glib2 and qt4-x11 build successfully. I didn't do the new glib2 with the old pkgconfig because the new glib2 has a versioned dependency on pkgconfig. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Fink-users mailing list Fink-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-users
