Re: [Wireshark-dev] Face issues while installing wireshark on rhel 7

2018-02-13 Thread Richard Sharpe 
On Mon, Feb 12, 2018 at 10:22 PM, Aditya Tyagi
 wrote:
> Please find attached screenshot when i trying to configure wireshark on rhel
> 7..even when it is configured it gives error while that this qt function is
> protected or something...

Can't read it. You know there is an app on RHEL for taking a screen
shot, don't you? That way you don't have to worry about holding the
camera steady.

-- 
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] report from the bleeding edge (VS 2017)

2018-02-13 Thread Anders Broman 


-Original Message-
From: Wireshark-dev [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of 
Ed Beroset
Sent: den 9 februari 2018 17:52
To: wireshark-dev@wireshark.org
Subject: [Wireshark-dev] report from the bleeding edge (VS 2017)

On 04/24/2017 01:01 PM, Graham Bloice wrote:

> Who knows what will be in the next Visual Studio.  I haven't seen any 
> announcements, but as VS 2017 was only released just over a month ago 
> I don't expect any public announcements yet.
> 
> It's possible that future C++ language changes may force them to 
> change the ABI.

I have been working through building an installer package on and for
Win64 on Windows 10 using VS 2017 and NSIS 3.03, so I thought I'd send this 
report from the bleeding edge.

Cylance vs. Cygwin
==
"BLODA" is the Cygwin acronym for "Big List Of Dodgy Apps" and unfortunately, I 
have discovered another one, which is Cylance which is anti-malware software 
(despite both starting with "cy" they have no relationship).  For background on 
that, see https://cygwin.com/faq/faq.html#faq.using.bloda and 
https://cygwin.com/ml/cygwin/2017-04/msg00319.html

I have been able to work around this by getting my IT folks to whitelist the 
following cygwin executables:
xterm.exe
git.exe
perl.exe
python2.7.exe

That seems to have been sufficient (so far) to get Wireshark to compile (for 
building Wireshark, it's probably not necessary to have xterm.exe but I use 
xterm often and it annoyed me!). Although it's more of a Cygwin than a 
Wireshark issue, I mention it here in case anyone encounters this problem and 
does a search.

Specifying platform
===
I used this command for CMake:

cmake -DENABLE_CHM_GUIDES=on -G "Visual Studio 15 2017 Win64" ..

I found that I had to explicitly specify the platform when using msbuild.  For 
example, to build a Release version on my machine:

msbuild /m /p:Configuration=Release /p:Platform=x64 Wireshark.sln

I don't yet know enough about msbuild or sln files to troubleshoot much 
further, but that worked for me.

Results
===
I haven't yet done thorough testing, but the installer, Wireshark and Tshark 
all seem to be to working correctly.

Hope that helps.

Ed

For what it's worth I have been building and distributing for VS 2017 for 
almost a year on Win7
Cygwin and python set up as per developers guide from way back. 
I have the following batch script I run in my cmd window 
**
** Visual Studio 2017 Developer Command Prompt v15.5.6
** Copyright (c) 2017 Microsoft Corporation
**
[vcvarsall.bat] Environment initialized for: 'x64'

set CYGWIN=nodosfilewarning
set WIRESHARK_BASE_DIR=C:\Development
set QT5_BASE_DIR=C:\Qt\5.9.4\msvc2017_64
set WIRESHARK_TARGET_PLATFORM=win64
set PATH=path=%PATH%;C:\cygwin64\bin;C:\Program Files\CMake\bin;C:\Python27

Then
cmake -DENABLE_CHM_GUIDES=on -G "Visual Studio 15 Win64" ..\wireshark
and
msbuild /m /p:Configuration=RelWithDebInfo Wireshark.sln 2>&1 > log.txt

___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Face issues while installing wireshark on rhel 7

2018-02-13 Thread Dario Lombardo 
I wouldn't send a screenshot anyway. Just copy&paste the text.

On Tue, Feb 13, 2018 at 4:21 PM, Richard Sharpe  wrote:

> On Mon, Feb 12, 2018 at 10:22 PM, Aditya Tyagi
>  wrote:
> > Please find attached screenshot when i trying to configure wireshark on
> rhel
> > 7..even when it is configured it gives error while that this qt function
> is
> > protected or something...
>
> Can't read it. You know there is an app on RHEL for taking a screen
> shot, don't you? That way you don't have to worry about holding the
> camera steady.
>
> --
> Regards,
> Richard Sharpe
> (何以解憂？唯有杜康。--曹操)
> 
> ___
> Sent via:Wireshark-dev mailing list 
> Archives:https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
>  mailto:wireshark-dev-requ...@wireshark.org?subject=
> unsubscribe
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Face issues while installing wireshark on rhel 7

2018-02-13 Thread Peter Wu 
On Tue, Feb 13, 2018 at 11:52:56AM +0530, Aditya Tyagi wrote:
> Please find attached screenshot when i trying to configure wireshark on
> rhel 7..even when it is configured it gives error while that this qt
> function is protected or something...

As Dario said, please just copy and paste the output rather than sending
a picture.

I was able to build Wireshark v2.4.5rc0-35-g7cfff44 from the master-2.4
branch with no issues using CMake:

$ yum list -C installed cmake gcc qt-devel
Installed Packages
cmake.x86_64   2.8.12.2-2.el7   
@base
gcc.x86_64 4.8.5-16.el7_4.1 
@updates
qt-devel.x86_641:4.8.5-15.el7_4 
@updates

Where have you installed Qt from?
-- 
Kind regards,
Peter Wu
https://lekensteyn.nl
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

[Wireshark-dev] Names longer than 8 characters in manuf file

2018-02-13 Thread M. Justin 
I was looking through the Wireshark manufacturer database manuf

file and noticed that three of the vendor names were more than 8 characters
long:

00:07:99TippingPointTippingPoint Technologies, Inc.
00:10:00CableLabs
44:45:53Microsoft

I assume that that these should be truncated to 8 characters like every
other entry.

I see another instance of CableLabs which is abbreviated as "Cablelab", and
the other instances of Microsoft are abbreviated as "Microsof", so I'm
guessing that's the correct name for those.

70:B3:D5:BD:10:00/36CablelabCableLabs
00:03:FFMicrosofMicrosoft Corporation
00:0D:3AMicrosofMicrosoft Corp.
00:50:C2:00:30:00/36MicrosofMicrosoft
30:0D:43MicrosofMicrosoft Mobile Oy
30:59:B7MicrosofMicrosoft
DC:B4:C4MicrosofMicrosoft XCG
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Names longer than 8 characters in manuf file

2018-02-13 Thread Alexis La Goutte 
Hi Justin,

it is a known issue and it is fixed on next release (2.5.x)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3666

Cheers

On Tue, Feb 13, 2018 at 7:52 PM, M. Justin  wrote:

> I was looking through the Wireshark manufacturer database manuf
> 
> file and noticed that three of the vendor names were more than 8 characters
> long:
>
> 00:07:99TippingPointTippingPoint Technologies, Inc.
> 00:10:00CableLabs
> 44:45:53Microsoft
>
> I assume that that these should be truncated to 8 characters like every
> other entry.
>
> I see another instance of CableLabs which is abbreviated as "Cablelab",
> and the other instances of Microsoft are abbreviated as "Microsof", so I'm
> guessing that's the correct name for those.
>
> 70:B3:D5:BD:10:00/36CablelabCableLabs
> 00:03:FFMicrosofMicrosoft Corporation
> 00:0D:3AMicrosofMicrosoft Corp.
> 00:50:C2:00:30:00/36MicrosofMicrosoft
> 30:0D:43MicrosofMicrosoft Mobile Oy
> 30:59:B7MicrosofMicrosoft
> DC:B4:C4MicrosofMicrosoft XCG
>
>
>
> 
> ___
> Sent via:Wireshark-dev mailing list 
> Archives:https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
>  mailto:wireshark-dev-requ...@wireshark.org?subject=
> unsubscribe
>
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Face issues while installing wireshark on rhel 7

2018-02-13 Thread Jim Young 
On Tue, Feb 13, 2018 at 11:52:56AM +0530, Aditya Tyagi wrote:
> Please find attached screenshot when i trying to configure wireshark on
> rhel 7..even when it is configured it gives error while that this qt
> function is protected or something...

The error looks to be  ...



> Checking whether Qt works without -fPIC ... no

> Checking whether Qt works with -fPIC ... no

> configure: error: Couldn't compile Qt without -fPIC nor with -fPIC




On Tue, Feb 13, 2018 at 1:04 PM, Peter Wu  wrote:

> On Tue, Feb 13, 2018 at 11:52:56AM +0530, Aditya Tyagi wrote:
> > Please find attached screenshot when i trying to configure wireshark on
> > rhel 7..even when it is configured it gives error while that this qt
> > function is protected or something...
>
> As Dario said, please just copy and paste the output rather than sending
> a picture.
>
> I was able to build Wireshark v2.4.5rc0-35-g7cfff44 from the master-2.4
> branch with no issues using CMake:
>
> $ yum list -C installed cmake gcc qt-devel
> Installed Packages
> cmake.x86_64   2.8.12.2-2.el7
>  @base
> gcc.x86_64 4.8.5-16.el7_4.1
>  @updates
> qt-devel.x86_641:4.8.5-15.el7_4
>  @updates
>
> Where have you installed Qt from?
> --
> Kind regards,
> Peter Wu
> https://lekensteyn.nl
> 
> ___
> Sent via:Wireshark-dev mailing list 
> Archives:https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
>  mailto:wireshark-dev-requ...@wireshark.org?subject=
> unsubscribe
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] report from the bleeding edge (VS 2017)

