On 11/23/22 10:15, Michael Davidsaver wrote:
On 11/22/22 13:32, Daykin, Evan via Tech-talk wrote:
... Now that we are getting these warnings, can they be ignored, or is this convention broken/otherwise disfavored in EPICS 7?
More than a convention, this warning is alerting you to potential problems
with compiler/linker search path. The order of entries in
'configure/RELEASE' determines the order of -I and -L arguments passed.
eg. a situation like you describe:
AUTOSAVE=/usr/lib/epics
ASYN=/my/special/asyn
EPICS_BASE=/usr/lib/epics
Would result in
-I/usr/lib/epics/include -I/my/special/modbus/include -I/usr/lib/epics/include
If asynDriver.h were present in both directories, the version
"/usr/lib/epics/include/asynDriver.h" would be used instead of the intended
"/my/special/asyn/include/asynDriver.h".
Corrected...
- References:
- Multiple pointers to /usr/lib/epics Daykin, Evan via Tech-talk
- Re: Multiple pointers to /usr/lib/epics Michael Davidsaver via Tech-talk
- Navigate by Date:
- Prev:
Re: Multiple pointers to /usr/lib/epics Michael Davidsaver via Tech-talk
- Next:
Re: Convert ai record into timestamp Andrew Johnson via Tech-talk
- 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: Multiple pointers to /usr/lib/epics Michael Davidsaver via Tech-talk
- Next:
EPICS startup script st.cmd on vxWorks warning message whitetiger1123 via Tech-talk
- 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
| 
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·