I wish to build a source rpm package but for only the command-line components of wirshark 2.0.1. Looking at previous queries this looked possible by first specifying "--disable-wireshark" for the configure script argument. This appears successful for the configure stage and when running just "make". However if I wish to use the provided rpm spec content and then run: make rpm-package this fails the configure check with : configure: error: Neither Qt nor GTK+ 2.12.0 or later are available, so Wireshark can't be compiled I have also tried modifying the spec so that all gui conditions options are excluded - e.g "%bcond_without qt " and can see this relected in makefile.in with: RPMBUILD_WITH_ARGS = --without gtk2 --without gtk3 --without qt --without qt5 --without lua However the configure check fails before reading the spec. for the rpmbuild asked 08 Jan '16, 08:10 windymc |
One Answer:
In general the RPM generation assumes you're building both the GUI and CLI. Once built you can install only the CLI but it's set up so you do actually have to build both. If that's not possible (because the system you're compiling on doesn't have Qt nor Gtk) then you'll need to hack up the spec file. Keep in mind that In other words when you (manually) run ./configure (before answered 08 Jan '16, 09:54 JeffMorriss ♦ |
As below, Had to do a bit a more work with the spec than just take out the qt & gtk package sections and adding "--disable-wireshark". But have now built the source rpm so thanks for your help Jeff:-)
"--disable-warnings-as-errors" parameter is not known so removed it .
And also rpmbuild fails with "could not find file" due to following: %exclude %{_bindir}/wireshark*
%exclude %{_mandir}/man1/wireshark.* %exclude %{_datadir}/applications/wireshark-gtk.desktop
...so removed them. Even though the purpose of them is to say don't worry about including them, rpm logic has to verify that they exist and then exclude them !