2018-02-13 Thread Gerald Combs 
On 2/13/18 8:26 AM, Anders Broman wrote:
> 
> For what it's worth I have been building and distributing for VS 2017 for 
> almost a year on Win7
> Cygwin and python set up as per developers guide from way back. 
> I have the following batch script I run in my cmd window 
> **
> ** Visual Studio 2017 Developer Command Prompt v15.5.6
> ** Copyright (c) 2017 Microsoft Corporation
> **
> [vcvarsall.bat] Environment initialized for: 'x64'
> 
> set CYGWIN=nodosfilewarning
> set WIRESHARK_BASE_DIR=C:\Development
> set QT5_BASE_DIR=C:\Qt\5.9.4\msvc2017_64
> set WIRESHARK_TARGET_PLATFORM=win64
> set PATH=path=%PATH%;C:\cygwin64\bin;C:\Program Files\CMake\bin;C:\Python27
> 
> Then
> cmake -DENABLE_CHM_GUIDES=on -G "Visual Studio 15 Win64" ..\wireshark
> and
> msbuild /m /p:Configuration=RelWithDebInfo Wireshark.sln 2>&1 > log.txt

Is there any reason we shouldn't switch to VS 2017 before the 2.6 release?
It's installed on the main and PD Windows builders.
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] report from the bleeding edge (VS 2017)

