Created attachment 407418 [details] "emerge --info" output I tried to emerge the latest stable wireshark with the default use flags. Snippet from /var/tmp/portage/net-analyzer/wireshark-1.12.6/temp/build.log: /usr/lib64/qt5/bin/moc -I.. -I../.. -o related_packet_delegate.moc.cpp related_packet_delegate.h /usr/lib64/qt5/bin/moc -I.. -I../.. -o search_frame.moc.cpp search_frame.h related_packet_delegate.h:0: Note: No relevant classes found. No output generated. ... /usr/lib64/qt5/bin/moc -I.. -I../.. -o simple_dialog_qt.moc.cpp simple_dialog_qt.h /usr/lib64/qt5/bin/moc -I.. -I../.. -o sparkline_delegate.moc.cpp sparkline_delegate.h sparkline_delegate.h:0: Note: No relevant classes found. No output generated. /usr/lib64/qt5/bin/moc -I.. -I../.. -o splash_overlay.moc.cpp splash_overlay.h /usr/lib64/qt5/bin/moc -I.. -I../.. -o stats_tree_dialog.moc.cpp stats_tree_dialog.h /usr/lib64/qt5/bin/moc -I.. -I../.. -o summary_dialog.moc.cpp summary_dialog.h /usr/lib64/qt5/bin/moc -I.. -I../.. -o syntax_line_edit.moc.cpp syntax_line_edit.h /usr/lib64/qt5/bin/moc -I.. -I../.. -o tcp_stream_dialog.moc.cpp tcp_stream_dialog.h /usr/lib64/qt5/bin/moc -I.. -I../.. -o time_shift_dialog.moc.cpp time_shift_dialog.h /usr/lib64/qt5/bin/moc -I.. -I../.. -o uat_dialog.moc.cpp uat_dialog.h /usr/lib64/qt5/bin/moc -I.. -I../.. -o wireshark_application.moc.cpp wireshark_application.h /bin/mkdir -p ../../image /bin/mkdir -p ../../image rcc -name `basename ../../image/about.qrc .qrc` -o ../../image/about.rcc.cpp ../../image/about.qrc rcc -name `basename ../../image/display_filter.qrc .qrc` -o ../../image/display_filter.rcc.cpp ../../image/display_filter.qrc rcc: could not find a Qt installation of '' rcc: could not find a Qt installation of '' Makefile:1708: recipe for target '../../image/about.rcc.cpp' failed make[2]: *** [../../image/about.rcc.cpp] Error 1 make[2]: *** Waiting for unfinished jobs.... Makefile:1708: recipe for target '../../image/display_filter.rcc.cpp' failed make[2]: *** [../../image/display_filter.rcc.cpp] Error 1 make[2]: Leaving directory '/var/tmp/portage/net-analyzer/wireshark-1.12.6/work/wireshark-1.12.6/ui/qt' Makefile:3985: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/var/tmp/portage/net-analyzer/wireshark-1.12.6/work/wireshark-1.12.6' Makefile:2122: recipe for target 'all' failed make: *** [all] Error 2 * ERROR: net-analyzer/wireshark-1.12.6::gentoo failed (compile phase): * emake failed Emerging wireshark with qt5 use flag disabled (e.g. 'sudo USE="-qt5" emerge wireshark') succeeds, though. I'm running KDE Plasma 5 for desktop environment, maybe this has something to do with the failure. I also attached the output of "emerge --info".
Please attach the entire build log to this bug report.
Created attachment 407432 [details] build.log.gz
It looks like you have Qt5 installed but not Qt4. And for some reason ui/qt/Makefile.am expects ` $(AM_V_RCC)rcc ' to resolve into something useful, but that variable isn't set anywhere during configuration, and you have a generic /usr/bin/rcc -> qtchooser that doesn't point to any specific Qt implementation. Since we're already discovering the proper rcc to use in the ebuild, we should probably patch that ui/qt/Makefile.am to use the RCC value we set up. Unless Qt people say we should use qtchooser to fix this for the long run.
Should be fixed now.
(In reply to Jeroen Roovers from comment #3) > It looks like you have Qt5 installed but not Qt4. Yepp. (In reply to Jeroen Roovers from comment #4) > Should be fixed now. I have emerged wireshark again and can confirm the build succeeds now with qt5 use flag, nice job! I'm new to the system, so I'm a bit unsure what to do now - should I change the issue status to "Verified"?
(In reply to Jeroen Roovers from comment #3) > It looks like you have Qt5 installed but not Qt4. And for some reason > ui/qt/Makefile.am expects ` $(AM_V_RCC)rcc ' to resolve into something > useful, but that variable isn't set anywhere during configuration, and you > have a generic > > /usr/bin/rcc -> qtchooser > > that doesn't point to any specific Qt implementation. Since we're already > discovering the proper rcc to use in the ebuild, we should probably patch > that ui/qt/Makefile.am to use the RCC value we set up. > > Unless Qt people say we should use qtchooser to fix this for the long run. Ebuilds should never use the non-version-specific symlinks in /usr/bin, instead they should use "$(qt{4,5}_get_bindir)/rcc".