mailing list archives
Re: Build instability
From: Hauke Mehrtens <hauke () hauke-m de>
Date: Sun, 08 Dec 2013 17:51:46 +0100
On 12/08/2013 04:30 PM, Kaul wrote:
I've been trying to enhance a specific dissector for two weeks now.
Since I'm afraid of diverging the code (although I'm working on a
specific dissector), I update my code base often (~ once a day).
Regretfully, 5 times (in 2 weeks!) this has resulted in compilation failure.
I'm pretty sure (subjectively) this hasn't happened in the past. Any
measures we can put (continuous build system?) in place to prevent this?
Today's failure (2nd failure only today btw):
make: Entering directory `/home/yanivk/wireshark/epan/dissectors'
packet-ssl-utils.c: In function 'ssl_keylog_parse_session_id':
packet-ssl-utils.c:4201:9: error: implicit declaration of function
if (from_hex_char(line[2*i]) !=
(ssl_session->session_id.data[i] >> 4) ||
packet-ssl-utils.c:4218:5: error: implicit declaration of function
if (!from_hex(&ssl_session->master_secret, line, len))
cc1: all warnings being treated as errors
make: *** [libdissectors_la-packet-ssl-utils.lo] Error 1
There are automated build, they are described here:
The last build results are here:
The problem you current have was already fixed in current trunk some
Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org>
mailto:wireshark-dev-request () wireshark org?subject=unsubscribe