[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: possible freetype transition; improved library handling needed for all C/C++ packages

Steve Langasek wrote:
> * Use Debian's libtool.

I took one affected package (kmldonkey) from your list, relibtoolized
it as described, and rebuilt it, which failed spectacularly.  Then, I
took another one (rekall), relibtoolized it, rebuilt it, and that
failed with a strikingly similar pattern.

kmldonkey links with the following libraries: -lkdeui -lkio.  As shipped,
libtool expands that to every library under the sun.  The new libtool
indeed reduces this to /usr/lib/libkdeui.so /usr/lib/libkio.so and a few
system libraries/objects, which is then greeted by ld with hundreds of
error messages of the kind:

/usr/share/qt3/include/qstring.h:847: undefined reference to `QString::shared_null'
/usr/share/qt3/include/qstring.h:848: undefined reference to `QStringData::deleteSelf()'

Both libkdeui and libkio reference (as shown by ldd) libqt-mt (which
I suppose is where these symbols should be).

The error messages in the rekall build are of the sort

.../rekall-2.2.3-2/db/mysql/kb_mysql.cpp:595: undefined reference to `i18n(char const*)'

In this case -lqt-mt is actually on the libtool command line.

So what is wrong here?  Have other maintainers of Qt/KDE-related packages
perhaps experienced this?

Please send copies of list mail to me.

Reply to: