Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 20 Sep 2003 18:20:21 +0300
From:      Andy Fawcett <andy@athame.co.uk>
To:        deischen@freebsd.org, Daniel Eischen <eischen@vigrid.com>
Cc:        Arjan van Leeuwen <avleeuwen@piwebs.com>
Subject:   Re: [kde-freebsd] Compiling arts in -CURRENT without -pthread
Message-ID:  <200309201820.21929.andy@athame.co.uk>
In-Reply-To: <Pine.GSO.4.10.10309201114190.19094-100000@pcnet5.pcnet.com>
References:  <Pine.GSO.4.10.10309201114190.19094-100000@pcnet5.pcnet.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Saturday 20 September 2003 18:17, Daniel Eischen wrote:
> On Sat, 20 Sep 2003, Andy Fawcett wrote:
> > On Saturday 20 September 2003 17:53, Daniel Eischen wrote:
> > > On Sat, 20 Sep 2003, Arjan van Leeuwen wrote:
> > > > On Saturday 20 September 2003 12:56, Arjan van Leeuwen wrote:
> > > > > Hi,
> > > > >
> > > > > I'm trying to compile arts (audio/arts) in -CURRENT. I
> > > > > replaced -lpthread with ${PTHREAD_LIBS} in the ports'
> > > > > configure script. This makes it recognize -lc_r correctly,
> > > > > and it also uses that when building the port.
> > > > >
> > > > > However, after some time, the port will fail with these error
> > > > > messages:
> > > >
> > > > (...)
> > > >
> > > > > How can all these pthread_* functions be undefined when it is
> > > > > linking against -lc_r?
> > > >
> > > > I just discovered that it works without any errors when using
> > > > -lkse instead of -lc_r. Aren't these two libraries supposed to
> > > > be compatible?
> > >
> > > Yes, that's really strange.  Are you sure that you have a correct
> > > libc_r in /usr/lib?  You seem to be building arts in the correct
> > > manner, and -lc_r _should_ work.
> >
> > I've also seen the identical effect, FWIW, when I started making
> > the post-pthread changes. Unfortunately I ran out of time to check
> > further.
> >
> > I don't do anything special with the world build, so I don't know
> > what the problem is.
>
> I think the problem might be with libstool^Wlibtool.  Take a
> look at the libtool that the build is using (from my experience
> some of these ports use the system's installed libtool, others
> use their own libtool).  See if it handles -lc_r specially.

KDE uses its own version. I know this from several years of KDE 
experience.

A.

-- 
Andy Fawcett                                     | andy@athame.co.uk
                                                 | tap@kde.org
"In an open world without walls and fences,      | tap@lspace.org
  we wouldn't need Windows and Gates."  -- anon  | tap@fruitsalad.org



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200309201820.21929.andy>