Firebird linked against libc_r and libpthread?

[Wesley Morgan]

On Sun, 8 Feb 2004, Joe Marcus Clarke wrote:

> On Sun, 2004-02-08 at 18:06, Wesley Morgan wrote:
> > On Sun, 8 Feb 2004, Joe Marcus Clarke wrote:
> >
> > > > > I just rebuild firebird on a recent -current, and it seems this port is
> > > > > suffering from the pthread changes, because it is linked to both libc_r
> > > > > and libpthread. It seems to run though, but not as stable as 0.6 was
> > > > > doing.
> > > >
> > > > I'm having some trouble with libtool wanting to use libc_r with several
> > > > ports, such as like g-wrap.
> > >
> > > Please be more specific.  What are the messages?
> >
> > There don't seem to be any specific messages, but the "libgw-gtk.lai" file
> > generated by libtool always has libc_r as a dependency. If I completely
> > remove libc_r, it still tries to link with it. No manual editing seems to
> > fix it, so it is pretty clear (from what I know, anyway) that libtool
> > itself is making the decision.
>
> I doubt this is really coming from g-wrap.  Take a look at
> /usr/local/bin/*-config and /usr/X11R6/*-config, and search for -lc_r.
> I have a feeling it's coming from glib or gtk+.

Hrm. Actually it seems to have either been coming from guile or slib. I
had already rebuilt those, too. Joy :) All these micropackages is the
biggest reason I use KDE over GNOME.

-- 
Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!