From: Roger Leigh <roger@xxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: [Gimp-print-devel] Probelms as usual...
Date: Sun, 23 Sep 2001 01:58:14 +0100
Message-ID: <20010923015814.A583@xxxxxxxxxxxxxxxxxxxxxx>
>
> Why does it crash?
> Do you get a segfault?
Yes.
> Could you try attaching
> a debugger and printing a backtrace so we can see what is wrong.
Yes, I can. Last time (with gimp-print-4.1.99-a2), when I had exactly this
problem, it was traced down to what I have described: different libtool
versions.
> Which libraries does 'ldd' show the print plugin being linked with.
...wait a "moment"...I have to recompile the whole stuff again, cause
I went back to gimp-print 4.05....I _need_ a running gimp with
printing capabillities...
Now...this is the output (same as last time I tried the *a2-version....)
after clicking File->Print
/usr/lib/gimp/1.2/plug-ins/print: fatal error: Segmentation fault
/usr/lib/gimp/1.2/plug-ins/print (pid:5913): [E]xit, [H]alt, show [S]tack trace or [P]roceed: S
#0 0x4020e5d8 in g_on_error_stack_trace () from /usr/lib/libglib-1.2.so.0
#1 0x40227014 in __DTOR_END__ () from /usr/lib/libglib-1.2.so.0
#2 0x62696c2f in ?? ()
ldd print gives me
libgimpui-1.2.so.2 => /usr/lib/libgimpui-1.2.so.2 (0x40021000)
libgimp-1.2.so.2 => /usr/lib/libgimp-1.2.so.2 (0x40049000)
libgtk-1.2.so.0 => /usr/lib/libgtk-1.2.so.0 (0x4006a000)
libgdk-1.2.so.0 => /usr/lib/libgdk-1.2.so.0 (0x401bd000)
libgmodule-1.2.so.0 => /usr/lib/libgmodule-1.2.so.0 (0x401fd000)
libglib-1.2.so.0 => /usr/lib/libglib-1.2.so.0 (0x40201000)
libdl.so.2 => /lib/libdl.so.2 (0x40228000)
libXext.so.6 => /usr/X11/lib/libXext.so.6 (0x4022c000)
libX11.so.6 => /usr/X11/lib/libX11.so.6 (0x4023a000)
libm.so.6 => /lib/libm.so.6 (0x4031a000)
libgimpprint.so.1 => /usr/lib/libgimpprint.so.1 (0x40341000)
libc.so.6 => /lib/libc.so.6 (0x403ea000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
> > 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?
Because the reason -- as it was the same last time -- wasn't removed.
> 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.
Me too...I only repeating the answeres I got last time...
> If the problem is that you are trying to build gimp-print within
> the gimp source tree,
...no...seperate build...
> 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.
See above...hope it helps.
> Roger
>
