7 Dec
2011
7 Dec
'11
5:50 a.m.
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.
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
Searching my build environment for generic_profile, Downscale and Upscale in /usr/lib,
/usr/include, /opt/trinity/lib, and /opt/trinity/include revealed nothing. However,
searching on my normal system I finally found those declarations:
ImageMagick/magick/deprecate.h:#define Downscale(quantum)
ImageMagick/magick/deprecate.h:#define Upscale(value)
ImageMagick/magick/image.h: generic_profile
The kis_image_magick_converter.cc errors were caused because I had installed
GraphicsMagick and removed ImageMagick. I should be able to eliminate the latter set of
errors by reinstalling ImageMagick.
That leaves me focused on the first set of errors.
Using readelf, the only file that surfaced with all of these undefined references is
/usr/lib/libMagickWand.so.3.0.0. That file is from the ImageMagick package.
There are two sym links to that file:
libMagickWand.so
libMagickWand.so.3
I reinstalled ImageMagick in my build system. Back to square one, so to speak, because
that is where the story began. As I mentioned, with ImageMagick installed I always get the
"undefined references" set of errors.
I already had the following in my configure options:
--with-extra-libs=/usr/lib
The /usr/include directory is already part of the $CPLUS_INCLUDE_PATH variable. I added
the following to my configure options:
--with-extra-includes=/usr/include/ImageMagick
--with-extra-includes=/usr/include/ImageMagick/magic
The build again failed. (I'm a student here. Trial and error is part of my learning
curve. :) )
Next I tried amending export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib.
The build again failed.
Okay, next I try amending the Makefile.am. As the errors are related to ImageMagick, I
amended that make file.
NOpe, failed to build. Same errors.
So --- why is nobody else reporting this build problem? I suspect many TDE developers are
not because koffice never was that popular. Of those who do build, why are they not having
this same build problem? Is this related to the version of ImageMagick? Possibly others
are building without either ImageMagick or GraphicsMagick, but when I try that most of the
apps don't build.
I would like to get to the bottom of this because I always have had trouble building
koffice.
Darrell