https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14606
Bug ID: 14606
Summary: wireshark.spec does not reflect choices made for
configure
Product: Wireshark
Version: 2.4.6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: Minor
Priority: Low
Component: Build process
Assignee: bugzilla-ad...@wireshark.org
Reporter: guru4...@web.de
Target Milestone: ---
Created attachment 16264
--> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=16264&action=edit
Result of running "configure"
Build Information:
Compiled (64-bit) with GTK+ 3.22.10, with Cairo 1.14.8, with Pango 1.40.4, with
libpcap, without POSIX capabilities, without libnl, with GLib 2.50.3, with zlib
1.2.7, with SMI 0.4.8, with c-ares 1.10.0, without Lua, without GnuTLS, with
Gcrypt 1.5.3, without Kerberos, without GeoIP, with nghttp2 1.21.1, with LZ4,
with Snappy, with libxml2 2.9.1, without PortAudio, without AirPcap, without
SBC, without SpanDSP.
Running on Linux 3.10.0-862.el7.x86_64, with Intel(R) Xeon(R) CPU E5-2609
v2 @ 2.50GHz (with SSE4.2), with 15805 MB of physical memory, with locale
de_DE.UTF-8, with libpcap version 1.5.3, with Gcrypt 1.5.3, with zlib 1.2.7.
Built using gcc 4.8.5 20150623 (Red Hat 4.8.5-16).
--
I want to build a rpm on RHEL 7.4.
This can be done most convenient provided a SPEC-file exists by "rpmbuild --bb
<file.spec>"
Obviously, there is one in ./packaging/rpm/SPECS (attached).
The configure options given can be seen at the very beginning.
The following statements are contrary to the options given:
%bcond_without qt5 (should read %bcond_with qt5)
%bcond_without gtk2 (should read %bcond_with gtk2)
%bcond_with gtk3 (should read %bcond_without gtk3)
%global with_lz4_and_snappy 1 (should read %global with_lz4_and_snappy 0)
%global with_nghttp2 1 (should read %global with_nghttp2 0)
So I had to make the changes documented above.
I would greatly appreciate if runnung "configure" would produce a correct
spec-file.
Care should be taken to reflect all other possible choices within configure as
well.
--
You are receiving this mail because:
You are watching all bug changes.___________________________________________________________________________
Sent via: Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives: https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
