Re: HEADS UP: libkse -> libpthread switch

From: Daniel Eischen (eischen_at_vigrid.com)
Date: 01/30/04

  • Next message: Jun Su: "Re: Call for testers: New PID allocator patch for -CURRENT" 
    Date: Fri, 30 Jan 2004 09:38:32 -0500 (EST)
To: "Jacques A. Vidrine" <nectar@FreeBSD.org>

    On Fri, 30 Jan 2004, Jacques A. Vidrine wrote:

    > On Fri, Jan 30, 2004 at 07:34:02AM -0500, Daniel Eischen wrote:
    > > Until
    > > the ports system is updated to handle this change, it is
    > > recommended that folks install an /etc/libmap.conf(5) that
    > > maps libc_r to libpthread.
    >
    > Why, exactly? (curious)
    >
    > IMHO it is unacceptable to require /etc/libmap.conf to exist. I know
    > this is temporary, but I hope it is *really* temporary.

    When you start [re]building ports now, they may pick up libpthread
    instead of PTHREAD_LIBS (currently -lc_r). Then you may have
    things linked to both libc_r and libpthread, or new applications
    may depend on libraries that were linked to libc_r. You can't
    depend on more than one threads library.

    I suspect it's going to be a mess for a while, but use of
    an appropriate libmap.conf should make things usable again.
    After ports catches up to these changes and you rebuild all
    your ports with the new threads library, then you'll no
    longer need the libmap.conf. Unless you have nvidia provided
    drivers/libraries. 

    -- 
Dan Eischen
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
  • Next message: Jun Su: "Re: Call for testers: New PID allocator patch for -CURRENT"

    Relevant Pages

    • Re: Fixing -pthreads (Re: ports and -current)
      ... people fix them. ... I don't have the time to fix broken ports ... transition to libpthread is making ports PTHREAD_LIBS compliant. ... has been over 2 years since, yada yada yada, and the ports ...
      (freebsd-current)
    • Re: wxgtk build error libpthred related
      ... On Wed, 2004-02-04 at 18:51, Alex Dupre wrote: ... libc_r and libpthread linked into it. ... all ports that depend on gtk12. ...
      (freebsd-current)
    • Re: Fatal error Spinlock called when not threaded. ... (Re:FreeBSD 5.3-BETA6 available)
      ... This affects your ports, not the base system. ... Unless you rebuild all your ports from ... The problem is mostly due to shared libraries being linked to ... on such a shared library will link the application to libpthread, ...
      (freebsd-current)
    • Re: library problems with -CURRENT
      ... >It's not in UPDATING, but a change was recently made (can't say exactly ... This was introduced by libpthread ... This affects all ports which are still using libc.5 and libpthread/libkse. ... The easiest approach is probably to rebuild all your ports so that they ...
      (freebsd-current)
    • Re: library problems with -CURRENT
      ... >>You'll have to recompile these ports, I suspect. ... > This was introduced by libpthread ... > functions implemented and is no longer rebuild as we're using libc.6 ...
      (freebsd-current)