2018-02-13 Thread Pascal Quantin 
Le 14 févr. 2018 02:24, "Gerald Combs"  a écrit :

On 2/13/18 8:26 AM, Anders Broman wrote:
>
> For what it's worth I have been building and distributing for VS 2017 for
almost a year on Win7
> Cygwin and python set up as per developers guide from way back.
> I have the following batch script I run in my cmd window
> **
> ** Visual Studio 2017 Developer Command Prompt v15.5.6
> ** Copyright (c) 2017 Microsoft Corporation
> **
> [vcvarsall.bat] Environment initialized for: 'x64'
>
> set CYGWIN=nodosfilewarning
> set WIRESHARK_BASE_DIR=C:\Development
> set QT5_BASE_DIR=C:\Qt\5.9.4\msvc2017_64
> set WIRESHARK_TARGET_PLATFORM=win64
> set PATH=path=%PATH%;C:\cygwin64\bin;C:\Program
Files\CMake\bin;C:\Python27
>
> Then
> cmake -DENABLE_CHM_GUIDES=on -G "Visual Studio 15 Win64" ..\wireshark
> and
> msbuild /m /p:Configuration=RelWithDebInfo Wireshark.sln 2>&1 > log.txt

Is there any reason we shouldn't switch to VS 2017 before the 2.6 release?
It's installed on the main and PD Windows builders.


The availability of a 32bits Qt package for MSVC2017? I would find it a bit
weird to use MSVC2015 for the x86 binary and MSVC2017 for the x64 one.
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] report from the bleeding edge (VS 2017)

2018-02-13 Thread Anders Broman 
Den 14 feb. 2018 6:58 fm skrev "Pascal Quantin" :



Le 14 févr. 2018 02:24, "Gerald Combs"  a écrit :

On 2/13/18 8:26 AM, Anders Broman wrote:
>
> For what it's worth I have been building and distributing for VS 2017 for
almost a year on Win7
> Cygwin and python set up as per developers guide from way back.
> I have the following batch script I run in my cmd window
> **
> ** Visual Studio 2017 Developer Command Prompt v15.5.6
> ** Copyright (c) 2017 Microsoft Corporation
> **
> [vcvarsall.bat] Environment initialized for: 'x64'
>
> set CYGWIN=nodosfilewarning
> set WIRESHARK_BASE_DIR=C:\Development
> set QT5_BASE_DIR=C:\Qt\5.9.4\msvc2017_64
> set WIRESHARK_TARGET_PLATFORM=win64
> set PATH=path=%PATH%;C:\cygwin64\bin;C:\Program
Files\CMake\bin;C:\Python27
>
> Then
> cmake -DENABLE_CHM_GUIDES=on -G "Visual Studio 15 Win64" ..\wireshark
> and
> msbuild /m /p:Configuration=RelWithDebInfo Wireshark.sln 2>&1 > log.txt

Is there any reason we shouldn't switch to VS 2017 before the 2.6 release?
It's installed on the main and PD Windows builders.


The availability of a 32bits Qt package for MSVC2017? I would find it a bit
weird to use MSVC2015 for the x86 binary and MSVC2017 for the x64 one.


Do we still need to build for 32 bits?


___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe