On Sat, Sep 22, 2001 at 06:36:18PM +0200, Meino Christian Cramer wrote:
> as I reported before, gimp and gimp-print use different versions of
> the libtool. The result is, that the generated plugin crashes, if
> gimp tries to load it.
Why does it crash? Do you get a segfault? Could you try attaching
a debugger and printing a backtrace so we can see what is wrong.
Which libraries does 'ldd' show the print plugin being linked with.
> GIMP: Libtool 3.5
> GIMP-PRINT: Libtool 3.4
> newest version of libtool: 4.2
> How can I avoid this trouble ?
Why is libtool the problem? I'm not an expert on the internals of
libtool, but I can't see why it matters if packages use different
versions. libtool is just a script for portable library creation.
If the problem is that you are trying to build gimp-print within
the gimp source tree, then there may be problems with one version
of libtool using the libfoo.la files created by another, but this
should not happen because if you are putting gimp-print into the
gimp tree, you should have used 'make gimp-dist' to make a tarball
suitable for inclusion into the gimp tree, which *does not*
include libtool, gettext, automake or autoconf generated files or
anything else apart from the bare essentials. You have to
regenerate them yourself.
I can't really address the problem unless you provide us with some
more information though.
Roger Leigh ** Registration Number: 151826, http://counter.li.org **
Need Epson Stylus Utilities? http://gimp-print.sourceforge.net/
For GPG Public Key: finger [EMAIL PROTECTED] or see public keyservers.
Gimp-developer mailing list