From: Josh Durgin <josh.durgin@inktank.com>
To: Noah Watkins <noah.watkins@inktank.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>,
Gregory Farnum <greg@inktank.com>,
Gregory Farnum <gregory.farnum@inktank.com>
Subject: Re: feedback on supporting libc++
Date: Mon, 30 Dec 2013 17:19:20 -0800 [thread overview]
Message-ID: <52C21B98.40109@inktank.com> (raw)
In-Reply-To: <CA+Hcz5_pOdrHyYq9xbn=09S6jFh9enRWq1uKxHSQKS3u2qiXQw@mail.gmail.com>
On 12/27/2013 03:34 PM, Noah Watkins wrote:
> On Wed, Oct 30, 2013 at 2:02 PM, Josh Durgin <josh.durgin@inktank.com> wrote:
>> On 10/29/2013 03:51 PM, Noah Watkins wrote:
>>
>> unsafe to me. Could you check whether you can run 'rados ls' compiled
>> against an old librados, but dynamically loading librados from this
>> branch compiled in c++98 mode?
>
> I'm still working on this, but my understanding so far from libc++
> documentation is that libc++ and libstdc++ are API but not ABI
> compatible, so there shouldn't be an expectation that librados binary
> library built against libstc++ will work if dynamically linked against
> libc++.
I meant if it was compiled against libstdc++ both times, I was curious
whether changing std::tr1::shared_ptr to ceph::shared_ptr would result
in any incompatibility.
I just tried this, and it worked fine (I think because it does not
actually create a new c++ type, but acts like a typedef and just
creates an alias), so I've got no issues with this approach.
Josh
next prev parent reply other threads:[~2013-12-31 1:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-29 22:51 feedback on supporting libc++ Noah Watkins
2013-10-30 16:13 ` asomers
2013-10-30 19:02 ` Josh Durgin
2013-12-27 23:34 ` Noah Watkins
2013-12-31 1:19 ` Josh Durgin [this message]
2013-12-31 16:59 ` Noah Watkins
2013-12-31 18:59 ` Josh Durgin
2014-01-09 19:54 ` Noah Watkins
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52C21B98.40109@inktank.com \
--to=josh.durgin@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=greg@inktank.com \
--cc=gregory.farnum@inktank.com \
--cc=noah.watkins@inktank.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.