I was compiling the synApps areaDetector on Cygwin 1.7 under
base 3.14.12.2 using the system libs for netCDF and HDF5 for
fun, but ran into a linker error, complaining that the symbol
"_function" was multiply defined, once in registryIoc.lib and
once in libnetcdf.a. I tracked the EPICS symbol down to the
"const char *function" variable in BASE/src/registry/registryFunction.c:
const char *function = "function";
static void *registryID = (void *)&function;
Seeing as neither symbols seem to be used outside of that file,
I prepended "static" to the declaration of "*function", recompiled
EPICS, and recompiled areaDetector successfully. I've only tested
the new base with softIoc, and areaDetector not at all, so by no
means have I adequately tested this hack. I cannot find any
mention of this particular hack in TechTalk or base Release Notes
or base Known Problems.
Instead, I thought I should ask, is this hack safe (or otherwise
appropriate)?
ru
--
Ru Igarashi Software & Instrumentation Specialist
e-mail: [email protected] Canadian Light Source
ph:306 657 3751 University of Saskatchewan
fax: 306 657 3535 Saskatoon SK S7N 0X4
- Replies:
- Re: OK to make function variable in registryFunction.c static? Andrew Johnson
- Navigate by Date:
- Prev:
Re: [Scopes] BMP image record?? Rod Nussbaumer
- Next:
Re: OK to make function variable in registryFunction.c static? Andrew Johnson
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
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: AreaDetector Roper or PVCam IOC link problem giles.knap
- Next:
Re: OK to make function variable in registryFunction.c static? Andrew Johnson
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
<2012>
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|