On 8/28/06, Mikolaj Kucharski <[EMAIL PROTECTED]> wrote:
On Mon, Aug 28, 2006 at 04:17:51AM +0100, Mikolaj Kucharski wrote:
> On Mon, Aug 28, 2006 at 03:15:47AM +0100, Mikolaj Kucharski wrote:
> > On Fri, Aug 11, 2006 at 04:20:12PM +0200, Adriaan Misc wrote:
> > > Under Gnome gimp dumps core on saving an image.
> > >
> > > --------error message --------
> > > gimp:/usr/local/lib/libgthread-2.0.so.1000.3: undefined symbol
> > > 'pthread_mutex_trylock'
> > > lazy binding failed!
> > >
> > > (script-fu:16248): LibGimpBase-WARNING **: script-fu: wire_read(): error
> > >
> > > [1] + Segmentation fault gimp (core dumped)
> > > -------- end of error message ----------
> >
> > I can confirm that I have the same behaviour.
>
> After I applayed attached patch to gtk+2 port I don't have undefined
> symbol errors from
>
> /usr/local/bin/gdk-pixbuf-query-loaders
>
> between gtk+2 @exec's. This however doesn't resolve problem with gimp. I
> just want to ask am I going in good direction with resolution for this
> problem? Should I recompile gimp with -pthread like gtk+2?
>
> Problem is related to gnome-vfs2. I think gtk+2 is trying to load
>
> /usr/local/lib/gtk-2.0/2.4.0/filesystems/libgnome-vfs.so
>
> which uses -pthread and gimp doesn't. So add -pthrad to LDFLAGS and
> CPPFLAGS like in gtk+2?
When I recompiled gimp with attached patch (similar to gtk+2) problem
with undefined symbol and segmentation fault disapears. Any comments,
please?
gtk+2 and gimp compiled ok with your patches on a fresh installed
2006-8-28 snapshot system using the ports.tar.gz of the same date. The
box is now compiling gnome and that will take a while ;)
=Adriaan=
