Man pages for wireshark don't happen

2019-03-16 Thread bob prohaska
Just tried making net/wireshark on raspberry pi 2 11.2/stable. 

GUI failed in gtk5, but CLI version installed successfully.
Where does it put the man pages? 

man wireshark reports
No manual entry for wireshark
and the docs I could find seemed to talk about the GUI version.

Thanks,

bob prohaska
___
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"


wireshark won't build

2016-11-15 Thread tech-lists

Hello ports@,

I'm having problems building wireshark.

System runs freebsd-stable r308206 and ports is 426176.

/etc/make.conf looks like this:

DEFAULT_VERSIONS+=ssl=libressl-devel

make config has KRB_NONE selected, all other options are the defaults. 
Just in case, I also ran make rmconfig (before selecting KRB_NONE 
otherwise it selects kerebos support in base system and I don't have 
kerebos, so it complains. I also ran make rmconfig-recursive, and in 
/usr/src ran yes | make delete-old and yes | make delete-old-libs.


Yet it still doesn't build. It DOES build on a vanilla freebsd-CURRENT 
machine. That machine also has the same /etc/make.conf. I also tried 
MAKE_JOBS_UNSAFE as suggested. I'm stumped. Can anyone help please? Here 
is the output leading up to the failure.


mv -f $depbase.Tpo $depbase.Po
/bin/sh ../libtool  --tag=CC   --mode=link cc  -Wall -Wextra 
-Wendif-labels -Wpointer-arith -Wformat-security -fwrapv -Wvla -Waddress 
-Wattributes -Wdiv-by-zero -Wignored-qualifiers -Wpragmas 
-Wno-overlength-strings -Wno-long-long -Wheader-guard -Wc++-compat 
-Wdeclaration-after-statement -Wunused-const-variable -Wshadow 
-Wno-pointer-sign -Wold-style-definition -Wstrict-prototypes 
-Wshorten-64-to-32 -Qunused-arguments -fvisibility=hidden 
-Wc99-extensions -O2 -pipe  -funit-at-a-time -fstack-protector 
-fno-strict-aliasing -L/usr/local/lib -Wl,-rpath,/usr/local/lib 
-fstack-protector -o randpktdump randpktdump.o extcap-base.o 
../randpkt_core/librandpkt_core.a ../wiretap/libwiretap.la 
../wsutil/libwsutil.la -L/usr/local/lib -lgthread-2.0 
-Wl,--export-dynamic -lgmodule-2.0 -pthread -lglib-2.0 -lintl   -lz -lm 
-L/usr/local/lib
/bin/sh ../libtool  --tag=CC   --mode=link cc  -Wall -Wextra 
-Wendif-labels -Wpointer-arith -Wformat-security -fwrapv -Wvla -Waddress 
-Wattributes -Wdiv-by-zero -Wignored-qualifiers -Wpragmas 
-Wno-overlength-strings -Wno-long-long -Wheader-guard -Wc++-compat 
-Wdeclaration-after-statement -Wunused-const-variable -Wshadow 
-Wno-pointer-sign -Wold-style-definition -Wstrict-prototypes 
-Wshorten-64-to-32 -Qunused-arguments -fvisibility=hidden 
-Wc99-extensions -O2 -pipe  -funit-at-a-time -fstack-protector 
-fno-strict-aliasing -L/usr/local/lib -Wl,-rpath,/usr/local/lib 
-fstack-protector -o sshdump sshdump.o extcap-base.o ssh-base.o 
../wiretap/libwiretap.la ../wsutil/libwsutil.la -L/usr/local/lib 
-lgthread-2.0 -Wl,--export-dynamic -lgmodule-2.0 -pthread -lglib-2.0 
-lintl  -lz -lm -L/usr/local/lib
libtool: link: cc -Wall -Wextra -Wendif-labels -Wpointer-arith 
-Wformat-security -fwrapv -Wvla -Waddress -Wattributes -Wdiv-by-zero 
-Wignored-qualifiers -Wpragmas -Wno-overlength-strings -Wno-long-long 
-Wheader-guard -Wc++-compat -Wdeclaration-after-statement 
-Wunused-const-variable -Wshadow -Wno-pointer-sign 
-Wold-style-definition -Wstrict-prototypes -Wshorten-64-to-32 
-Qunused-arguments -fvisibility=hidden -Wc99-extensions -O2 -pipe 
-funit-at-a-time -fstack-protector -fno-strict-aliasing -Wl,-rpath 
-Wl,/usr/local/lib -fstack-protector -o .libs/randpktdump randpktdump.o 
extcap-base.o -Wl,--export-dynamic -pthread  -L/usr/local/lib 
../randpkt_core/librandpkt_core.a ../wiretap/.libs/libwiretap.so 
../wsutil/.libs/libwsutil.so -lgthread-2.0 -lgmodule-2.0 -lglib-2.0 
-lintl -lz -lm -pthread -Wl,-rpath -Wl,/usr/local/lib
libtool: link: cc -Wall -Wextra -Wendif-labels -Wpointer-arith 
-Wformat-security -fwrapv -Wvla -Waddress -Wattributes -Wdiv-by-zero 
-Wignored-qualifiers -Wpragmas -Wno-overlength-strings -Wno-long-long 
-Wheader-guard -Wc++-compat -Wdeclaration-after-statement 
-Wunused-const-variable -Wshadow -Wno-pointer-sign 
-Wold-style-definition -Wstrict-prototypes -Wshorten-64-to-32 
-Qunused-arguments -fvisibility=hidden -Wc99-extensions -O2 -pipe 
-funit-at-a-time -fstack-protector -fno-strict-aliasing -Wl,-rpath 
-Wl,/usr/local/lib -fstack-protector -o .libs/sshdump sshdump.o 
extcap-base.o ssh-base.o -Wl,--export-dynamic -pthread  -L/usr/local/lib 
../wiretap/.libs/libwiretap.so ../wsutil/.libs/libwsutil.so 
-lgthread-2.0 -lgmodule-2.0 -lglib-2.0 -lintl -lz -lm -pthread 
-Wl,-rpath -Wl,/usr/local/lib
/bin/sh ../libtool  --tag=CC   --mode=link cc  -Wall -Wextra 
-Wendif-labels -Wpointer-arith -Wformat-security -fwrapv -Wvla -Waddress 
-Wattributes -Wdiv-by-zero -Wignored-qualifiers -Wpragmas 
-Wno-overlength-strings -Wno-long-long -Wheader-guard -Wc++-compat 
-Wdeclaration-after-statement -Wunused-const-variable -Wshadow 
-Wno-pointer-sign -Wold-style-definition -Wstrict-prototypes 
-Wshorten-64-to-32 -Qunused-arguments -fvisibility=hidden 
-Wc99-extensions -O2 -pipe  -funit-at-a-time -fstack-protector 
-fno-strict-aliasing -L/usr/local/lib -Wl,-rpath,/usr/local/lib 
-fstack-protector -o ciscodump ciscodump.o extcap-base.o ssh-base.o 
../writecap/libwritecap.a ../wsutil/libwsutil.la -L/usr/local/lib 
-lgthread-2.0 -Wl,--export-dynamic -lgmodule-2.0 -pthread -lglib-2.0 
-lintl  -lz -lm -L/usr/local/lib

sshdump.o: In function `main':
sshdump.c:(.text+0x918

Re: wireshark 2.2.x build fail

2016-10-17 Thread Joe Marcus Clarke

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

2016-10-16 Thread Michael Butler

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

2016-10-16 Thread Joe Marcus Clarke

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"


wireshark 2.2.x build fail

2016-10-15 Thread Michael Butler
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"


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"


Latest wireshark does not build with base system

2015-11-17 Thread Kevin Oberman
I feel odd commenting, as I think ports should not be using base system
tools like krb5, but that is the default for wireshark. If I choose to use
the port version, it builds fine.

I'd really like to see the default changed to use the port, but, if use of
the base krb5 is allowed, it probably should work.

I have opened https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204649
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
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"


Wireshark - error while building from source

2014-10-27 Thread Ewald Jenisch
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] Error code 1

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

Stop in /usr/ports/net/wireshark.

--  Cut here  --

I then followed the tip given at the end

Re: Wireshark - error while building from source

2014-10-27 Thread Kevin Oberman
On Mon, Oct 27, 2014 at 4:22 AM, Ewald Jenisch a...@jenisch.at 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] Error code 1

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

 Stop in /usr

Wireshark, RTP stream playback and portaudio2

2014-03-22 Thread Mars G. Miro
Hi

If you build wireshark w/ support for playing back RTP streams and you
have already audio/portaudio2 installed, the build will fail. But you
can build wireshark w/ portaudio2 instead, here's a patched attached.

Thanks.

-- 
In Riemann, Hilbert or in Banach space
Let superscripts and subscripts go their ways.
Our asymptotes no longer out of phase,
We shall encounter, counting, face to face.
-- Stanislaw Lem, Cyberiad
--- Makefile.orig   2014-03-10 07:56:33.0 +0800
+++ Makefile2014-03-22 16:19:47.0 +0800
@@ -112,8 +112,8 @@
 .endif
 
 .if ${PORT_OPTIONS:MRTP}  !defined(LITE)
-LIB_DEPENDS+=  portaudio:${PORTSDIR}/audio/portaudio
-CONFIGURE_ARGS+=--with-portaudio=${LOCALBASE}
+LIB_DEPENDS+=  portaudio:${PORTSDIR}/audio/portaudio2
+CONFIGURE_ARGS+=--with-portaudio2=${LOCALBASE}
 WIRESHARK_LIBS+=${PTHREAD_LIBS}
 .else
 CONFIGURE_ARGS+=--without-portaudio
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

wireshark

2012-08-18 Thread Doug Barton
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.

Any chance of getting this in soon'ish? Or do I have your permission to
do the version upgrade?

Doug

-- 

I am only one, but I am one.  I cannot do everything, but I can do
something.  And I will not let what I cannot do interfere with what
I can do.
-- Edward Everett Hale, (1822 - 1909)
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


Re: wireshark

2012-08-18 Thread Jason Hellenthal
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: 10-CURRENT ports/net/wireshark does not compile

2011-11-26 Thread Tom Uffner

as of Sat Nov 26 03:57:08 EST 2011 on FreeBSD 10.0-CURRENT amd64, I also
have a problem building wireshark and/or wireshark-lite. i get different
errors though.

It did not make any difference whether or not I used the UPDATING-20110928
9.9-CURRENT hack. tried it both ways w/ freshly built libtool. rebuilding
nettle-2.4 (which seemed to be where all of the undefined references in my
linker errors live) didn't help either.

i finally got it to build by commenting out WITHOUT_GNUTLS=1 in /etc/make.conf

this is probably related to the PR ports/162879 

tom
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


10-CURRENT ports/net/wireshark does not compile

2011-11-16 Thread Matthias Apitz

Hello,

/usr/ports is uptodate as of CVS of yesterday, kernel/world are r226986;
the above mentioned port does not compile, it gives:

# make install
...
libtool: compile:  cc -DHAVE_CONFIG_H -I. -I. -I../.. -I./../.. -I./.. 
-I/usr/local/include -I/usr/local/include/p11-kit-1 -I/usr/local/ nclude 
-I/usr/local/include -I/usr/local/include -I/usr/include/pcap 
-I/usr/local/lib/include -I/usr/include -DPLUGIN_DIR=\/usr/local/l 
b/wireshark/plugins/1.6.2\ -DINET6 -D_U_=__attribute__((unused)) -O2 -pipe 
-funit-at-a-time -fno-strict-aliasing -Wall -W -Wextra -Wd 
claration-after-statement -Wendif-labels -Wpointer-arith -Wno-pointer-sign 
-Wcast-align -Wformat-security -I/usr/local/include -I/usr/lo al/include 
-D_THREAD_SAFE -D_REENTRANT -I/usr/local/include/gtk-2.0 
-I/usr/local/lib/gtk-2.0/include -I/usr/local/include/atk-1.0 -I/usr 
local/include/cairo -I/usr/local/include/gdk-pixbuf-2.0 
-I/usr/local/include/pango-1.0 -I/usr/local/include/gio-unix-2.0/ 
-I/usr/local/i clude -I/usr/local/include/glib-2.0 
-I/usr/local/include/pixman-1 -I/usr/local/include/freetype2 
-I/usr/include/pcap -I/usr/local/lib/in lude -I/usr/include -MT 
libdissectors_la-packet-kerberos.lo -MD -MP -MF 
.deps/libdissectors_la-packet-kerberos.Tpo -c packet-kerberos.c  -fPIC -DPIC -o 
.libs/libdissectors_la-packet-kerberos.o
packet-kerberos.c: In function 'read_keytab_file':
packet-kerberos.c:653: error: 'krb5_principal_data' has no member named 'name'
packet-kerberos.c:654: error: 'krb5_principal_data' has no member named 'name'
packet-kerberos.c:654: error: 'krb5_principal_data' has no member named 'name'
packet-kerberos.c:657: warning: format '%s' expects type 'char *', but argument 
4 has type 'krb5_data'
packet-kerberos.c:657: warning: format '%s' expects type 'char *', but argument 
4 has type 'krb5_data'
packet-kerberos.c:660: error: 'krb5_keytab_entry' has no member named 'keyblock'
packet-kerberos.c:661: error: 'krb5_keytab_entry' has no member named 'keyblock'
packet-kerberos.c:662: error: 'krb5_keytab_entry' has no member named 'keyblock'
packet-kerberos.c:662: error: 'krb5_keytab_entry' has no member named 'keyblock'
packet-kerberos.c: In function 'decrypt_krb5_data':
packet-kerberos.c:702: error: 'krb5_crypto' undeclared (first use in this 
function)
packet-kerberos.c:702: error: (Each undeclared identifier is reported only once
packet-kerberos.c:702: error: for each function it appears in.)
packet-kerberos.c:702: error: expected ';' before 'crypto'
packet-kerberos.c:703: warning: ISO C90 forbids mixed declarations and code
packet-kerberos.c:710: error: 'krb5_keytab_entry' has no member named 'keyblock'
packet-kerberos.c:711: error: 'krb5_keytab_entry' has no member named 'keyblock'
packet-kerberos.c:712: error: 'krb5_keytab_entry' has no member named 'keyblock'
packet-kerberos.c:713: warning: implicit declaration of function 
'krb5_crypto_init'
packet-kerberos.c:713: error: 'krb5_keytab_entry' has no member named 'keyblock'
packet-kerberos.c:713: error: 'crypto' undeclared (first use in this function)
packet-kerberos.c:725: warning: implicit declaration of function 
'krb5_decrypt_ivec'
packet-kerberos.c:735: warning: implicit declaration of function 
'krb5_crypto_destroy'
gmake[5]: *** [libdissectors_la-packet-kerberos.lo] Error 1
gmake[5]: Leaving directory 
`/usr/ports/net/wireshark/work/wireshark-1.6.2/epan/dissectors'
gmake[4]: *** [all-recursive] Error 1
gmake[4]: Leaving directory 
`/usr/ports/net/wireshark/work/wireshark-1.6.2/epan/dissectors'
gmake[3]: *** [all] Error 2
gmake[3]: Leaving directory 
`/usr/ports/net/wireshark/work/wireshark-1.6.2/epan/dissectors'
gmake[2]: *** [all-recursive] Error 1
gmake[2]: Leaving directory `/usr/ports/net/wireshark/work/wireshark-1.6.2/epan'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/usr/ports/net/wireshark/work/wireshark-1.6.2'

-- 
Matthias Apitz
e g...@unixarea.de - w http://www.unixarea.de/
UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370)
UNIX on x86 since SVR4.2 UnixWare 2.1.2, FreeBSD since 2.2.5
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


running wireshark as a non root user

2008-02-13 Thread Piotr

hi

howto configure freeBSD 6.3 to run wireshark as a non root user ?
if I start it as a normal user, I cannot choose the interfaces.





___
Join Excite! - http://www.excite.com
The most personalized portal on the Web!


___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: running wireshark as a non root user

2008-02-13 Thread Alex Dupre

Piotr ha scritto:

howto configure freeBSD 6.3 to run wireshark as a non root user ?
if I start it as a normal user, I cannot choose the interfaces.


sudo wireshark

--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: running wireshark as a non root user

2008-02-13 Thread Max Laier

Am Mi, 13.02.2008, 15:10, schrieb Piotr:
 howto configure freeBSD 6.3 to run wireshark as a non root user ?
 if I start it as a normal user, I cannot choose the interfaces.

This is a wireshark FAQ:
http://wiki.wireshark.org/CaptureSetup/CapturePrivileges

-- 
/\  Best regards,  | [EMAIL PROTECTED]
\ /  Max Laier  | ICQ #67774661
 X   http://pf4freebsd.love2party.net/  | [EMAIL PROTECTED]
/ \  ASCII Ribbon Campaign  | Against HTML Mail and News
___
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...

2007-02-23 Thread Eric Schuele

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_1needs 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...

2007-02-23 Thread Robert Huff
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...

2007-02-23 Thread Peter Pentchev
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...

2007-02-23 Thread Robert Huff
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]


wireshark build problem....

2007-02-21 Thread Eric Schuele

Hello,

Anyone seeing the following while building the latest wireshark? 
Previously had it installed, this was just a portupgrade from:


wireshark-0.99.4_1needs 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]


Re: wireshark build problem....

2007-02-21 Thread Stacey Roberts
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_1needs 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


Re: wireshark build problem...

2007-02-21 Thread George W. Dinolt
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_1needs 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]


Wireshark-0.99.2 build (formerly ethereal)

2006-07-23 Thread Chris Timmons


There are some issues with this port, which used to be known as the 
Ethereal network analzyer.


#1 There is now a dependency on security/libgcrypt which the port needs to
   be taught about.  On 6.1-STABLE, this causes a build failure which can
   manually be resolved by adding -lgcrypt to the command line:

epan/.libs/libwireshark.so: undefined reference to `gcry_md_get_algo_dlen'
epan/.libs/libwireshark.so: undefined reference to `gcry_md_close'
epan/.libs/libwireshark.so: undefined reference to `gcry_md_read'
epan/.libs/libwireshark.so: undefined reference to `gcry_md_setkey'
epan/.libs/libwireshark.so: undefined reference to 
`gcry_cipher_get_algo_keylen'

epan/.libs/libwireshark.so: undefined reference to `gcry_control'
epan/.libs/libwireshark.so: undefined reference to `gcry_md_write'
epan/.libs/libwireshark.so: undefined reference to `gcry_cipher_open'
epan/.libs/libwireshark.so: undefined reference to `gcry_cipher_ctl'
epan/.libs/libwireshark.so: undefined reference to `gcry_cipher_close'
epan/.libs/libwireshark.so: undefined reference to `gcry_md_open'
epan/.libs/libwireshark.so: undefined reference to `gcry_md_algo_name'
epan/.libs/libwireshark.so: undefined reference to `gpg_strerror'
epan/.libs/libwireshark.so: undefined reference to `gcry_cipher_decrypt'
epan/.libs/libwireshark.so: undefined reference to `gcry_cipher_algo_name'
*** Error code 1

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

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

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

Stop in /usr/ports/net/wireshark.


#2  Someone just updated net/wireshark/pkg-descr to show the project
link to be: http://www.writeshark.org/

http://www.wireshark.org is the correct site.



___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]