Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 510100

Summary: [qt overlay] dev-qt/qtcore-5.2.1: test_private_includes test fails
Product: Gentoo Linux Reporter: Lubos Dolezel <lubos>
Component: [OLD] LibraryAssignee: Qt Bug Alias <qt>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description Lubos Dolezel 2014-05-11 20:59:02 UTC
qtbase contains various automated tests, one of them being test_private_includes which checks that private Qt headers (such as QPA) can be accessed by CMake-based build systems that need them.

I am writing such an application on Gentoo and private includes don't work for me. I've run this automated test to see if I'm doing something wrong and it fails as well. Hence I consider this a bug in the Gentoo package, because I assume that all tests should pass.

The test is located in qtbase-opensource-src-5.2.1/tests/auto/cmake/test_private_includes.

lubos@zeus /tmp/test_private_includes $ make
Scanning dependencies of target testapp
[100%] Building CXX object CMakeFiles/testapp.dir/main.cpp.o
/tmp/test_private_includes/main.cpp:44:33: fatal error: qpa/qplatformscreen.h: No such file or directory                                                                                                                                                                       
compilation terminated.
CMakeFiles/testapp.dir/build.make:57: recipe for target 'CMakeFiles/testapp.dir/main.cpp.o' failed
make[2]: *** [CMakeFiles/testapp.dir/main.cpp.o] Error 1
CMakeFiles/Makefile2:63: recipe for target 'CMakeFiles/testapp.dir/all' failed
make[1]: *** [CMakeFiles/testapp.dir/all] Error 2
Makefile:75: recipe for target 'all' failed
make: *** [all] Error 2
Comment 1 Johannes Huber (RETIRED) gentoo-dev 2014-05-11 21:16:31 UTC
Please don't assign maintainer by yourself
Comment 2 Davide Pesavento (RETIRED) gentoo-dev 2014-05-12 00:23:18 UTC

*** This bug has been marked as a duplicate of bug 497312 ***