Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 562860 - dev-qt/qt-creator-3.5.0 requires clang>=3.6.0 even without clang flag
Summary: dev-qt/qt-creator-3.5.0 requires clang>=3.6.0 even without clang flag
Status: RESOLVED DUPLICATE of bug 560398
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal minor (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-10-11 21:55 UTC by Jan K
Modified: 2015-10-13 17:28 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jan K 2015-10-11 21:55:31 UTC
Hello,

I've been trying to emerge qt-creator-3.5 without clang flag:
[ebuild  N    ~] dev-qt/qt-creator-3.5.0  USE="cmake git python subversion valgrind webkit -android -autotools -baremetal -bazaar -clang -clearcase -cvs -doc -ios -mercurial -perforce -qbs -qnx -systemd {-test} -winrt"

I have clang in my system, v3.5.0. qt-creator build failed, build log ends with:

Project ERROR: LLVM/Clang version >= 3.6.0 required, version provided: 3.5.0
Makefile:224: recipe for target 'sub-clangbackend-make_first' failed
make[2]: *** [sub-clangbackend-make_first] Error 3

qt-creator ebuild depends on correct clang iff clang flag is enabled (which is not my case).
IMHO either configure is broken, or just qt-creator tries to build clang plugins regardless. Still, the build fails.


Reproducible: Always
Comment 1 jannis 2015-10-12 12:36:43 UTC
Without clang installed, it also fails but differently. At the configuration-step, this line is printed:
 * Disabling clang plugin

Later, the build fails with this:
Project ERROR: Cannot find Clang shared library in /usr/lib64
Makefile:224: die Regel für Ziel „sub-clangbackend-make_first“ scheiterte
Comment 2 Davide Pesavento (RETIRED) gentoo-dev 2015-10-13 17:28:33 UTC

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