Hi,
Thus wrote Gerald Combs (ger...@wireshark.org):
> On 2/21/13 12:47 AM, Martin Kaiser wrote:
> > If that's too error-prone as people may include gcrypt.h elsewhere in
> > the future and forget to add the pragmas, we could have a wrapper
> > include file (epan/crypt/ws-libgcrypt.h ?) with the 4
On 2/21/13 12:47 AM, Martin Kaiser wrote:
> If that's too error-prone as people may include gcrypt.h elsewhere in
> the future and forget to add the pragmas, we could have a wrapper
> include file (epan/crypt/ws-libgcrypt.h ?) with the 4 lines above and
> include that instead of gcrypt.h.
Sounds g
Hello,
I am currently working on a protocol stack which is not fully standardized and
still under development.
The Protocol stack is: Ethernet > ProtocolA > ProtocolB,C or D
My Problem is There are multiple Versions of Protocol A and multiple Dissectors
for Protocol A.
I since my focus is on the
2013/2/21 Martin Kaiser
> Dear all,
>
> this issue has been around for a long time. When we use libgcrypt 1.5.0,
> including gcrypt.h spills out lots of warnings about deprecated
> definitions, breaking compilation with -Werror.
>
> Steven Fisher asked about this on the libgcrypt list
>
>
> http:
Dear all,
this issue has been around for a long time. When we use libgcrypt 1.5.0,
including gcrypt.h spills out lots of warnings about deprecated
definitions, breaking compilation with -Werror.
Steven Fisher asked about this on the libgcrypt list
http://old.nabble.com/Re%3A-Problem-with-warning
Anyone able to create a checkett.pl script to check for this?
Note that checkAPI.pl contains code to check etts, but it is currently
disabled, because it generates lots of false positives. I've written a
naive approach to also check for etts (see attachment), but using it
with the dissector s
