7 Dec
2011
7 Dec
'11
2:08 a.m.
Le Tue, 6 Dec 2011 12:06:16 -0600,
"Timothy Pearson" <kb9vqf(a)pearsoncomputing.net> a écrit :
My first attempt would be to see which shared library
all those
symbols ended up in. Sometimes (it depends on the processing power
of your computer) you can do a simple text-based search in your
library directory for e.g. DrawSetFillPatternURL to figure out which
library it is.
grep isn't needed, you can do something like
$ readelf --symbols --wide /opt/kde3/lib64/libkdecore.so
and it's more efficient as readelf reads only the needed parts of the
library binary.
If the library is a C++ one (like most KDE4 and Trinity ones) you can
get the meaningful function names by using c++filt (it's in binutils):
$ readelf --symbols --wide /opt/kde3/lib64/libkdecore.so | c++filt
Once you know the library name, try appending it as a linker flag to
the koffice/filters/chalk/gmagick/Makefile.am LDFLAGS string; e.g if
you found libfoo.so.1.0.0 contains the symbol then you would append
-lfoo
Tim
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-devel-unsubscribe(a)lists.pearsoncomputing.net For additional
commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net Read
list messsages on the Web archive:
http://trinity-devel.pearsoncomputing.net/ Please remember not to
top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting