We had a discussion about this recently at ESS, due to our EPICS base environment having been compiled with an older c++ standard while one particular module needed c++11.
Assuming that you are using gcc, this page seems to describe potential incompatibilities:
https://gcc.gnu.org/wiki/Cxx11AbiCompatibility
I can't see anything specific in there that matches the potential issues described on this page, but there are a few standard library references that seem to be present, so who knows.
(In the end, for us we were about to release base 7.0.5, so it was a natural time to update the site-wide c++ standard)
Cheers,
Simon
On 2021-04-29, 00:17, "Core-talk on behalf of Michael Davidsaver via Core-talk" <core-talk-bounces at aps.anl.gov on behalf of core-talk at aps.anl.gov> wrote:
On 4/28/21 2:21 PM, Mark Rivers via Core-talk wrote:
> this because if I build NDPluginPVA with the c++11 flag I also need to build base with the same flag?
At least pvDataCPP and pvAccessCPP, yes. It wouldn't hurt to build Base with c++11 as well.
- References:
- Problem building NDPluginPVA on base 7.0.5 Mark Rivers via Core-talk
- Re: Problem building NDPluginPVA on base 7.0.5 Michael Davidsaver via Core-talk
- Navigate by Date:
- Prev:
Re: Problem building NDPluginPVA on base 7.0.5 Michael Davidsaver via Core-talk
- Next:
Re: [Merge] ~anj/epics-base/+git/base-7.0:fix-1824277 into epics-base:7.0 Dirk Zimoch 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: Problem building NDPluginPVA on base 7.0.5 Michael Davidsaver via Core-talk
- Next:
Build failed: epics-base base-integration-700 AppVeyor 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
|