Wireshark-dev: Re: [Wireshark-dev] Cmake and RPM
From: Jonne Zutt <jonne.zutt.ml@xxxxxxxxx>
Date: Tue, 16 Aug 2016 21:30:53 +0200
Hi,
Yes, that's something on our systems, not sure why exactly. I'll try to build in a different folder, just to be sure.
Thanks.
On Tue, Aug 16, 2016 at 9:12 PM, João Valverde <joao.valverde@xxxxxxxxxxxxxxxxxx> wrote:
The wireshark-2.3.0.tar.xz file should be created automatically in the SOURCES directory, yes, barring any weird mismatches with the full path.
Why the /export root, by the way? Is that something peculiar to your system?
On 08/16/2016 08:00 PM, Jonne Zutt wrote:
No problem, I really appreciate your help.
It looks like this script wants to decompress
/export/home/jonne/wireshark/wireshark/packaging/rpm/SOURCES /wireshark-2.3.0.tar.xz,
but I don't have that file.
Jonne.
$ cat /var/tmp/rpm-tmp.Ys8Pam
#!/bin/sh
RPM_SOURCE_DIR="/export/home/jonne/wireshark/wireshark/packa ging/rpm/SOURCES"
RPM_BUILD_DIR="/export/home/jonne/wireshark/wireshark/packag ing/rpm/BUILD"
RPM_OPT_FLAGS="-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
-fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches
-m64 -mtune=generic"
RPM_LD_FLAGS="-Wl,-z,relro "
RPM_ARCH="x86_64"
RPM_OS="linux"
export RPM_SOURCE_DIR RPM_BUILD_DIR RPM_OPT_FLAGS RPM_LD_FLAGS
RPM_ARCH RPM_OS
RPM_DOC_DIR="/usr/local/share/doc"
export RPM_DOC_DIR
RPM_PACKAGE_NAME="wireshark"
RPM_PACKAGE_VERSION="2.3.0"
RPM_PACKAGE_RELEASE="1"
export RPM_PACKAGE_NAME RPM_PACKAGE_VERSION RPM_PACKAGE_RELEASE
LANG=C
export LANG
unset CDPATH DISPLAY ||:
RPM_BUILD_ROOT="/export/home/jonne/wireshark/wireshark/packa ging/rpm/BUILDROOT/wireshark- 2.3.0-1.x86_64"
export RPM_BUILD_ROOT
PKG_CONFIG_PATH="${PKG_CONFIG_PATH}:/usr/local/lib64/pkgconf ig:/usr/local/share/pkgconfig"
export PKG_CONFIG_PATH
CONFIG_SITE=NONE
export CONFIG_SITE
set -x
umask 022
cd "/export/home/jonne/wireshark/wireshark/packaging/rpm/BUILD"
cd '/export/home/jonne/wireshark/wireshark/packaging/rpm/BUILD'
rm -rf 'wireshark-2.3.0'
/usr/bin/xz -dc
'/export/home/jonne/wireshark/wireshark/packaging/rpm/SOURCE S/wireshark-2.3.0.tar.xz'
| /usr/bin/tar -xf -
STATUS=$?
if [ $STATUS -ne 0 ]; then
exit $STATUS
fi
cd 'wireshark-2.3.0'
/usr/bin/chmod -Rf a+rX,u+w,g-w,o-w .
# Don't specify the prefix here: configure is a macro which expands to set
# the prefix and everything else too. If you need to change the prefix
# set _prefix (note the underscore) either in this file or on rpmbuild's
# command-line.
CFLAGS="${CFLAGS:--O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2
-fexceptions -fstack-protector-strong --param=ssp-buffer-size=4
-grecord-gcc-switches -m64 -mtune=generic}" ; export CFLAGS ;
CXXFLAGS="${CXXFLAGS:--O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2
-fexceptions -fstack-protector-strong --param=ssp-buffer-size=4
-grecord-gcc-switches -m64 -mtune=generic}" ; export CXXFLAGS ;
FFLAGS="${FFLAGS:--O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2
-fexceptions -fstack-protector-strong --param=ssp-buffer-size=4
-grecord-gcc-switches -m64 -mtune=generic
-I/usr/local/lib64/gfortran/modules}" ; export FFLAGS ;
FCFLAGS="${FCFLAGS:--O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2
-fexceptions -fstack-protector-strong --param=ssp-buffer-size=4
-grecord-gcc-switches -m64 -mtune=generic
-I/usr/local/lib64/gfortran/modules}" ; export FCFLAGS ;
LDFLAGS="${LDFLAGS:--Wl,-z,relro }"; export LDFLAGS;
for i in $(find . -name config.guess -o -name config.sub) ; do
[ -f /usr/lib/rpm/redhat/$(basename $i) ] && /usr/bin/rm -f $i &&
/usr/bin/cp -fv /usr/lib/rpm/redhat/$(basename $i) $i ;
done ;
./configure --build=x86_64-redhat-linux-gnu
--host=x86_64-redhat-linux-gnu \
--program-prefix= \
--disable-dependency-tracking \
--prefix=/usr/local \
--exec-prefix=/usr/local \
--bindir=/usr/local/bin \
--sbindir=/usr/local/sbin \
--sysconfdir=/etc \
--datadir=/usr/local/share \
--includedir=/usr/local/include \
--libdir=/usr/local/lib64 \
--libexecdir=/usr/local/libexec \
--localstatedir=/var \
--sharedstatedir=/var/lib \
--mandir=/usr/local/share/man \
--infodir=/usr/local/share/info \
--with-gnu-ld \
--with-c-ares \
--with-lua \
--with-qt=5 \
--without-gtk \
--disable-warnings-as-errors
# Remove rpath. It's prohibited in Fedora[1] and anyway we don't need
it (and
# sometimes it gets in the way).
# [1] https://fedoraproject.org/wiki/Packaging:Guidelines#Beware_ of_Rpath
sed -i 's|^hardcode_libdir_flag_spec=.*|hardcode_libdir_flag_spec=" "|g'
libtool
sed -i 's|^runpath_var=LD_RUN_PATH|runpath_var=DIE_RPATH_DIE|g' libtool
# Suggestion: put this in your ~/.rpmmacros (without the hash sign, of
course):
# -j16 -j 40
make -j16
exit 0
On Tue, Aug 16, 2016 at 8:53 PM, João Valverde
<joao.valverde@tecnico.ulisboa.pt
<mailto:joao.valverde@tecnico.ulisboa.pt >> wrote:
Sorry, that was too terse and not very helpful.
Check /var/tmp/rpm-tmp.P9teqs or some other temp file rpm creates
for the %prep section of the specfile. Mine says:
cd '/home/jpv/wireshark/code/trunk/build/packaging/rpm/BUILD'
rm -rf 'wireshark-2.3.0'
/usr/bin/xz -dc
'/home/jpv/wireshark/code/trunk/build/packaging/rpm/SOURCES/ wireshark-2.3.0.tar.xz'
| /usr/bin/tar -xf -
STATUS=$?
if [ $STATUS -ne 0 ]; then
exit $STATUS
fi
cd 'wireshark-2.3.0'
/usr/bin/chmod -Rf a+rX,u+w,g-w,o-w .
On 08/16/2016 07:46 PM, Jonne Zutt wrote:
I don't seem to have any /path/to/wireshark-2.3.0.tar.xz anywhere.
Should make dist create that?
Thanks,
Jonne.
On Tue, Aug 16, 2016 at 8:42 PM, João Valverde
<joao.valverde@tecnico.ulisboa.pt
<mailto:joao.valverde@tecnico.ulisboa.pt >
<mailto:joao.valverde@tecnico.ulisboa.pt
<mailto:joao.valverde@tecnico.ulisboa.pt >>> wrote:
Thanks. Your rpmbuild output looks wrong, I don't know why.
Your %prep script should have a line like this:
/usr/bin/xz -dc '/path/to/wireshark-2.3.0.tar.xz' |
/usr/bin/tar -xf -
I don't have time right now to test this on Fedora 20.
On 08/16/2016 05:38 PM, Jonne Zutt wrote:
Fedora 20.
$ cat /etc/fedora-release
Fedora release 20 (Heisenbug)
On Tue, Aug 16, 2016 at 6:32 PM, João Valverde
<joao.valverde@tecnico.ulisboa.pt
<mailto:joao.valverde@tecnico.ulisboa.pt >
<mailto:joao.valverde@tecnico.ulisboa.pt
<mailto:joao.valverde@tecnico.ulisboa.pt >>
<mailto:joao.valverde@tecnico.ulisboa.pt
<mailto:joao.valverde@tecnico.ulisboa.pt >
<mailto:joao.valverde@tecnico.ulisboa.pt
<mailto:joao.valverde@tecnico.ulisboa.pt >>>> wrote:
Now that all the build dependencies are present it seems
like you
hit two separate build system bugs.
Which distro/system are you using exactly, please?
On 08/16/2016 05:12 PM, Jonne Zutt wrote:
Thanks to Jeff's suggestion I was able to install
qt5-qttools-devel
which provided me with lrelease-qt5
$ dzdo yum whatprovides /usr/bin/lrelease-qt5
qt5-qttools-devel-5.2.0-0.5.be
<http://qt5-qttools-devel-5.2.0-0.5.be >
<http://qt5-qttools-devel-5.2.0-0.5.be
<http://qt5-qttools-devel-5.2.0-0.5.be >>
<http://qt5-qttools-devel-5.2.0-0.5.be
<http://qt5-qttools-devel-5.2.0-0.5.be >
<http://qt5-qttools-devel-5.2.0-0.5.be
<http://qt5-qttools-devel-5.2.0-0.5.be >>>ta1.fc20.i686 :
Development files for
qt5-qttools
"./configure --with-qt=5 --with-gtk=no" now ends
with:
checking for qtchooser...
/usr/lib/qtchooser/qtchooser
checking for uic... /usr/lib/qtchooser/uic
checking for qtchooser... (cached)
/usr/lib/qtchooser/qtchooser
checking for moc... /usr/lib/qtchooser/moc
checking for qtchooser... (cached)
/usr/lib/qtchooser/qtchooser
checking for rcc... /usr/lib/qtchooser/rcc
checking for qtchooser... (cached)
/usr/lib/qtchooser/qtchooser
checking for lrelease... /usr/lib/qtchooser/lrelease
checking whether lrelease -version works... no
configure: error: /usr/lib/qtchooser/lrelease
-qt=5 -version
returned
non-zero exit status
make: *** No targets specified and no makefile
found. Stop.
Ok, so configure fails when trying "lrelease -qt=5
-version", it
seems
my lrelease doesn't like the -qt=5 argument.
$ lrelease -qt=4 -version
lrelease: could not find a Qt installation of '4'
$ lrelease -qt=5 -version
lrelease: could not find a Qt installation of '5'
$ lrelease -qt=default -version
lrelease version 4.8.6
It seems to like -qt=qt5 though:
$ /usr/lib/qtchooser/lrelease -qt=qt5 -version
lrelease version 5.3.2
I changed:
LRELEASE="$LRELEASE -qt=$qt_version"
into
LRELEASE="$LRELEASE
-qt=qt$qt_version"
Then configure seems to work:
checking for qtchooser...
/usr/lib/qtchooser/qtchooser
checking for uic... /usr/lib/qtchooser/uic
checking for qtchooser... (cached)
/usr/lib/qtchooser/qtchooser
checking for moc... /usr/lib/qtchooser/moc
checking for qtchooser... (cached)
/usr/lib/qtchooser/qtchooser
checking for rcc... /usr/lib/qtchooser/rcc
checking for qtchooser... (cached)
/usr/lib/qtchooser/qtchooser
checking for lrelease... /usr/lib/qtchooser/lrelease
checking whether lrelease -version works... ok,
lrelease
version
5.3.2
It seems I need to do the same for UIC:
UIC ui_about_dialog.h
uic: could not find a Qt installation of '5'
UIC="$UIC -qt=qt$qt_version"
And also for MOC, RCC.
Maybe I should've changed qt_version, but
anyways, I do
not see
a neat
way for that (e.g., cannot provide --with-qt=qt5 to
configure).
Seems like I'm almost there, getting to closer
to build
an rpm:
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.P9teqs
+ umask 022
+ cd
/export/home/jonne/wireshark/wireshark/packaging/rpm/BUILD
+ cd
/export/home/jonne/wireshark/wireshark/packaging/rpm/BUILD
+ rm -rf wireshark-2.3.0
+ /usr/bin/tar -xf -
+ /usr/bin/xz -dc
/export/home/jonne/wireshark/wireshark/packaging/rpm/SOURCES /wireshark-2.3.0.tar.xz
/usr/bin/tar: This does not look like a tar archive
/usr/bin/tar: Exiting with failure status due to
previous errors
error: Bad exit status from
/var/tmp/rpm-tmp.P9teqs (%prep)
RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.P9teqs
(%prep)
Thanks for you help,
Jonne.
$ qtchooser -qt=5 -version
qtchooser: unknown option: -version
$ qtchooser -qt=5
Usage:
qtchooser { -l | -list-versions | -print-env }
qtchooser -run-tool=<tool name> [-qt=<Qt version>]
[program
arguments]
<executable name> [-qt=<Qt version>] [program
arguments]
Environment variables accepted:
QTCHOOSER_RUNTOOL name of the tool to be run
(same as the
-run-tool
argument)
QT_SELECT version of Qt to be run
(same as the -qt
argument)
$ qtchooser -qt=5 -l
default
qt4-64
qt4
qt5-64
qt5
On Tue, Aug 16, 2016 at 4:14 PM, João Valverde
<joao.valverde@tecnico.ulisboa.pt
<mailto:joao.valverde@tecnico.ulisboa.pt >
<mailto:joao.valverde@tecnico.ulisboa.pt
<mailto:joao.valverde@tecnico.ulisboa.pt >>
<mailto:joao.valverde@tecnico.ulisboa.pt
<mailto:joao.valverde@tecnico.ulisboa.pt >
<mailto:joao.valverde@tecnico.ulisboa.pt
<mailto:joao.valverde@tecnico.ulisboa.pt >>>
<mailto:joao.valverde@tecnico.ulisboa.pt
<mailto:joao.valverde@tecnico.ulisboa.pt >
<mailto:joao.valverde@tecnico.ulisboa.pt
<mailto:joao.valverde@tecnico.ulisboa.pt >>
<mailto:joao.valverde@tecnico.ulisboa.pt
<mailto:joao.valverde@tecnico.ulisboa.pt >
<mailto:joao.valverde@tecnico.ulisboa.pt
<mailto:joao.valverde@tecnico.ulisboa.pt >>>>> wrote:
I wasn't aware of that shell script, it
might need
updating.
This part of the Qt toolchain (qt-tools) is
awkward,
to be
kind, and
detection might not work always well.
Feel free to ask for help here if you get stuck.
You need lrelease to build the Qt GUI. Not
sure what
is going on
with qtchooser.
On 08/16/2016 02:41 PM, Jonne Zutt wrote:
I see, thanks for that. I was already trying
this path after
reading the
reply of Anders.
I installed the rpms that were suggested
by wireshark/tools/install_rpms_for_devel.sh
I then also installed
qtchooser-39-1.fc20.x86_64, but
configure
is still
unable to find it somehow. I guess I need to
help it a bit
somehow, I'll
keep trying!
Thanks,
Jonne.
....
checking for GLIB... yes
checking for Qt5Core - version >=
5.0.0... yes
(version
5.3.2)
checking for Qt5Gui - version >=
5.0.0... yes
(version
5.3.2)
checking for Qt5Widgets - version >=
5.0.0... yes
(version 5.3.2)
checking for Qt5PrintSupport - version >=
5.0.0... yes
(version
5.3.2)
checking for Qt5Multimedia - version >=
5.0.0... yes
(version 5.3.2)
checking for Qt5MacExtras - version >=
5.0.0... no
checking whether Qt works without
-fPIC... no
checking whether Qt works with -fPIC... yes
checking for qtchooser... no
checking for uic-qt5... /usr/bin/uic-qt5
checking for qtchooser... no
checking for moc-qt5... /usr/bin/moc-qt5
checking for qtchooser... no
checking for rcc-qt5... /usr/bin/rcc-qt5
checking for qtchooser... no
checking for lrelease-qt5... no
checking for lrelease... no
configure: error: I couldn't find
lrelease-qt5 or
lrelease; make
sure
it's installed and in your path
make: *** No targets specified and no
makefile
found. Stop.
On Tue, Aug 16, 2016 at 1:57 PM, João
Valverde
<joao.valverde@tecnico.ulisboa.pt
<mailto:joao.valverde@tecnico.ulisboa.pt >
<mailto:joao.valverde@tecnico.ulisboa.pt
<mailto:joao.valverde@tecnico.ulisboa.pt >>
<mailto:joao.valverde@tecnico.ulisboa.pt
<mailto:joao.valverde@tecnico.ulisboa.pt >
<mailto:joao.valverde@tecnico.ulisboa.pt
<mailto:joao.valverde@tecnico.ulisboa.pt >>>
<mailto:joao.valverde@tecnico.ulisboa.pt
<mailto:joao.valverde@tecnico.ulisboa.pt >
<mailto:joao.valverde@tecnico.ulisboa.pt
<mailto:joao.valverde@tecnico.ulisboa.pt >>
<mailto:joao.valverde@tecnico.ulisboa.pt
<mailto:joao.valverde@tecnico.ulisboa.pt >
<mailto:joao.valverde@tecnico.ulisboa.pt
<mailto:joao.valverde@tecnico.ulisboa.pt >>>>
<mailto:joao.valverde@tecnico.ulisboa.pt
<mailto:joao.valverde@tecnico.ulisboa.pt >
<mailto:joao.valverde@tecnico.ulisboa.pt
<mailto:joao.valverde@tecnico.ulisboa.pt >>
<mailto:joao.valverde@tecnico.ulisboa.pt
<mailto:joao.valverde@tecnico.ulisboa.pt >
<mailto:joao.valverde@tecnico.ulisboa.pt
<mailto:joao.valverde@tecnico.ulisboa.pt >>>
<mailto:joao.valverde@tecnico.ulisboa.pt
<mailto:joao.valverde@tecnico.ulisboa.pt >
<mailto:joao.valverde@tecnico.ulisboa.pt
<mailto:joao.valverde@tecnico.ulisboa.pt >>
<mailto:joao.valverde@tecnico.ulisboa.pt
<mailto:joao.valverde@tecnico.ulisboa.pt >
<mailto:joao.valverde@tecnico.ulisboa.pt
<mailto:joao.valverde@tecnico.ulisboa.pt >>>>>> wrote:
On 08/16/2016 10:23 AM, Jonne Zutt
wrote:
Hi all,
Could somebody tell me what I
have to do
to be
able to
build an
RPM package?
You have to use autotools. :-)
CMake doesn't support building an rpm
package yet (see
README.cmake).
I successfully build wireshark using
cmake and make.
I have a working wireshark-gtk
executable in the
build
directory
that I
can run and works fine.
Now, if I try to run "make
rpm-package", it
seems it doesn't
know the
target. I wonder what I have to
do to
get this?
$ make rpm-package
make: *** No rule to make target
`rpm-package'.
Stop.
Thanks,
Jonne.
____________________________________________________________ _______________
Sent via: Wireshark-dev
mailing list
<wireshark-dev@xxxxxxxxxxxxx
<mailto:wireshark-dev@wireshark.org >
<mailto:wireshark-dev@wireshark.org
<mailto:wireshark-dev@wireshark.org >>
<mailto:wireshark-dev@wireshark.org
<mailto:wireshark-dev@wireshark.org >
<mailto:wireshark-dev@wireshark.org
<mailto:wireshark-dev@wireshark.org >>>
<mailto:wireshark-dev@wireshark.org
<mailto:wireshark-dev@wireshark.org >
<mailto:wireshark-dev@wireshark.org
<mailto:wireshark-dev@wireshark.org >>
<mailto:wireshark-dev@wireshark.org
<mailto:wireshark-dev@wireshark.org >
<mailto:wireshark-dev@wireshark.org
<mailto:wireshark-dev@wireshark.org >>>>
<mailto:wireshark-dev@wireshark.org
<mailto:wireshark-dev@wireshark.org >
<mailto:wireshark-dev@wireshark.org
<mailto:wireshark-dev@wireshark.org >>
<mailto:wireshark-dev@wireshark.org
<mailto:wireshark-dev@wireshark.org >
<mailto:wireshark-dev@wireshark.org
<mailto:wireshark-dev@wireshark.org >>>
<mailto:wireshark-dev@wireshark.org
<mailto:wireshark-dev@wireshark.org >
<mailto:wireshark-dev@wireshark.org
<mailto:wireshark-dev@wireshark.org >>
<mailto:wireshark-dev@wireshark.org
<mailto:wireshark-dev@wireshark.org >
<mailto:wireshark-dev@wireshark.org
<mailto:wireshark-dev@wireshark.org >>>>>>
Archives:
https://www.wireshark.org/lists/wireshark-dev
<https://www.wireshark.org/lists/wireshark-dev >
<https://www.wireshark.org/lists/wireshark-dev
<https://www.wireshark.org/lists/wireshark-dev >>
<https://www.wireshark.org/lists/wireshark-dev
<https://www.wireshark.org/lists/wireshark-dev >
<https://www.wireshark.org/lists/wireshark-dev
<https://www.wireshark.org/lists/wireshark-dev >>>
<https://www.wireshark.org/lists/wireshark-dev
<https://www.wireshark.org/lists/wireshark-dev >
<https://www.wireshark.org/lists/wireshark-dev
<https://www.wireshark.org/lists/wireshark-dev >>
<https://www.wireshark.org/lists/wireshark-dev
<https://www.wireshark.org/lists/wireshark-dev >
<https://www.wireshark.org/lists/wireshark-dev
<https://www.wireshark.org/lists/wireshark-dev >>>>
<https://www.wireshark.org/lists/wireshark-dev
<https://www.wireshark.org/lists/wireshark-dev >
<https://www.wireshark.org/lists/wireshark-dev
<https://www.wireshark.org/lists/wireshark-dev >>
<https://www.wireshark.org/lists/wireshark-dev
<https://www.wireshark.org/lists/wireshark-dev >
<https://www.wireshark.org/lists/wireshark-dev
<https://www.wireshark.org/lists/wireshark-dev >>>
<https://www.wireshark.org/lists/wireshark-dev
<https://www.wireshark.org/lists/wireshark-dev >
<https://www.wireshark.org/lists/wireshark-dev
<https://www.wireshark.org/lists/wireshark-dev >>
<https://www.wireshark.org/lists/wireshark-dev
<https://www.wireshark.org/lists/wireshark-dev >
<https://www.wireshark.org/lists/wireshark-dev
<https://www.wireshark.org/lists/wireshark-dev >>>>>
Unsubscribe:
https://wireshark.org/mailman/options/wireshark-dev
<https://wireshark.org/mailman/options/wireshark-dev >
<https://wireshark.org/mailman/options/wireshark-dev
<https://wireshark.org/mailman/options/wireshark-dev >>
<https://wireshark.org/mailman/options/wireshark-dev
<https://wireshark.org/mailman/options/wireshark-dev >
<https://wireshark.org/mailman/options/wireshark-dev
<https://wireshark.org/mailman/options/wireshark-dev >>>
<https://wireshark.org/mailman/options/wireshark-dev
<https://wireshark.org/mailman/options/wireshark-dev >
<https://wireshark.org/mailman/options/wireshark-dev
<https://wireshark.org/mailman/options/wireshark-dev >>
<https://wireshark.org/mailman/options/wireshark-dev
<https://wireshark.org/mailman/options/wireshark-dev >
<https://wireshark.org/mailman/options/wireshark-dev
<https://wireshark.org/mailman/options/wireshark-dev >>>>
<https://wireshark.org/mailman/options/wireshark-dev
<https://wireshark.org/mailman/options/wireshark-dev >
<https://wireshark.org/mailman/options/wireshark-dev
<https://wireshark.org/mailman/options/wireshark-dev >>
<https://wireshark.org/mailman/options/wireshark-dev
<https://wireshark.org/mailman/options/wireshark-dev >
<https://wireshark.org/mailman/options/wireshark-dev
<https://wireshark.org/mailman/options/wireshark-dev >>>
<https://wireshark.org/mailman/options/wireshark-dev
<https://wireshark.org/mailman/options/wireshark-dev >
<https://wireshark.org/mailman/options/wireshark-dev
<https://wireshark.org/mailman/options/wireshark-dev >>
<https://wireshark.org/mailman/options/wireshark-dev
<https://wireshark.org/mailman/options/wireshark-dev >
<https://wireshark.org/mailman/options/wireshark-dev
<https://wireshark.org/mailman/options/wireshark-dev >>>>>
mailto:wireshark-dev-request@wireshark.org
<mailto:wireshark-dev-request@wireshark.org >
<mailto:wireshark-dev-request@wireshark.org
<mailto:wireshark-dev-request@wireshark.org >>
<mailto:wireshark-dev-request@wireshark.org
<mailto:wireshark-dev-request@wireshark.org >
<mailto:wireshark-dev-request@wireshark.org
<mailto:wireshark-dev-request@wireshark.org >>>
<mailto:wireshark-dev-request@wireshark.org
<mailto:wireshark-dev-request@wireshark.org >
<mailto:wireshark-dev-request@wireshark.org
<mailto:wireshark-dev-request@wireshark.org >>
<mailto:wireshark-dev-request@wireshark.org
<mailto:wireshark-dev-request@wireshark.org >
<mailto:wireshark-dev-request@wireshark.org
<mailto:wireshark-dev-request@wireshark.org >>>>
<mailto:wireshark-dev-request@wireshark.org
<mailto:wireshark-dev-request@wireshark.org >
<mailto:wireshark-dev-request@wireshark.org
<mailto:wireshark-dev-request@wireshark.org >>
<mailto:wireshark-dev-request@wireshark.org
<mailto:wireshark-dev-request@wireshark.org >
<mailto:wireshark-dev-request@wireshark.org
<mailto:wireshark-dev-request@wireshark.org >>>
<mailto:wireshark-dev-request@wireshark.org
<mailto:wireshark-dev-request@wireshark.org >
<mailto:wireshark-dev-request@wireshark.org
<mailto:wireshark-dev-request@wireshark.org >>
<mailto:wireshark-dev-request@wireshark.org
<mailto:wireshark-dev-request@wireshark.org >
<mailto:wireshark-dev-request@wireshark.org
<mailto:wireshark-dev-request@wireshark.org >>>>>?subject=unsubscribe
____________________________________________________________ _______________
Sent via: Wireshark-dev mailing list
<wireshark-dev@xxxxxxxxxxxxx
<mailto:wireshark-dev@wireshark.org >
<mailto:wireshark-dev@wireshark.org
<mailto:wireshark-dev@wireshark.org >>
<mailto:wireshark-dev@wireshark.org
<mailto:wireshark-dev@wireshark.org >
<mailto:wireshark-dev@wireshark.org
<mailto:wireshark-dev@wireshark.org >>>
<mailto:wireshark-dev@wireshark.org
<mailto:wireshark-dev@wireshark.org >
<mailto:wireshark-dev@wireshark.org
<mailto:wireshark-dev@wireshark.org >>
<mailto:wireshark-dev@wireshark.org
<mailto:wireshark-dev@wireshark.org >
<mailto:wireshark-dev@wireshark.org
<mailto:wireshark-dev@wireshark.org >>>>
<mailto:wireshark-dev@wireshark.org
<mailto:wireshark-dev@wireshark.org >
<mailto:wireshark-dev@wireshark.org
<mailto:wireshark-dev@wireshark.org >>
<mailto:wireshark-dev@wireshark.org
<mailto:wireshark-dev@wireshark.org >
<mailto:wireshark-dev@wireshark.org
<mailto:wireshark-dev@wireshark.org >>>
<mailto:wireshark-dev@wireshark.org
<mailto:wireshark-dev@wireshark.org >
<mailto:wireshark-dev@wireshark.org
<mailto:wireshark-dev@wireshark.org >>
<mailto:wireshark-dev@wireshark.org
<mailto:wireshark-dev@wireshark.org >
<mailto:wireshark-dev@wireshark.org
<mailto:wireshark-dev@wireshark.org >>>>>>
Archives:
https://www.wireshark.org/lists/wireshark-dev
<https://www.wireshark.org/lists/wireshark-dev >
<https://www.wireshark.org/lists/wireshark-dev
<https://www.wireshark.org/lists/wireshark-dev >>
<https://www.wireshark.org/lists/wireshark-dev
<https://www.wireshark.org/lists/wireshark-dev >
<https://www.wireshark.org/lists/wireshark-dev
<https://www.wireshark.org/lists/wireshark-dev >>>
<https://www.wireshark.org/lists/wireshark-dev
<https://www.wireshark.org/lists/wireshark-dev >
<https://www.wireshark.org/lists/wireshark-dev
<https://www.wireshark.org/lists/wireshark-dev >>
<https://www.wireshark.org/lists/wireshark-dev
<https://www.wireshark.org/lists/wireshark-dev >
<https://www.wireshark.org/lists/wireshark-dev
<https://www.wireshark.org/lists/wireshark-dev >>>>
<https://www.wireshark.org/lists/wireshark-dev
<https://www.wireshark.org/lists/wireshark-dev >
<https://www.wireshark.org/lists/wireshark-dev
<https://www.wireshark.org/lists/wireshark-dev >>
<https://www.wireshark.org/lists/wireshark-dev
<https://www.wireshark.org/lists/wireshark-dev >
<https://www.wireshark.org/lists/wireshark-dev
<https://www.wireshark.org/lists/wireshark-dev >>>
<https://www.wireshark.org/lists/wireshark-dev
<https://www.wireshark.org/lists/wireshark-dev >
<https://www.wireshark.org/lists/wireshark-dev
<https://www.wireshark.org/lists/wireshark-dev >>
<https://www.wireshark.org/lists/wireshark-dev
<https://www.wireshark.org/lists/wireshark-dev >
<https://www.wireshark.org/lists/wireshark-dev
<https://www.wireshark.org/lists/wireshark-dev >>>>>
- References:
- [Wireshark-dev] Cmake and RPM
- From: Jonne Zutt
- Re: [Wireshark-dev] Cmake and RPM
- From: João Valverde
- Re: [Wireshark-dev] Cmake and RPM
- From: Jonne Zutt
- Re: [Wireshark-dev] Cmake and RPM
- From: João Valverde
- Re: [Wireshark-dev] Cmake and RPM
- From: Jonne Zutt
- Re: [Wireshark-dev] Cmake and RPM
- From: João Valverde
- Re: [Wireshark-dev] Cmake and RPM
- From: Jonne Zutt
- Re: [Wireshark-dev] Cmake and RPM
- From: João Valverde
- Re: [Wireshark-dev] Cmake and RPM
- From: Jonne Zutt
- Re: [Wireshark-dev] Cmake and RPM
- From: João Valverde
- Re: [Wireshark-dev] Cmake and RPM
- From: Jonne Zutt
- Re: [Wireshark-dev] Cmake and RPM
- From: João Valverde
- [Wireshark-dev] Cmake and RPM
- Prev by Date: Re: [Wireshark-dev] Cmake and RPM
- Next by Date: Re: [Wireshark-dev] Cmake and RPM
- Previous by thread: Re: [Wireshark-dev] Cmake and RPM
- Next by thread: Re: [Wireshark-dev] Cmake and RPM
- Index(es):