Experimental Physics and Industrial Control System
|
I have an interesting observation:
When building EPICS Base and installing in a different place using
INSTALL_LOCATION, the linked libgdd contains the directory where it
was installed to, as a grep'able string, while all the other
libraries in Base don't. (Currently building 3.15.2.rc1, but other
versions are the same.)
E.g., after building using "make INSTALL_LOCATION=`pwd`/NNN", I can
~/work/CODAC/base-3.15.2-rc1 > grep "NNN"
NNN/lib/linux-x86_64/libdbRecStd.a
~/work/CODAC/base-3.15.2-rc1 > grep "NNN"
NNN/lib/linux-x86_64/libgdd.a
Binary file NNN/lib/linux-x86_64/libgdd.a matches
This leads to gdd failing "check-buildroot" when building an RPM.
That test tries to make sure that binaries and libraries contain no
dependencies to the place they were built.
I have been poking around for quite a while, but I can neither find
the difference between gdd and all the other libraries, nor am I
able to suppress the embedded build-path.
Any ideas?
Thanks a lot,
~Ralph
|
- Replies:
- Re: Weird behavior when linking libgdd Michael Davidsaver
- Re: Weird behavior when linking libgdd Andrew Johnson
- Navigate by Date:
- Prev:
Re: Jenkins build is back to normal : epics-base-3.15-cyg64 #200 Andrew Johnson
- Next:
Re: Weird behavior when linking libgdd Michael Davidsaver
- 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: Cygnus support Michael Davidsaver
- Next:
Re: Weird behavior when linking libgdd Michael Davidsaver
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
<2015>
2016
2017
2018
2019
2020
2021
2022
2023
2024
|
ANJ, 16 Dec 2015 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
·
Search
·
EPICS V4
·
IRMIS
·
Talk
·
Bugs
·
Documents
·
Links
·
Licensing
·
|