Re: Threading/KSE problem

From: Daniel Eischen (deischen_at_freebsd.org)
Date: 09/20/05

  • Next message: Kris Kennaway: "Re: Threading/KSE problem"
    Date: Tue, 20 Sep 2005 14:55:50 -0400 (EDT)
    To: Scott Long <scottl@samsco.org>
    
    

    On Tue, 20 Sep 2005, Scott Long wrote:

    > Daniel Eischen wrote:
    > >
    > > Sure, symbol versioning would be great to have, but I still don't
    > > know why library versions are bumped when they don't need to be.
    > > It's like we've thrown up our hands and said "Something has changed
    > > in one or more of the libraries, and we don't know how this affects
    > > other libraries, so we're going to bump them all." Speaking for
    > > the thread libraries, they were not users of any of the changed
    > > ABIs -- there was no reason to bump them.
    > >
    >
    > We have a very strong history of making changes in our base libraries
    > that have very unintended consequences.

    And as far as I can recall, we have ironed them all out in -current
    before any release.

    > Try running the Java binaries
    > for 4.x, the only ones that we are certified to distribute, on 5.x or
    > 6.x.

    Why? Do they not work with the compat libraries installed?

    > I put this problem forward a year ago and asked for help on solving it.
    > It's not like I woke up one morning and decided to screw around with
    > the libraries for the hell of it.

    I don't think anyone thinks that. But I prefer the old way. If we're
    not properly keeping track of our ABI changes and what they affect,
    then let's work on that problem. Symbol versioning isn't going to
    solve that for us anyways.

    -- 
    DE
    _______________________________________________
    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: Kris Kennaway: "Re: Threading/KSE problem"

    Relevant Pages

    • Re: [jakub@redhat.com:Linking against libpthread via -pthread?
      ... Dan Nelson wrote: ... and a third is linked to libpthread. ... I think symbol versioning only helps if you want to provide multiple ... It won't help two libraries that both want to ...
      (freebsd-current)
    • Re: [jakub@redhat.com:Linking against libpthread via -pthread?
      ... a "ldd libgomp.so.1" shows no dependence ... executable links to three shlibs, one library is linked to libc_r, ... I think symbol versioning only helps if you want to provide multiple ... It won't help two libraries that both want to provide the ...
      (freebsd-current)
    • Re: libpthread shared library version number
      ... the line of what we have for other system libraries. ... We certainly should be bumping them ... would have to bump them again before a release, ... we should enable symbol versioning at ...
      (freebsd-current)
    • Re: Shared library version bump?
      ... :>> In preparation for release of 7.0, ... Hopefully this will be the last major bump for a long time... ... why bother with symbol versioning at all... ... If other libraries become symbol versioned after 7.0 gets ...
      (freebsd-current)
    • Re: pthread_cond_t changes
      ... > libraries from 2.4.26 failed. ... The best chance of getting a answer is to ask at the glibc mailing list. ... Symbol versioning for the most part. ... Old binaries are linked to a particular symbol/version and will ...
      (comp.os.linux.development.apps)