Re: [Wireshark-commits] buildbot failure in Wireshark (development) on Visual-Studio-Code-Analysis

[Ed Beroset <beroset () mindspring com>]

Jeorg, 

> eax.c(32) : fatal error C1083: Cannot open include file: 'gcrypt.h': No such file or directory

> Ideas anyone?

I see you already found and fixed the problem in version 40502.  I apologize for accidentally deleting that change from 
the patch I submitted, Joerg.  Thanks for doing that.  

Also, there's a problem introduced by commenting out some of the code.  You noted that you made fixes for these:

[ 64%] Building C object epan/CMakeFiles/epan.dir/dissectors/packet-c1222.c.o            
../../asn1/c1222/packet-c1222-template.c: In function ‘dissect_epsem’:                   
../../asn1/c1222/packet-c1222-template.c:860:15: error: variable ‘ft’ set but not used [-Werror=unused-but-set-variable]

[  5%] Building C object epan/CMakeFiles/epan.dir/dissectors/packet-c1222.c.o
../../asn1/c1222/packet-c1222-template.c:103:19: error: ‘c1222_flags’ defined but not used [-Werror=unused-variable]

and I see the code you've commented out.  However, that also eliminates some functionality.  Specifically that causes 
autogenerated code to parse the flags.  With the code intact, we get this (an extract from tshark):

        user-information
            C12.22 EPSEM Flags: 0x88, C12.22 Reserved Flag, C12.22 Security Mode Flags: Ciphertext with authentication, 
C12.22 Response Control Flags: Always respond
                1... .... = C12.22 Reserved Flag: True
                .0.. .... = C12.22 Recovery Flag: False
                ..0. .... = C12.22 Proxy Service Used Flag: False
                ...0 .... = C12.22 ED Class Flag: False
                .... 10.. = C12.22 Security Mode Flags: Ciphertext with authentication (0x02)
                .... ..00 = C12.22 Response Control Flags: Always respond (0x00)
            C12.22 EPSEM: OK
                C12.22 Response: OK (0x00)

Without the code, we get this:

        user-information
            C12.22 EPSEM: OK
                C12.22 Response: OK (0x00)

I don't seem to get the same warning using MSC2008EE here.  There must be some way to eliminate the warning without 
sacrificing the feature.  Can you tell me how you got those warnings?  I may be able to help.

Ed
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe