On Tuesday, 23 May 2017 18:31:35 CEST Aleix Pol wrote: > On Sun, Apr 23, 2017 at 12:52 PM, Volker Krause <vkra...@kde.org> wrote: > Hi volker, > I've been looking into how it works, I wanted to test the tests/orwell > application but I keep getting this error: > ./bin/orwell: symbol lookup error: ./bin/orwell: undefined symbol: > _ZN12UserFeedback18CompilerInfoSourceC1Ev > > I'm seeing a similar error when running autotests: > ********* Start testing of DataSourceTest ********* > Config: Using QtTest library 5.9.0, Qt 5.9.0 > (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC > 6.3.1 20170306) > PASS : DataSourceTest::initTestCase() > PASS : DataSourceTest::testPlatformInfoSource() > PASS : DataSourceTest::testScreenInfoSource() > PASS : DataSourceTest::testPropertyRatioSource() > PASS : DataSourceTest::testMultiPropertyRatioSource() > PASS : DataSourceTest::testApplicationVersionSource() > PASS : DataSourceTest::testQtVersionSource() > PASS : DataSourceTest::testStartCountSource() > PASS : DataSourceTest::testUsageTimeSource() > PASS : DataSourceTest::testCpuInfoSource() > PASS : DataSourceTest::testLocaleInfoSource() > ./bin/datasourcetest: symbol lookup error: ./bin/datasourcetest: > undefined symbol: _ZN12UserFeedback16OpenGLInfoSourceC1Ev > > I would have looked into fixing it, but I'm not sure I understand why > there's all the RPATH logic in place, so I'd prefer to hear from you > first.
I have removed the remains of the pre-ECM rpath handling. This also changed binary output directories on Linux to follow KDE standards, so you might want to do a clean build to avoid issues with outdated binaries in the build dir. > A good next step would also be to get it running on build.kde.org, so > we can identify these issues. Indeed, I've requested CI coverage now. Regards, Volker
signature.asc
Description: This is a digitally signed message part.