This is a static archive of our old Q&A Site. Please post any new questions and answers at ask.wireshark.org.

Help to look at my reject file produced by installing wireshark under FreeBSD ports!

0

I tried to install the wireshark under my FreeBSD ports, it failed and get the reject file, I want to know what the reject file mean, Does anyone of you can tell me that? Thank you!

[[email protected] /usr/ports/net/wireshark]# make install clean

===> Found saved configuration for wireshark-0.99.7

=> MD5 Checksum OK for wireshark-0.99.7.tar.bz2. => SHA256 Checksum OK for wireshark-0.99.7.tar.bz2. ===> wireshark-0.99.7 depends on file: /usr/local/bin/perl5.8.8 - found ===> Patching for wireshark-0.99.7 ===> wireshark-0.99.7 depends on file: /usr/local/bin/perl5.8.8 - found ===> Applying FreeBSD patches for wireshark-0.99.7 1 out of 1 hunks failed--saving rejects to epan/dissectors/packet-diameter.c.rej => Patch patch-epan_dissectors_packet-diameter.c failed to apply cleanly. => Patch(es) patch-Makefile.in patch-configure patch-epan_Makefile.in applied cleanly. *** Error code 1

Stop in /usr/ports/net/wireshark. *** Error code 1

Stop in /usr/ports/net/wireshark. [[email protected] /usr/ports/net/wireshark]# cat work/wireshark-0.99.7/epan/dissectors/packet-diameter.c.rej 2022,2034 * { "Flags", "diameter.flags", FT_UINT8, BASE_HEX, NULL, 0x0, "", HFILL }}, { &hf_diameter_flags_request, - { "Request", "diameter.flags.request", FT_BOOLEAN, 8, TFS(&flags_set_truth), DIAM_FLAGS_R, "", HFILL }}, { &hf_diameter_flags_proxyable, - { "Proxyable", "diameter.flags.proxyable", FT_BOOLEAN, 8, TFS(&flags_set_truth), DIAM_FLAGS_P, "", HFILL }}, { &hf_diameter_flags_error, - { "Error","diameter.flags.error", FT_BOOLEAN, 8, TFS(&flags_set_truth), DIAM_FLAGS_E, "", HFILL }}, { &hf_diameter_flags_T, { "T(Potentially re-transmitted message)","diameter.flags.T", FT_BOOLEAN, 8, TFS(&flags_set_truth),DIAM_FLAGS_T, --- 2022,2034 ---- { "Flags", "diameter.flags", FT_UINT8, BASE_HEX, NULL, 0x0, "", HFILL }}, { &hf_diameter_flags_request, + { "Request ", "diameter.flags.request", FT_BOOLEAN, 8, TFS(&flags_set_truth), DIAM_FLAGS_R, "", HFILL }}, { &hf_diameter_flags_proxyable, + { "Proxyable ", "diameter.flags.proxyable", FT_BOOLEAN, 8, TFS(&flags_set_truth), DIAM_FLAGS_P, "", HFILL }}, { &hf_diameter_flags_error, + { "Error ","diameter.flags.error", FT_BOOLEAN, 8, TFS(&flags_set_truth), DIAM_FLAGS_E, "", HFILL }}, { &hf_diameter_flags_T, { "T(Potentially re-transmitted message)","diameter.flags.T", FT_BOOLEAN, 8, TFS(&flags_set_truth),DIAM_FLAGS_T, [[email protected] /usr/ports/net/wireshark]#

asked 02 Nov '11, 00:39

candyli's gravatar image

candyli
1111
accept rate: 0%

Version 0.99.7 is very old and no longer supported. I suggest trying to install a more modern version of Wireshark which you can find at the download page.

(02 Nov '11, 18:07) cmaynard ♦♦

One Answer:

1

This is an issue of the FreeBSD port system, not Wireshark; the FreeBSD port maintainers maintain the ports.

As Using the Ports Collection says, "Warning: Before installing any port, you should be sure to have an up-to-date Ports Collection and you should check http://vuxml.freebsd.org/ for security issues related to your port." Make sure your Ports Collection is up to date - as Chris Maynard notes, Wireshark 0.99.7 is a very old release.

You might want to check out the freebsd-questions mailing list.

answered 03 Nov '11, 18:25

Guy%20Harris's gravatar image

Guy Harris ♦♦
17.4k335196
accept rate: 19%