Wireshark-dev: Re: [Wireshark-dev] Pointers needed for building Wireshark 2.6.3 on a Raspberry
On 11/09/18 05:46, Geoff Lee wrote:
Hi,
I’m hoping you can give me some pointers about how to compile Wireshark
2.6.3 on a Raspberry Pi Model 3B, with Raspbian Stretch as the OS.
I have wireshark 2.2.6, installed via apt-get, but am experiencing a
problem which I have been told is solved in more uptodate versions of
wireshark. Unfortunately I haven’t been able to locate any later
versions compiled for the Raspberry Pi, which I understand uses an ARMv7
processor.
It’s my first time attempting a compile from source using CMake (I did
use make once about 5 years ago on another project – and that took me
about 2 months to get working L ). I’ve read a couple of CMake
tutorials, but there is rather a large gap between the basic “hello
world” examples, and really substantial project like wireshark!, on top
of which I know very little about C and C++.
I’ve been following the instructions from here
https://www.wireshark.org/docs/wsdg_html_chunked/ChSrcBuildFirstTime.html#_building_on_unix
I’ve also read
https://www.wireshark.org/docs/wsug_html_chunked/ChBuildInstallUnixBuild.html,
and
https://www.wireshark.org/docs/wsug_html_chunked/ChBuildInstallUnixTrouble.html
, as well as looked at the INSTALL file on
https://github.com/wireshark/wireshark
I **think** I’ve managed to install all the necessary tools and dev
packages needed (but can’t be sure).
My core problem is that I’m too new to Cmake to understand what **to
do** about the messages I’m seeing in CMakeError.log and CMakeOutput.log
(both attached to this email).
I’m hoping that my problem is basic enough that with a few pointers
about what to look at or learn about next, it can be solved.
Your email doesn't explain what you are actually trying to solve. Did
you complete the CMake step sucessfully? Errors in CMakeError.log are
normal and expected.
You just need CMake to configure and generate the build successfully.
For your chosen platform and wireshark version you can easily hit
dependency issues that can be difficult to resolve.
Many thanks in advance for any help you can give
Geoff
___________________________________________________________________________
Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives: https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
