Re: libpthread version bump

From: Warner Losh (imp_at_bsdimp.com)
Date: 04/22/05

  • Next message: Warner Losh: "Re: libpthread version bump" 
    Date: Fri, 22 Apr 2005 13:14:08 -0600 (MDT)
To: deischen@freebsd.org

    > > The recent changes to implement the the %fs/%gs manipulation syscalls has
    > > created a problem for 5.x compatibility. While libc has been bumped for
    > > 6.x already, libpthread hasn't, so running 5.x apps on -CURRENT ends up
    > > with the app pulling in the old libc correctly, but it pulls in the
    > > current libpthread which depends on the new libc and the linker errors out
    > > on the missing symbols.
    > >
    > > I think we need to bump libpthread's version to allow for compatibility in
    > > 6. Then we can ship the old libpthread along with the old libc and the
    > > Right Thing happens.
    >
    > I wish someone would work on getting symbol versioning working
    > so we don't have to keep bumping library versions for things
    > like this :-)

    Symbol versioning wouldn't help this case...

    Warner
    _______________________________________________
    freebsd-arch@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-arch
    To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org"

  • Next message: Warner Losh: "Re: libpthread version bump"

    Relevant Pages

    • Re: Looks like threading is b0rken on FreeBSD/powerpc
      ... I think you might want to try point libpthread at libthr with ... for libpthread. ... when checking the errno set after calling accessto check if a file ... there is a plan to bump libthr version when symbol versioning ...
      (freebsd-current)
    • Re: New malloc breaks old libpthread
      ... >>>and this it the usual case calling for the bump. ... I'm no expert at this (I think kan originated pthread.map for libpthread), ... Our libc currently doesn't have symbol versioning information, ...
      (freebsd-current)