i have both qt4 and qt5 installed : When trying to emerge openscenegraph from the gamerlay overlay, it fails on moc. It uses the one from qt5 while i'm pretty sure it's supposed to use qt4. Stuff on autoconf at start mentions qt4. Reproducible: Always % equery belongs /usr/lib64/qt5/bin/moc /usr/bin/moc * Searching for /usr/lib64/qt5/bin/moc,/usr/bin/moc ... dev-qt/qtcore-4.8.5 (/usr/bin/moc) dev-qt/qtcore-5.2.9999 (/usr/lib64/qt5/bin/moc) (last one from qt overlay..)
Created attachment 365954 [details] build.log (trimmed unimportant compilation stuff to fit 1mb)
don't assign gamerlay bugs to games team. It's an unsupported overlay
I just tested, and I don't have the problem with dev-games/openscenegraph-3.0.1-r1 (last version in gentoo tree)
(In reply to Julian Ospald (hasufell) from comment #2) > don't assign gamerlay bugs to games team. It's an unsupported overlay Was it for me ? I did not assign anything to anyone. I choose a "component" in the bug report dialog. The indications are "The area where the problem occurs."
Confirming. I have qt5 from qt overlay, and one time it tries to use qt5 moc (as says its output) with wrong arguments, as it just prints help output in log.
Thomas Capricelli: that was about version 3.2.0. Version 3.0.1 seems to be from gentoo. Hm... may be try to bump _this_ one? I also have OSG from gamerlay. It was installed before i decided to try qt5, now it is in @preserved-rebuild list due to upgrade of its deps, including libpng, jpeg and some other.
(In reply to Nikita Zlobin from comment #6) > Thomas Capricelli: that was about version 3.2.0. Version 3.0.1 seems to be > from gentoo. Hm... may be try to bump _this_ one? I don't understand what you say. I have 3.0.1-r1 installed (from main tree, +qt4), and the failure happens when gentoo tries to update to 3.2.0 (from overlay)
I can confirm the bug is still there. I tried the turnaround from bug #479046 (defining MOC5=), but this doesn't work.
I've tried to contac original package maintainer via email and ask him to take a look on this bug. Let's give him few days to react, then I'd try to do something.
Thanks for the heads up. I'll look into this and have to install qt5 first ;)