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: | Re: Weird behavior when linking libgdd |
From: | Ralph Lange <[email protected]> |
To: | EPICS Core-Talk <[email protected]> |
Date: | Tue, 05 May 2015 14:40:45 +0200 |
On 05/05/2015 13:26, Michael Davidsaver wrote:
On 05/05/2015 03:43 AM, Ralph Lange wrote:The RPM check assumes the standard scenario where the 'build' target builds and the 'install' target installs. So you can safely have the debug information in the libraries contain the build location path, because the install moves it to a different location - and that new location is what the check-buildroot checks against.Is this check really being done before debug symbols are (or would be) stripped? As I think about this, I would expect that this situation would be handled by checking after the creation of a *-debuginfo .rpm (using the ELF .gnu_debuglink extension).
The check is being done after stripping. But: Only the shared libraries are stripped.The test fails for the static library and the debuginfo parts. The shared library passes.
(This sounds silly. I know. Don't ask me.) ~Ralph