Hi Nick,
On 2012-10-24 [email protected] wrote:
>
> I don't know the details, but I suspect this will impact the large number
> of sites (like Diamond) that have not upgraded to VxWorks 6. This may be
> because when EPICS moved to 3.14 and the IOC became portable, a lot of us
> decided that our futures lay elsewhere.
This is not related to vxWorks at all; we will continue to support vxWorks
5.5.x for as long as possible, but this question relates only to systems using
the Posix OSD routines in libCom. Our vxWorks OSD routines do not use those
Posix routines.
Ralph asked:
> to get access to the Posix spinlocks, one must set
> -D_POSIX_C_SOURCE=200112L (or greater).
> Currently, base uses -D_POSIX_C_SOURCE=199506L.
>
> Should we change this globally? Would this break anything?
I suspect not, have you tried it on Linux? Assuming that does what you need
I'd say go ahead and we can test the result to ensure it doesn't break other
architectures later.
- Andrew
--
Never interrupt your enemy when he is making a mistake.
-- Napoleon Bonaparte
- Replies:
- Re: RFC: libCom/osi - new spinlock API Ralph Lange
- References:
- RFC: libCom/osi - new spinlock API Ralph Lange
- Re: RFC: libCom/osi - new spinlock API Ralph Lange
- RE: RFC: libCom/osi - new spinlock API nick.rees
- Navigate by Date:
- Prev:
RE: RFC: libCom/osi - new spinlock API nick.rees
- Next:
Re: RFC: libCom/osi - new spinlock API Ralph Lange
- 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: RFC: libCom/osi - new spinlock API nick.rees
- Next:
Re: RFC: libCom/osi - new spinlock API Ralph Lange
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
<2012>
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|