Hello,
(1) building Wireshark in build.wireshark fails
The solution here is to use "build" as the name of the build directory and
then make succeeds. Otherwise, if the build directory has some other name
like build.wireshark then make fails at about 70% when building qtui.
Why do I want to name
On Apr 15, 2021, at 12:55 AM, Vincent Randal wrote:
> (1) building Wireshark in build.wireshark fails
> The solution here is to use "build" as the name of the build directory and
> then make succeeds. Otherwise, if the build directory has some other name
> like build.wireshark then make fails
(1) There is no error message other than it fails immediately when
beginning building "qtui" (at about 70% of the way into make for
wireshark-3.4.4)
(2) Good point. Wireshark uses dissectors to provide details of packets, as
you point out. So then the dissector source code provides the details of
t
Hi Vincent,
Le jeu. 15 avr. 2021 à 10:52, Vincent Randal a écrit :
> (1) There is no error message other than it fails immediately when
> beginning building "qtui" (at about 70% of the way into make for
> wireshark-3.4.4)
>
You should have an error message, please check above in the build log.
Wireshark is a complicated project to build. You can follow the tested
way, as shown in the Developers Guide, which is essentially what our
Continuous Integration (CI) systems use and most other developers, or you
can forge your own path on less travelled routes strewn with rocks, rusty
nails and
Hi Pascal,
Where is the build log? I've since rebuilt Wireshark successfully in
./build as Graham wisely suggests. This thing is not easy to reproduce.
There may be something unstable about my build environment on Ubuntu 18.04
if that even makes sense. What I do have is the build output to the
ter
On Apr 15, 2021, at 8:10 AM, Vincent Randal wrote:
> Where is the build log?
In the file to which you redirected the standard output and error of the make
command - or the file created by tee, if piped the standard output and error of
the make command to "tee errs" so that the errors are print
On Apr 15, 2021, at 2:03 AM, Graham Bloice wrote:
> Wireshark is a complicated project to build. You can follow the tested way,
> as shown in the Developers Guide, which is essentially what our Continuous
> Integration (CI) systems use and most other developers, or you can forge your
> own pa
On Thu, 15 Apr 2021 at 21:23, Guy Harris wrote:
> On Apr 15, 2021, at 2:03 AM, Graham Bloice
> wrote:
>
> > Wireshark is a complicated project to build. You can follow the tested
> way, as shown in the Developers Guide, which is essentially what our
> Continuous Integration (CI) systems use and
Hi Pascal, Guy, and numerous others,
I managed to save my terminal window contents. It's over 1MB compressed. If
I cannot reproduce the problem I will look through that.
Thank you,
Vincent
On Thu, Apr 15, 2021 at 9:10 AM Vincent Randal wrote:
> Hi Pascal,
>
> Where is the build log? I've since
On Apr 15, 2021, at 3:46 PM, Vincent Randal wrote:
> I managed to save my terminal window contents. It's over 1MB compressed.
$ mkdir build.wireshark
$ cd build.wireshark
$ cmake .. >cmake.out 2>&1
$ make -j 16 >errs 2>&1
$ ls -lh cmake.out errs
-r
On Thu, Apr 15, 2021 at 1:23 PM Guy Harris wrote:
>
> On Apr 15, 2021, at 2:03 AM, Graham Bloice
> wrote:
>
> > Wireshark is a complicated project to build. You can follow the tested
> > way, as shown in the Developers Guide, which is essentially what our
> > Continuous Integration (CI) syste
12 matches
Mail list logo
