GitHub user jpeach opened a pull request:

    https://github.com/apache/trafficserver/pull/720

    TS-4560: Fix C++ API shared_ptr detection.

    Since ink_autoconf.h is not installed, we can't use it to figure
    out which shared_ptr implementation to use. Further, Traffic Server
    might not have been built with the same toolchain that 3rd party
    plugins are using.
    
    Since shared_ptr is used in the C++ API headers, both Traffic Server
    and the plugins need to agree on which implementation to use. The
    best (but not perfect) solution is to hardcode it into the header
    file during the Traffic Server build. This means that both parties
    are consistent and any remaining problems could be attributed to
    C++ standard library compatibility.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jpeach/trafficserver fix/4560

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/trafficserver/pull/720.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #720
    
----
commit b9c29f62db44573e390a203123c864f71fdf935f
Author: James Peach <jpe...@apache.org>
Date:   2016-06-16T23:51:40Z

    TS-4560: Fix C++ API shared_ptr detection.
    
    Since ink_autoconf.h is not installed, we can't use it to figure
    out which shared_ptr implementation to use. Further, Traffic Server
    might not have been built with the same toolchain that 3rd party
    plugins are using.
    
    Since shared_ptr is used in the C++ API headers, both Traffic Server
    and the plugins need to agree on which implementation to use. The
    best (but not perfect) solution is to hardcode it into the header
    file during the Traffic Server build. This means that both parties
    are consistent and any remaining problems could be attributed to
    C++ standard library compatibility.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to