Re: nss_ldap broken

From: Daniel Eischen (eischen_at_vigrid.com)
Date: 03/31/04

  • Next message: Lewis Thompson: "Re: Last NSS commit is very dangerous"
    Date: Wed, 31 Mar 2004 16:48:02 -0500 (EST)
    To: "Jacques A. Vidrine" <nectar@FreeBSD.org>
    
    

    On Mon, 29 Mar 2004, Daniel Eischen wrote:

    > On Mon, 29 Mar 2004, Jacques A. Vidrine wrote:
    >
    > > Sean, could you report how this patch works for you? Hmm, actually, it
    > > looks almost identical to what you posted :-) Is there a reason that
    > > you stored the value of `__isthreaded' in a local variable? Did that
    > > make a difference for your case?
    >
    > I'm unsure how nss_ldap was built to depend on libpthread (or
    > any threads library). I built it from ports and 'ldd' didn't
    > report any dependency on a threads library.

    I rebuilt it and now it does depend on libpthread. I
    think it is because I had openldap-client-2.1.26 which
    didn't have a dependency on libpthread, but upgrading
    to openldap-client-2.1.28 brought in the dependency.

    Too bad these shared libraries can't be made to use
    the libgcc trick, so they can still be thread-safe
    but not depend on a threads library. That would
    also make it easier to use different thread libraries
    for different applications relying on common shared
    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: Lewis Thompson: "Re: Last NSS commit is very dangerous"

    Relevant Pages

    • Re: Fixing -pthreads (Re: ports and -current)
      ... multiple platforms knows that most thread libraries are ... called libpthread and are linked to with -lpthread. ... > compile a third-party app in FreeBSD is via the ports system, ... will be on the link command and it should be very obvious ...
      (freebsd-current)
    • RE: Fixing -pthreads (Re: ports and -current)
      ... > multiple platforms knows that most thread libraries are ... > called libpthread and are linked to with -lpthread. ... produce an error) but fails to compile and link pthreads code when that flag ... special case every platform. ...
      (freebsd-current)
    • Re: libpthread?
      ... > link to libraries that link to thread libraries. ... > else I've tried - works perfectly with libpthread. ... You don't need to rebuild any ports if you globally ...
      (freebsd-current)
    • Re: HEADS UP: libkse -> libpthread switch
      ... > For the ports team, it is recommended that you don't install a ... > thread libraries. ... > libpthread isn't found. ... vincent% make -V PTHREAD_LIBS ...
      (freebsd-current)
    • Re: HEADS UP: libkse -> libpthread switch
      ... > For the ports team, it is recommended that you don't install a ... > thread libraries. ... > libpthread isn't found. ... vincent% make -V PTHREAD_LIBS ...
      (freebsd-current)