Am 27.08.2017 um 18:49 schrieb Hartmut Goebel:
> It is searched in several sub-directories of
> /tmp/guix-build-…/qtwayland-opensource-src-5.9.1/plugins/platforms/../../../
> (which is the /tmp/guix-build-qtwayland-5.9.1.drv-0 directory), but
> not in …/lib. I did not find out how to
Uff, I tracked this down in a heavy thinking session.
*
This search-path stems from the libraries RUNPATH, which was
$ORIGIN/../../lib and is now only $ORIGIN/../../../
*
The RUNPATH is set in
/gnu/store/…-qtbase-5.9.1/lib/qt5/mkspecs/features/qt.prf line 272,
using the relative path from $$qtRelativeRPathBase (which equals
$target.path, which is
/gnu/store/…-qtbase-5.9.1/lib/qt5/plugins/platforms) to
$QT_INSTALL_LIBS (which is /gnu/store/…-qtbase-5.9.1/lib). This
relative path obviously is ../../../ .
*
Prior to this patch we installed the plugins into
…-qtbase-5.9.1/plugins, which results in the aforementioned relative
path to be ../../lib and the RUNPATH to be set to $ORIGIN/../../lib.
Conclusions:
1. It's been pure luck that the qtwayland tests passed prior to this change.
2. Do make the tests pass, we need to set LD_LIBRARY_PATH prior to
running the tests
3. tests of other packages may fail for the same reason.
I'll take care of the packages in kde-frameworks.scm, I assume/hope
Thomas will take care of the ones in kde.scm.
宋文武, how can we coordinate the required changes? Should they go into one
patch? Or into a series?
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.goe...@crazy-compilers.com |
| www.crazy-compilers.com | compilers which you thought are impossible |
