2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 <2015> 2016 2017 2018 2019 2020 2021 2022 2023 2024 | Index | 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 <2015> 2016 2017 2018 2019 2020 2021 2022 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Weird behavior when linking libgdd |
From: | Ralph Lange <[email protected]> |
To: | EPICS Core-Talk <[email protected]> |
Date: | Mon, 04 May 2015 17:26:08 +0200 |
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 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 |