Posting this to report success
The `ninja -j1` suggestion made the difference. While it ran visibly slower
than the simple `ninja` command which defaults to parallel builds, `ninja -j1`
just kept working away steadily and finished all the remaining 294 steps
without any hesitation. I now
On Sep 12, 2018, at 5:07 PM, Geoff Lee wrote:
> As explained in Guy Harris's most recent and very illuminating post,
> (almost) all of the "error" messages were in fact part of the CMake process,
> for probing my gcc compiler to see what features and options it supports.
Probing the compiler *an
On 13/09/18 01:07, Geoff Lee wrote:
Many thanks indeed to everyone who posted answers to help me! Much
appreciated.
(And apologies if this fails to attach to the thread properly - I foolishly
set the daily digest option when I subscribed to the list, and can't figure
out how to respond prope
Many thanks indeed to everyone who posted answers to help me! Much
appreciated.
(And apologies if this fails to attach to the thread properly - I foolishly
set the daily digest option when I subscribed to the list, and can't figure
out how to respond properly to individual messages. I've fixed t
On Sep 11, 2018, at 5:11 PM, Richard Sharpe wrote:
> Hmmm, now that I have looked at your CMakeError.log, it looks like
> maybe you need a newer version of cmake.
The only things I'm seeing in CMakeError.log are:
indications that the compiler doesn't support certain warning flags;
On Sep 10, 2018, at 9:46 PM, Geoff Lee wrote:
> 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
As João said, what you do with them is *ignore* them.
CMake does a number of tests to determine, for example, whether certa
Hi Sean,
it will be better to create a bug on bug tracker https://bugs.wireshark.org
Cdlt
On Wed, Sep 12, 2018 at 2:02 AM Sean Hayden
wrote:
> MacOs 10.13.6
> WireShark 2.6.3 (and 2.6.2)
>
> When I start a remote SSH session, the UI/trackpad input becomes
> “locked”. The session is working a
