Firebird linked against libc_r and libpthread?

[Daniel Eischen]

On Sun, 8 Feb 2004, Wesley Morgan wrote:

> On Sun, 8 Feb 2004, Mark Huizer wrote:
> 
> > On Sun, Feb 08, 2004 at 11:37:12AM -0800, Joe Marcus Clarke wrote:
> > > marcus      2004/02/08 11:37:12 PST
> > >
> > >   * Clean up the pkg-message a bit to reflect reality with respect to Perl
> > >
> > >   Thanks to casaveli on BSDForums for finding it was esound causing the lock up
> > >   as well as testing the patch mentioned above.
> >
> > 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.

Yeah, I've seem several slightly different versions of libfool and I
recall them sometimes knowing about libc_r.

<rant>
Why do some ports include their own libfool?
<\rant>

-- 
Dan Eischen