trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: December 2011

Re: [trinity-devel] KOffice 3.5.13 FTBFS

From: Darrell Anderson <humanreadable@...>
Date: Thu, 8 Dec 2011 09:17:53 -0800 (PST)
> > Something changed between 6.5.3-3 and 6.5.9-6.
> Something in 6.5.9-6
> > does not build correctly.
> The library seems to have a missing NEEDED for the library
> which
> provides the functions (which appears to be
> libMagickWand.so).
> You can read the dynamic library part of an ELF library by
> the command
> $ readelf -d <library>.so
> > 
> > Any ideas what? Something in the config options?
> Compiler flags? My
> > searching the web revealed nothing.

> I have no 'undefined reference' error with Slackware64
> 13.37 and its
> provided ImageMagick 6.6.6_10. But strangely
> libMagickCore.so doesn't
> specify libMagickWand.so in it's NEEDED list (not even in
> the ldd
> result); seems that the 6.6.6_10 libMagickCore.so doesn't
> use
> libMagickWand.so at all.

Last night I stumbled across a possible solution.

As I mentioned, in my 13.1 build environment I rebuilt 6.5.3-3, which came with 13.0. After rebuilding there were no undefined reference errors with libMagickCore.so. After I posted my sentiment that something had changed between that version and 6.5.9-6, I started fiddling. I changed the 6.5.9-6 build script from --without-modules to --with-modules=yes. Merely deleting the --without-modules option did not work.

Lo and behold the undefined reference errors disappeared.

Perhaps between 6.5.3-3 and 6.6.6_10 there was a glitch in the way the package built to cause such errors. That you don't seem the errors with a newer version could indicate the developers fixed the problem. Just speculating, of course.

Today I plan to try again building koffice with the rebuilt ImageMagick package.

Possibly then this one build option in ImageMagick could explain why nobody else who built koffice has seen those errors. Perhaps in their distro ImageMagick is built differently.

By the way, when building ImageMagick for other people, be sure to build in a non Nvidia environment because the ImageMagick sources automatically build internal dependencies on OpenCL. I could not find any configure option to prevent that.

From where do you find this NEEDED list?

Darrell