Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 10 Apr 2004 19:29:29 -0400 (EDT)
From:      Daniel Eischen <eischen@vigrid.com>
To:        Matthias Schuendehuette <msch@snafu.de>
Cc:        Tim Robbins <tjr@freebsd.org>
Subject:   Re: libpthread?
Message-ID:  <Pine.GSO.4.10.10404101927520.238-100000@pcnet5.pcnet.com>
In-Reply-To: <200404102335.18433.msch@snafu.de>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 10 Apr 2004, Matthias Schuendehuette wrote:

> Hi Dan, Hi you others,
> 
> On Saturday 10 April 2004 17:10, Daniel Eischen wrote:
> > On Sat, 10 Apr 2004, Tim Robbins wrote:
> >
> > You don't need to rebuild any ports if you globally
> > map libc_r to libpthread with /etc/libmap.conf.  Over
> > time, when all your ports are upgraded at your leisure,
> > references to libc_r will be removed.  Of course,
> > portupgrade -af would do the trick much quicker...
> 
> Yeah, that was the key-paragraph! I read this already in UPGRADING but 
> obviously didn't understand it fully...
> 
> 'portupgrade -af' is not an option here because of my ISDN-Line (64 
> kbit/s). I'm perhaps one of the last users of hm's 'i4b'-package... :-)
> 
> > > The golden rule is: don't mix threading libraries within a program.
> > > If a program is linked to libc_r, so must all the other
> > > thread-aware libraries it links to be. The same goes for
> > > libpthread.
> >
> > If you are coming from 5.2.1-RELEASE and before, and trying
> > to upgrade to -release, the default threading library changed
                  ^^^^^^^^
You figured it out, but for anyone else confused, I meant -current.

-- 
Dan Eischen



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.10.10404101927520.238-100000>