build directory
> $ rm -rf * && cmake -G Ninja .. && ninja
> [ build fails ]
>
> $ sudo xcode-select --switch /Library/Developer/CommandLineTools
> $ xcode-select --print-path
> /Library/Developer/CommandLineTools
>
> $ rm -rf * && cmake -G Ninja .. &
On Fri, Apr 24, 2020 at 6:27 PM Graham Bloice
wrote:
>
>
> On Fri, 24 Apr 2020 at 17:22, Lori Jakab wrote:
>
>> On Fri, Apr 24, 2020 at 6:06 PM Graham Bloice <
>> graham.blo...@trihedral.com> wrote:
>>
>>> The macOS build slave is coping,
I attached my cmake output, in case that helps.
-Lori
On Fri, Apr 24, 2020 at 6:21 PM Lori Jakab wrote:
> On Fri, Apr 24, 2020 at 6:06 PM Graham Bloice
> wrote:
>
>> The macOS build slave is coping, according to the CMake output it's using:
>>
>> -- The C compi
build; and cd build; and cmake -G Ninja
../wireshark; and time ninja -j 10
I wonder what's different from the build slave that breaks the build...
-Lori
>
> On Fri, 24 Apr 2020 at 15:48, Lori Jakab wrote:
>
>> This particular failure can be fixed by this:
>> https:
nd d30a0a2ce7c17f5d695e9ee7647e92d3cc1156bb.
>
> On Fri, Apr 24, 2020 at 3:29 PM Lori Jakab wrote:
>
>> Hi,
>>
>> I'm have been building on macOS Mojave for a while without issues, but
>> for the last few days the build has been broken. I didn't try a g
Hi,
I'm have been building on macOS Mojave for a while without issues, but for
the last few days the build has been broken. I didn't try a git dissect yet
to see which commit broke it, but the issue seems to be caused by the usage
of the _Nonnull, _Nullable, or _Null_unspecified type specifiers in
On Thu, Mar 21, 2019 at 3:15 PM Stig Bjørlykke wrote:
>
> On Thu, Mar 21, 2019 at 3:09 PM Lori Jakab wrote:
> > Did anyone manage to build a dark mode enabled version successfully?
>
> Dark mode was disabled in 81c4f74a1921e8c89fcf200beb6892b78a7297d9
>
> Remove this
options.
Did anyone manage to build a dark mode enabled version successfully?
Thanks,
-Lori
>
> Anyone got an idea, which SDK version we are using?
>
> regards
> Roland
>
> Am Do., 21. März 2019 um 09:43 Uhr schrieb Lori Jakab
> :
>>
>> Hi,
>>
>> I
Hi,
I'm on macOS Mojave using dark mode, and my understanding was that
Wireshark 3 does support it. Is there anything that needs to be done
to activate it? For me it still shows up with light color palette.
About:
Version 3.0.0 (v3.0.0-0-g937e33de)
Copyright 1998-2019 Gerald Combs and
contribu
Hi,
I'm running on macOS High Sierra 10.13.5 with Xcode 9.4.1 + Command Line
Tools and using Homebrew for installing most open source packages (like
Qt5). I would say this is a pretty common developer setup on macOS. I can
build the Wireshark binaries with this setup and they run fine. However, I
On 01/15/2014 04:28 AM, Evan Huus wrote:
> I have created an account and added an SSH key, but I am getting
> "Permission denied (publickey)" when trying to clone. Is it working
> for anyone else?
I just checked the SSH and HTTPS methods with username and they both
worked for me.
-Lori
>
> On Tu
On 05/02/2013 05:49 PM, Alexis La Goutte wrote:
> On Thu, May 2, 2013 at 4:41 PM, Anders Broman
> mailto:anders.bro...@ericsson.com>> wrote:
>
> Hi,
> Disclaimer: Without looking at the code.
>
> +1
>
>
> Couldn't the "LISO Data" dissector check the destination port and
> call LIS
Hi,
There is a special "LISP Control" packet type, where the UDP source port is the
one registered for "LISP Data" and the UDP destination port is "LISP Control"
(4341 and 4342 respectively). Wireshark dissects this packet as "LISP Data"
which leads to incorrect dissection. While "LISP Contro
On 04/12/2013 01:19 AM, Gerald Combs wrote:
> The git repository is a bit of a second-class citizen because our
> SVN→git mirroring is unidirectional. Commits must be done using
> Subversion. I'm considering switching from our current software
> (svn-all-fast-export) to SubGit (http://subgit.com/)
On 08/23/12 05:52, Pascal Quantin wrote:
> 2012/8/19 Lori Jakab mailto:l...@lispmob.org>>
>
> On 08/19/12 06:56, Pascal Quantin wrote:
> > Having a RSS link (or something similar) to the subversion file log
> >
>
> (http://anonsvn.wireshark.org/vi
SS feed would fulfill
this. And they are not mutually exclusive either. RSS would allow
interested non-authors as well to easily follow changes, while the
maintainer option could be integrated with bugzilla so that authors are
automatically CC'ed on patches submitted for files they maint
On 03/13/12 23:07, Martin Kaiser wrote:
> Hi Lori and all,
>
> Thus wrote Lori Jakab (lja...@ac.upc.edu):
>
>> AFAIK, currently the protocol displayed in the Protocol column of
>> Wireshark is that of the last dissector called on the packet. This makes
>> it difficul
menting
this be accepted? Would someone mentor work on such a patch?
Thanks,
-Lori Jakab
author of the LISP dissector
___
Sent via:Wireshark-dev mailing list
Archives:http://www.wireshark.org/lists/wireshark-dev
Uns
18 matches
Mail list logo
