On 10/8/20 9:30 AM, Konrad, Martin via Core-talk wrote:
> Hi Ralph,
>> ITER needed to switch EPICS Base to use "-std=c++11" because without
>> that setting, linking EPICS libraries would not work for other code that
>> was compiled using C++11.
> Weird. I tried to reproduce this by building pvxs (which builds using
> -std=c++11) on CentOS 7 against EPICS 7 (built without -std=c++11).
> Works fine for me.
>
> Are you linking against any libraries provided by a vendor as binaries?
> Is there a way we can reproduce the problem?
@Ralph Ah, I had forgotten about this...
@Martin This isn't a question of libstdc++, but rather of how/where
pvDataCPP gets 'shared_ptr<T>'.
https://github.com/epics-base/pvDataCPP/blob/320cc3c60b575fa49e49a21619472f01b8890049/src/misc/pv/sharedPtr.h#L62-L86
- Replies:
- Re: ABI compatibility with different C++ standard versions Michael Davidsaver via Core-talk
- References:
- ABI compatibility with different C++ standard versions Konrad, Martin via Core-talk
- Re: ABI compatibility with different C++ standard versions Ralph Lange via Core-talk
- Re: ABI compatibility with different C++ standard versions Konrad, Martin via Core-talk
- Navigate by Date:
- Prev:
Re: ABI compatibility with different C++ standard versions Konrad, Martin via Core-talk
- Next:
Re: ABI compatibility with different C++ standard versions Michael Davidsaver via Core-talk
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
<2020>
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: ABI compatibility with different C++ standard versions Konrad, Martin via Core-talk
- Next:
Re: ABI compatibility with different C++ standard versions Michael Davidsaver via Core-talk
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
<2020>
2021
2022
2023
2024
|