<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - Fix moc-qt5 detection" href="https://bugs.freedesktop.org/show_bug.cgi?id=80250#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - Fix moc-qt5 detection" href="https://bugs.freedesktop.org/show_bug.cgi?id=80250">bug 80250</a> from <a class="email" href="mailto:hib@hiberis.nl" title="Hib Eris <hib@hiberis.nl>"> Hib Eris</a> <pre>(In reply to <a href="show_bug.cgi?id=80250#c6">comment #6</a>) > sure, but who says that moc-qt5 can can return > "moc 5.2" > ? > Is it that hard just adding your case to the regexp? No, it is not hard, but it would be adding a workaround instead of fixing a bug. I've just tested my moc-qt5 by renaming in to 'foo', and then it gives: $ foo -v foo 5.2.1 So it is just returning the command name and the moc version number. In the configure script we are looking for a command (xxx-)moc-qt5, so that will return (xxx-)moc-qt5 5.2.1, which will never match 'moc 5'. Matching with 'moc 5' is wrong. In my opinion it is better to fix that by matching with 'moc-qt5 5' instead.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>