Re: wireshark 2.2.x build fail
On 10/16/16 18:56, Michael Butler wrote: On 10/16/16 11:36, Joe Marcus Clarke wrote: Seems like the easy fix would be to incorporate the fix for this bug, and then disable SSE4.2 in a CFLAGS override. The better fix would be to have clang do the same as GCC so that the test build would fail on those platforms that don't support SSE4.2. Personally, I feel that this whole approach is wrong. To have CONFIGURE set a flag asking for instructions not supported by the host for the whole project when only one module has a run-time check for them is depending on undefined behavior. This is plainly poor engineering. It so happens that GCC does the expected thing but there is no guarantee that any other compiler can or should. In CLANG's case, it found an opportunity to use an SSE-4.2 instruction in compiling LEMON and assumed it could use it as CONFIGURE told it explicitly that it could. "fixing" every compiler out there to be GCC-compatible is not an acceptable or desirable work-around. The option should only be set for the module prepared for and capable of handling the absence of the extended instructions, Sure. I think the better case is to do a runtime check of a binary built with this instruction set versus just a compiler check. Seems like the compiler check is what WS is settling on, though. Will any stub executable built with these instructions fail, or is there a specific call that needs to be made to test this? I imagine the latter. Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: wireshark 2.2.x build fail
On 10/16/16 11:36, Joe Marcus Clarke wrote: Seems like the easy fix would be to incorporate the fix for this bug, and then disable SSE4.2 in a CFLAGS override. The better fix would be to have clang do the same as GCC so that the test build would fail on those platforms that don't support SSE4.2. Personally, I feel that this whole approach is wrong. To have CONFIGURE set a flag asking for instructions not supported by the host for the whole project when only one module has a run-time check for them is depending on undefined behavior. This is plainly poor engineering. It so happens that GCC does the expected thing but there is no guarantee that any other compiler can or should. In CLANG's case, it found an opportunity to use an SSE-4.2 instruction in compiling LEMON and assumed it could use it as CONFIGURE told it explicitly that it could. "fixing" every compiler out there to be GCC-compatible is not an acceptable or desirable work-around. The option should only be set for the module prepared for and capable of handling the absence of the extended instructions, Michael ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: wireshark 2.2.x build fail
On 10/15/16 21:06, Michael Butler wrote: Just a "heads up": wireshark 2.2.x introduces the compiler flag "-msse4.2" via 'configure' if the compiler accepts that flag. The capability, or otherwise, of the host machine is ignored as it is expected that the one module in which GCC will use these instructions has a run-time check. This does not work for CLANG on "deficient" hardware; LEMON (part of the build tool-chain) will also be compiled with these extended instructions and cause exceptions on hardware that doesn't support them :-( There's a related discussion on the wireshark-bugs list referring to "bug 10792" Seems like the easy fix would be to incorporate the fix for this bug, and then disable SSE4.2 in a CFLAGS override. The better fix would be to have clang do the same as GCC so that the test build would fail on those platforms that don't support SSE4.2. Joe Michael -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Wireshark - error while building from source
On Mon, Oct 27, 2014 at 4:22 AM, Ewald Jenisch wrote: > Hi, > > I'm trying to get wireshark working unter 9.3 (x64, kernel/system > current as of last week) without success so far. > > I went to /usr/ports/net/wireshark ran make and here's what I ended up > with: > > -- < Cut here > -- > > . > . > . > > CC libdissectors_la-packet-logotypecertextn.lo > ../../asn1/kerberos/packet-kerberos-template.c: In function > 'read_keytab_file': > ../../asn1/kerberos/packet-kerberos-template.c:470: warning: request for > implicit conversion from 'gpointer' to 'struct enc_key_t *' not permitted > in C++ > ../../asn1/kerberos/packet-kerberos-template.c:482: error: > 'krb5_principal_data' has no member named 'name' > ../../asn1/kerberos/packet-kerberos-template.c:483: error: > 'krb5_principal_data' has no member named 'name' > ../../asn1/kerberos/packet-kerberos-template.c:483: error: > 'krb5_principal_data' has no member named 'name' > ../../asn1/kerberos/packet-kerberos-template.c:486: warning: format '%s' > expects type 'char *', but argument 4 has type 'krb5_data' > ../../asn1/kerberos/packet-kerberos-template.c:486: warning: format '%s' > expects type 'char *', but argument 4 has type 'krb5_data' > ../../asn1/kerberos/packet-kerberos-template.c:489: error: > 'krb5_keytab_entry' has no member named 'keyblock' > ../../asn1/kerberos/packet-kerberos-template.c:490: error: > 'krb5_keytab_entry' has no member named 'keyblock' > ../../asn1/kerberos/packet-kerberos-template.c:491: error: > 'krb5_keytab_entry' has no member named 'keyblock' > ../../asn1/kerberos/packet-kerberos-template.c:491: error: > 'krb5_keytab_entry' has no member named 'keyblock' > ../../asn1/kerberos/packet-kerberos-template.c:491: warning: request for > implicit conversion from 'gpointer' to 'char *' not permitted in C++ > ../../asn1/kerberos/packet-kerberos-template.c: In function > 'decrypt_krb5_data': > ../../asn1/kerberos/packet-kerberos-template.c:531: error: 'krb5_crypto' > undeclared (first use in this function) > ../../asn1/kerberos/packet-kerberos-template.c:531: error: (Each > undeclared identifier is reported only once > ../../asn1/kerberos/packet-kerberos-template.c:531: error: for each > function it appears in.) > ../../asn1/kerberos/packet-kerberos-template.c:531: error: expected ';' > before 'crypto' > ../../asn1/kerberos/packet-kerberos-template.c:532: warning: ISO C90 > forbids mixed declarations and code > ../../asn1/kerberos/packet-kerberos-template.c:539: error: > 'krb5_keytab_entry' has no member named 'keyblock' > ../../asn1/kerberos/packet-kerberos-template.c:540: error: > 'krb5_keytab_entry' has no member named 'keyblock' > ../../asn1/kerberos/packet-kerberos-template.c:541: error: > 'krb5_keytab_entry' has no member named 'keyblock' > ../../asn1/kerberos/packet-kerberos-template.c:542: warning: implicit > declaration of function 'krb5_crypto_init' > ../../asn1/kerberos/packet-kerberos-template.c:542: error: > 'krb5_keytab_entry' has no member named 'keyblock' > ../../asn1/kerberos/packet-kerberos-template.c:542: error: 'crypto' > undeclared (first use in this function) > ../../asn1/kerberos/packet-kerberos-template.c:553: warning: request for > implicit conversion from 'gpointer' to 'guint8 *' not permitted in C++ > ../../asn1/kerberos/packet-kerberos-template.c:554: warning: implicit > declaration of function 'krb5_decrypt_ivec' > ../../asn1/kerberos/packet-kerberos-template.c:564: warning: implicit > declaration of function 'krb5_crypto_destroy' > ../../asn1/kerberos/packet-kerberos-template.c:566: warning: request for > implicit conversion from 'gpointer' to 'char *' not permitted in C++ > Makefile:12591: recipe for target 'libdissectors_la-packet-kerberos.lo' > failed > gmake[5]: *** [libdissectors_la-packet-kerberos.lo] Error 1 > CC libdissectors_la-packet-lpp.lo > gmake[5]: *** Waiting for unfinished jobs > gmake[5]: Leaving directory > '/usr/ports/net/wireshark/work/wireshark-1.12.1/epan/dissectors' > Makefile:13170: recipe for target 'all-recursive' failed > gmake[4]: *** [all-recursive] Error 1 > gmake[4]: Leaving directory > '/usr/ports/net/wireshark/work/wireshark-1.12.1/epan/dissectors' > Makefile:3443: recipe for target 'all' failed > gmake[3]: *** [all] Error 2 > gmake[3]: Leaving directory > '/usr/ports/net/wireshark/work/wireshark-1.12.1/epan/dissectors' > Makefile:1906: recipe for target 'all-recursive' failed > gmake[2]: *** [all-recursive] Error 1 > gmake[2]: Leaving directory > '/usr/ports/net/wireshark/work/wireshark-1.12.1/epan' > Makefile:3970: recipe for target 'all-recursive' failed > gmake[1]: *** [all-recursive] Error 1 > gmake[1]: Leaving directory > '/usr/ports/net/wireshark/work/wireshark-1.12.1' > Makefile:2106: recipe for target 'all' failed > gmake: *** [all] Error 2 > ===> Compilation failed unexpectedly. > Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to > the maintainer. > *** [do-build] E
Re: wireshark
On Sat, Aug 18, 2012 at 06:31:26PM -0700, Doug Barton wrote: > I can't update wireshark to the latest version in ports due to the > portaudit warning. > > Meanwhile, I just tried 1.8.2 and it seems like a simple version > upgrade. The result builds and runs just fine, plist looks good, etc. I can vouche for this as well. Been running this since it was announced. Only one thing to consider. When opening a large packet dump with certain options like GeoIP & SNMP MIB turned on from a previous version you may find that wireshark crashes depening upon the captured data. Workaround is to move your .wireshark directory over and migrate any files back that are neccesary to your SOP which is fairly trivial. After that it will continue to operate as expected without flaw. > > Any chance of getting this in soon'ish? Or do I have your permission to > do the version upgrade? > -- - (2^(N-1)) JJH48-ARIN pgpmzmbW4tZyP.pgp Description: PGP signature
Re: wireshark build problem...
Peter Pentchev writes: > Errr, did you actually try with "-0" and "-02"? The gcc flags > ought to be "-O" and "-O2" - that's the letter "O", not the digit > "0"... Yes. Typo mine. Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: wireshark build problem...
On Fri, Feb 23, 2007 at 09:57:19AM -0500, Robert Huff wrote: > Eric Schuele writes: > > > On 02/21/2007 19:50, George W. Dinolt wrote: > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/108776 > > > > > > Unfortunately, the PR is "closed" because it is "not reproducible". At > > > > Quite reproducible on my machine. :/ > > And mine, with both "-0" and "-02". Errr, did you actually try with "-0" and "-02"? The gcc flags ought to be "-O" and "-O2" - that's the letter "O", not the digit "0"... G'luck, Peter -- Peter Pentchev [EMAIL PROTECTED][EMAIL PROTECTED][EMAIL PROTECTED] PGP key:http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 If this sentence didn't exist, somebody would have invented it. pgpZlBaSqwG7I.pgp Description: PGP signature
Re: wireshark build problem...
Eric Schuele writes: > On 02/21/2007 19:50, George W. Dinolt wrote: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/108776 > > > > Unfortunately, the PR is "closed" because it is "not reproducible". At > > Quite reproducible on my machine. :/ And mine, with both "-0" and "-02". If someone cares to re-open the PR, I have logs for both attempts. Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: wireshark build problem...
On 02/21/2007 19:50, George W. Dinolt wrote: Eric: I too saw the same problem on both 6.2 and current. If one searches the PR's one can find a reference to this problem. http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/108776 Unfortunately, the PR is "closed" because it is "not reproducible". At Quite reproducible on my machine. :/ the bottom of the PR I found the following information: "I rebuild net-snmp with "-O2" optimization and then build wireshark with "-O2" or "-O", and both succeeded." Odd that it is suggested to work with greater optimizations. I'll give it a shot first chance I get. Thanks. I did this with "-O2" and both net-snmp and wireshare 0.99.5 built without errors and wireshark seems to work. I hope this helps. G. Dinolt. Hello Eric, On Wed, 21 Feb 2007, Eric Schuele wrote: Hello, =20 Anyone seeing the following while building the latest wireshark?=20 Yep. See: http://www.freebsd.org/cgi/query-pr.cgi?pr=3D108892 Can't say much for the responses though :-/ Regards, Stacey Previously had it installed, this was just a portupgrade from: =20 wireshark-0.99.4_1 < needs updating (port has 0.99.5) =20 -Wl,/usr/local/lib -Wl,--rpath -Wl,/usr/X11R6/lib epan/.libs/libwireshark.so: undefined reference to `.LC831' epan/.libs/libwireshark.so: undefined reference to `.LC834' epan/.libs/libwireshark.so: undefined reference to `.LC830' epan/.libs/libwireshark.so: undefined reference to `.LC832' epan/.libs/libwireshark.so: undefined reference to `.LC835' epan/.libs/libwireshark.so: undefined reference to `.LC833' epan/.libs/libwireshark.so: undefined reference to `.LC829' gmake[2]: *** [wireshark] Error 1 gmake[2]: Leaving directory `/usr/ports/net/wireshark/work/wireshark-0.99= .5' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/net/wireshark/work/wireshark-0.99= .5' gmake: *** [all] Error 2 *** Error code 2 =20 If so... any workarounds? =20 --=20 Regards, Eric ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- Regards, Eric ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: wireshark build problem...
Eric: I too saw the same problem on both 6.2 and current. If one searches the PR's one can find a reference to this problem. http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/108776 Unfortunately, the PR is "closed" because it is "not reproducible". At the bottom of the PR I found the following information: > "I rebuild net-snmp with "-O2" optimization and then build wireshark > with "-O2" or "-O", and both succeeded." I did this with "-O2" and both net-snmp and wireshare 0.99.5 built without errors and wireshark seems to work. I hope this helps. G. Dinolt. > Hello Eric, > > On Wed, 21 Feb 2007, Eric Schuele wrote: > > > Hello, > >=20 > > Anyone seeing the following while building the latest wireshark?=20 > > Yep. See: http://www.freebsd.org/cgi/query-pr.cgi?pr=3D108892 > > Can't say much for the responses though :-/ > > Regards, > > Stacey > > > Previously had it installed, this was just a portupgrade from: > >=20 > > wireshark-0.99.4_1 < needs updating (port has 0.99.5) > >=20 > > -Wl,/usr/local/lib -Wl,--rpath -Wl,/usr/X11R6/lib > > epan/.libs/libwireshark.so: undefined reference to `.LC831' > > epan/.libs/libwireshark.so: undefined reference to `.LC834' > > epan/.libs/libwireshark.so: undefined reference to `.LC830' > > epan/.libs/libwireshark.so: undefined reference to `.LC832' > > epan/.libs/libwireshark.so: undefined reference to `.LC835' > > epan/.libs/libwireshark.so: undefined reference to `.LC833' > > epan/.libs/libwireshark.so: undefined reference to `.LC829' > > gmake[2]: *** [wireshark] Error 1 > > gmake[2]: Leaving directory `/usr/ports/net/wireshark/work/wireshark-0.99= > .5' > > gmake[1]: *** [all-recursive] Error 1 > > gmake[1]: Leaving directory `/usr/ports/net/wireshark/work/wireshark-0.99= > .5' > > gmake: *** [all] Error 2 > > *** Error code 2 > >=20 > > If so... any workarounds? > >=20 > > --=20 > > Regards, > > Eric > > ___ > > freebsd-ports@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: wireshark build problem....
Hello Eric, On Wed, 21 Feb 2007, Eric Schuele wrote: > Hello, > > Anyone seeing the following while building the latest wireshark? Yep. See: http://www.freebsd.org/cgi/query-pr.cgi?pr=108892 Can't say much for the responses though :-/ Regards, Stacey > Previously had it installed, this was just a portupgrade from: > > wireshark-0.99.4_1 < needs updating (port has 0.99.5) > > -Wl,/usr/local/lib -Wl,--rpath -Wl,/usr/X11R6/lib > epan/.libs/libwireshark.so: undefined reference to `.LC831' > epan/.libs/libwireshark.so: undefined reference to `.LC834' > epan/.libs/libwireshark.so: undefined reference to `.LC830' > epan/.libs/libwireshark.so: undefined reference to `.LC832' > epan/.libs/libwireshark.so: undefined reference to `.LC835' > epan/.libs/libwireshark.so: undefined reference to `.LC833' > epan/.libs/libwireshark.so: undefined reference to `.LC829' > gmake[2]: *** [wireshark] Error 1 > gmake[2]: Leaving directory `/usr/ports/net/wireshark/work/wireshark-0.99.5' > gmake[1]: *** [all-recursive] Error 1 > gmake[1]: Leaving directory `/usr/ports/net/wireshark/work/wireshark-0.99.5' > gmake: *** [all] Error 2 > *** Error code 2 > > If so... any workarounds? > > -- > Regards, > Eric > ___ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "[EMAIL PROTECTED]" pgp9f44rbta4Q.pgp Description: PGP signature
