ould be removed.
>> If so, since it runs natively in Aqua, will there be a MacPorts version of
>> it?
>
> No! Because the wireshark port already has a "qt" variant! For switching
> between
> gtk2, gtk3 and Qt, you'll need to deactivate the current wir
the Cocoa
interface and don't need X11.
However, there's also at least qt4-x11, so NOT using X11 is not mandatory.
Depends on the user's choice.
> If so, since it runs natively in Aqua, will there be a MacPorts version of it?
No! Because the wireshark port already has a "qt
With the impending release of Wireshark 2.0 where one of the critical elements
is that it will be switching over to the QT libraries from the GTK libraries,
what is impact/effect on the MacPorts version of it? I'm not a graphics
engine/windowing systems expert so my question is: Wil
The latest MacPorts upgrade to Wireshark 1.12.4, which updated without a
problem, now reliably crashes when trying to start it up. Previous version
worked fine.
I have the Wireshark app 1.99.2 also installed which still works ok.
When starting from the terminal MacPorts Wireshark crashes with
On Mar 11, 2015, at 7:32 AM, Adam Dershowitz Ph.D., P.E.
wrote:
>
>
> On Mar 11, 2015, at 5:02 AM, Mark Lucas wrote:
>
>> The latest MacPorts upgrade to Wireshark 1.12.4, which updated without a
>> problem, now reliably crashes when trying to start it up. Previous
On Mar 11, 2015, at 5:02 AM, Mark Lucas wrote:
> The latest MacPorts upgrade to Wireshark 1.12.4, which updated without a
> problem, now reliably crashes when trying to start it up. Previous version
> worked fine.
> I have the Wireshark app 1.99.2 also installed which st
>
>> On Mar 6, 2015, at 11:33 AM, t...@qx.net wrote:
>>
>>> Non-fat file: /opt/local/lib/libffi.6.dylib is architecture: ppc7400
>>> Non-fat file: /opt/local/lib/libgio-2.0.0.dylib is architecture: ppc
>>>
>> It looked to me like libffi is the one in error,
>
> Agreed. Now the question is: why did
On Saturday March 07 2015 03:32:33 Ryan Schmidt wrote:
>But, I think it will come down to this line in the source code:
>
>#define machine_choice MODE_CHOICE(ppc7400,ppc64)
>
>in the files src/powerpc/darwin.S and src/powerpc/darwin_closure.S. I don't
>know if just changing that "ppc7400" to "ppc
> On Mar 6, 2015, at 11:33 AM, t...@qx.net wrote:
>
>> Non-fat file: /opt/local/lib/libffi.6.dylib is architecture: ppc7400
>> Non-fat file: /opt/local/lib/libgio-2.0.0.dylib is architecture: ppc
>>
> It looked to me like libffi is the one in error,
Agreed. Now the question is: why did libffi g
On Friday March 06 2015 12:33:05 t...@qx.net wrote:
> It looked to me like libffi is the one in error, so below is a grep of
> libffi.6.dylib from the original install attempt:
Yes.
This command
> libtool: link: /opt/local/bin/gcc-apple-4.2 -dynamiclib -o
> .libs/libffi.6.dylib src/.libs/pre
>>
>> On Mar 5, 2015, at 11:29 AM, t...@qx.net wrote:
>>
>>> Powerbook PPC (pismo) 500Mhz, 10.4.11, 1G ram, 11G disk available
>>> I did the 'sudo port clean wireshark' and retried, with same error.
>>> A search revealed a reference to a patch
On Friday March 06 2015 11:55:15 t...@qx.net wrote:
> > lipo -info /opt/local/lib/libffi.6.dylib /opt/local/lib/libgio-2.0.0.dylib
> >
> >
> Non-fat file: /opt/local/lib/libffi.6.dylib is architecture: ppc7400
> Non-fat file: /opt/local/lib/libgio-2.0.0.dylib is architecture: ppc
The latter shoul
>
> On Mar 5, 2015, at 11:29 AM, t...@qx.net wrote:
>
>> Powerbook PPC (pismo) 500Mhz, 10.4.11, 1G ram, 11G disk available
>> I did the 'sudo port clean wireshark' and retried, with same error.
>> A search revealed a reference to a patch:
>> https://tra
On Mar 6, 2015, at 3:54 AM, René J.V. Bertin wrote:
> On Friday March 06 2015 03:04:57 Ryan Schmidt wrote:
>
>> This is probably a PowerPC G3-specific issue. I'll bet something got
>> inadvertently compiled for PowerPC G4, which is not compatible with your G3.
>> What is the CPU subtype of /op
On Friday March 06 2015 03:04:57 Ryan Schmidt wrote:
>This is probably a PowerPC G3-specific issue. I'll bet something got
>inadvertently compiled for PowerPC G4, which is not compatible with your G3.
>What is the CPU subtype of /opt/local/lib/libffi.6.dylib and
>/opt/local/lib/libgio-2.0.0.dyl
On Mar 5, 2015, at 11:29 AM, t...@qx.net wrote:
> Powerbook PPC (pismo) 500Mhz, 10.4.11, 1G ram, 11G disk available
> I did the 'sudo port clean wireshark' and retried, with same error.
> A search revealed a reference to a patch:
> https://trac.macports.org/attachment/t
Powerbook PPC (pismo) 500Mhz, 10.4.11, 1G ram, 11G disk available
I did the 'sudo port clean wireshark' and retried, with same error.
A search revealed a reference to a patch:
https://trac.macports.org/attachment/ticket/41843/0001-gnome-gstreamer010-add-dependency-on-gobject-introsp.p
I was using the instructions for Mac OS X from this page:
http://ubertooth.sourceforge.net/usage/build/#osx
wireshark-devel is an alpha release, not a developer library --- and, while I
haven't looked, it may well be the *previous* alpha release.
I will retry using the "wireshark&quo
On Wed, Oct 16, 2013 at 1:35 PM, Kennedy, Smith (Wireless Architect) <
smith.kenn...@hp.com> wrote:
> I'm in the process of trying to build the Wireshark plugin for the
> Ubertooth One. The instructions are here:
>
> http://ubertooth.sourceforge.net/usage/build/#osx
>
Hi again,
I'm in the process of trying to build the Wireshark plugin for the Ubertooth
One. The instructions are here:
http://ubertooth.sourceforge.net/usage/build/#osx
The issue I'm having is building the Wireshark plugin. Following these
instructions (that need to be fixed):
Thanks for the quick reply! Updated 40782 with reference to 40620.
Smith
On 2013-10-15, at 11:01 PM, Ryan Schmidt
wrote:
>
> On Oct 15, 2013, at 23:36, "Kennedy, Smith (Wireless Architect)"
> wrote:
>
>> When I recently updated my wireshark port, the build
On Oct 15, 2013, at 23:36, "Kennedy, Smith (Wireless Architect)"
wrote:
> When I recently updated my wireshark port, the build failed. The trace in my
> shell where the error occurred was this:
>
>> In file included from packet-gluster_cli.c:43:
>> ./packet-g
Hello,
When I recently updated my wireshark port, the build failed. The trace in my
shell where the error occurred was this:
> In file included from packet-gluster_cli.c:43:
> ./packet-gluster.h:359:2: error: expected '}'
> DT_UNKNOWN = 0,
> ^
> /usr/in
On Feb 22, 2013, at 15:18, Kok-Yong Tan wrote:
> So, should I file a bug or have one of you already done so?
I didn't see a bug report about this so you should file one.
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists
On Feb 22, 2013, at 09:15 , Brandon Allbery wrote:
> On Fri, Feb 22, 2013 at 5:36 AM, Ryan Schmidt wrote:
> On Feb 22, 2013, at 03:37, Kok-Yong Tan wrote:
> > Question is: Is this a bug or have I done something incorrectly?
>
> It sounds like a bug to me.
>
> >
On Fri, Feb 22, 2013 at 5:36 AM, Ryan Schmidt wrote:
> On Feb 22, 2013, at 03:37, Kok-Yong Tan wrote:
> > Question is: Is this a bug or have I done something incorrectly?
>
> It sounds like a bug to me.
>
> > Is wireshark using "python" or "python2.7&qu
On Feb 22, 2013, at 03:37, Kok-Yong Tan wrote:
> Question is: Is this a bug or have I done something incorrectly?
It sounds like a bug to me.
> Is wireshark using "python" or "python2.7"?
I don't know. If it's using "python" that would be a bug.
I have successfully built Wireshark 1.8.5 on an Intel MacBook Pro running MacOS
10.8.2 with XQuartz.app 2.7.4. And here's the script buried within an
application wrapper I found somewhere with a nice Wireshark icon on it that I
use to start Wireshark:
#!/bin/bash
/usr/bin/op
Like Myron, I finally built xorg-server (along with wireshark) from
scratch using gcc-4.2 instead of gcc-4.0 by totally dumping /opt with
"sudo rm -rf /opt" and reinstalling from .dmg. Now, wireshark 1.8 now
works without X11 kicking its legs out from under it (i.e., X11 used to
cra
I installed the xorg-server and now wireshark works fine. Thanks for
your help.
--myron
=
Myron Kowalski
MoCoSIN Network/Systems Administrator
Moravian College
my...@moravian.edu
(610) 861-1441
On Jul 17, 2012, at 1:46 PM, Jeremy Huddleston Sequoia wrote
>>> It appears that when I changed the default compiler, the "sudo port -v
>>> install wireshark configure.compiler=gcc-4.2"
>> Why did you do that? What problem are you trying to fix by forcing that
>> compiler to be used? What Xcode version do you ha
On Jul 17, 2012, at 11:03 AM, Brandon Allbery wrote:
On Tue, Jul 17, 2012 at 9:20 AM, myron
wrote:
I had been following a thread about wireshark the other day and
decided to start up my wireshark which I had
just upgraded. I hadn't used it for a few months, and it was working
then
On 7/16/12 15:59, Jeremy Huddleston Sequoia wrote:
On Jul 15, 2012, at 21:31, Kok-Yong Tan wrote:
Thanks for the info. I went into .bashrc and found an explicit setting for the DISPLAY
environment variable which I ripped out. Then I restarted X11 and did "sudo
wireshark" whe
On Tue, Jul 17, 2012 at 9:20 AM, myron wrote:
> I had been following a thread about wireshark the other day and decided to
> start up my wireshark which I had
> just upgraded. I hadn't used it for a few months, and it was working then.
> Now I'm getting a similar problem as
I had been following a thread about wireshark the other day and
decided to start up my wireshark which I had
just upgraded. I hadn't used it for a few months, and it was working
then. Now I'm getting a similar problem as the
other poster. I didn't get what his solution was.
I
On Jul 15, 2012, at 21:31, Kok-Yong Tan wrote:
>> Thanks for the info. I went into .bashrc and found an explicit setting for
>> the DISPLAY environment variable which I ripped out. Then I restarted X11
>> and did "sudo wireshark" whereupon X11 crashed and t
On 7/16/12 10:27, Brandon Allbery wrote:
On Mon, Jul 16, 2012 at 1:20 AM, Kok-Yong Tan
mailto:k...@realityartisans.com>> wrote:
Hmmm...that seems to be only recompiling wireshark itself. Is
there a command in MacPorts that will do a clean for *EVERYTHING*
that wireshark depe
On Mon, Jul 16, 2012 at 1:20 AM, Kok-Yong Tan wrote:
> Hmmm...that seems to be only recompiling wireshark itself. Is there a
> command in MacPorts that will do a clean for *EVERYTHING* that wireshark
> depends on without wiping out tarballs? i.e., take the list generated by
> &q
On Jul 16, 2012, at 00:20, Kok-Yong Tan wrote:
> On 7/16/12 00:31, Kok-Yong Tan wrote:
>> It appears that when I changed the default compiler, the "sudo port -v
>> install wireshark configure.compiler=gcc-4.2" command might not have
>> recompiled the ports tha
On 7/16/12 00:31, Kok-Yong Tan wrote:
On 7/16/12 00:11, Kok-Yong Tan wrote:
On 7/15/12 23:27, Brandon Allbery wrote:
On Sun, Jul 15, 2012 at 10:39 PM, Kok-Yong Tan
mailto:k...@realityartisans.com>> wrote:
Can anyone tell me what this error means when I try to start
wireshark
On 7/16/12 00:11, Kok-Yong Tan wrote:
On 7/15/12 23:27, Brandon Allbery wrote:
On Sun, Jul 15, 2012 at 10:39 PM, Kok-Yong Tan
mailto:k...@realityartisans.com>> wrote:
Can anyone tell me what this error means when I try to start
wireshark in an xterm window via the X11
On 7/15/12 23:27, Brandon Allbery wrote:
On Sun, Jul 15, 2012 at 10:39 PM, Kok-Yong Tan
mailto:k...@realityartisans.com>> wrote:
Can anyone tell me what this error means when I try to start
wireshark in an xterm window via the X11 system:
bash-3.2$ sudo wireshark
(wir
On Sun, Jul 15, 2012 at 10:39 PM, Kok-Yong Tan wrote:
> Can anyone tell me what this error means when I try to start wireshark in
> an xterm window via the X11 system:
>
> bash-3.2$ sudo wireshark
>
> (wireshark:11767): Gtk-WARNING **: cannot open display: :0.0
>
It means
Hi,
Can anyone tell me what this error means when I try to start wireshark
in an xterm window via the X11 system:
bash-3.2$ sudo wireshark
(wireshark:11767): Gtk-WARNING **: cannot open display: :0.0
bash-3.2$
___
macports-users mailing list
> Did I understood right?
> *-devel is the development version, where the other is without *-devel
> in string is the stable.
You're correct, it just means the devel version hasn't been updated.
smime.p7s
Description: S/MIME cryptographic signature
__
Hi
Did I understood right?
*-devel is the development version, where the other is without *-devel
in string is the stable.
Wireshark's devel is older than the non-devel.
> port search wireshark
ethereal @0.99.0 (net)
(NB: wireshark is the maintained version) Graphical network
anal
On Nov 12, 2010, at 14:40, Sven Aluoor wrote:
> I installed
>
> # port list installed | grep wireshark
> wireshark @1.4.1 net/wireshark
"port list" does not do what you think it does. See:
http://trac.macports.org/wiki/FAQ#portlist
The
Hi folks
I installed
# port list installed | grep wireshark
wireshark @1.4.1 net/wireshark
When logging with my user account -> no interfaces show up in the list
for capturing (as root it works). The source for this problem are too
less rights on /dev/bpf*
#
iled requesting ChmodBPF functionality be
> added to the MacPorts wireshark ports:
>
> http://trac.macports.org/ticket/26293
>
Added myself to that ticket's list. Would be great if that patch is up and
running.
___
macports-users mailing list
On Sep 17, 2010, at 07:53, Jeff Singleton wrote:
> Also, doing it this way provides a ChmodBPF script to automatically set the
> permissions on the /dev/bpf* for you.
Here is the ticket that was filed requesting ChmodBPF functionality be added to
the MacPorts wireshark ports:
On Sep 17, 2010, at 21:27, Savory Michael wrote:
> wireshark-devel @1.4.0 (net)
[snip]
> could to be updated to 1.5.0, now that 1.4.0 has been released as stable
> then...
Well, version 1.5.0 does not exist yet. The developers are working on creating
version 1.5.0. The wireshark-d
; detected in a packet capture. I'll leave the rest for you to play with...but
> its pretty easy to see what people are transferring around the network. Add
> the airpcap plugin, and you can do this wirelessly as well.
>
> Question about port wireshark-devel, does it utilize t
t its pretty easy to see what people are transferring around the
network. Add the airpcap plugin, and you can do this wirelessly as well.
Question about port wireshark-devel, does it utilize the built in 'make
osx-app' in anyway to automate making a bundle?
What will it take to get a
HI Ryan
So the
$ sudo port info wireshark-devel
wireshark-devel @1.4.0 (net)
Variants: adns, gnutls, ipv6, libgcrypt, libsmi, lua, no_gui,
no_ssl, pcre, rtp
Description: A network analyzer that lets you capture and interactively
On Sep 17, 2010, at 19:08, Savory Michael wrote:
> Maybe time for a wireshark-dev port?
The wireshark-devel port already exists.
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.
Hi Jeff
Maybe time for a wireshark-dev port?
Any docs on the really cool plugins available?
Mike
On Sep 17, 2010, at 5:53 AM, Jeff Singleton wrote:
> Oh ... if you wish to try building Wireshark from SVN, the v1.5.0 tree is
> very stable and a lot of really cool plugins. Not to ment
Oh ... if you wish to try building Wireshark from SVN, the v1.5.0 tree is
very stable and a lot of really cool plugins. Not to mention it comes with
a 'make osx-app' command that will build the .app bundle for you...there is
also 'make osx-package' that makes the .pkg bundle.
On Wed, Sep 15, 2010 at 3:04 PM, Ryan Schmidt wrote:
> On Sep 15, 2010, at 04:17, Jasper Frumau wrote:
> > On Tue, Sep 14, 2010 at 6:51 PM, Jeff Singleton wrote:
> >> Actually ... that will work! Its the ChmodBPF steps to change the
> permissions so that the 'admin' group can access the devices.
>
On Sep 15, 2010, at 04:17, Jasper Frumau wrote:
> On Tue, Sep 14, 2010 at 6:51 PM, Jeff Singleton wrote:
>> Actually ... that will work! Its the ChmodBPF steps to change the
>> permissions so that the 'admin' group can access the devices.
>
> I looked for bpf as indicated at
> http://wiki.wir
Is this the correct folder? wil chmod 666 do?
> On Tue, Sep 14, 2010 at 10:36 AM, Rainer Müller wrote:
>
>> On 2010-09-14 12:40 , Jasper Frumau wrote:
>> > Installed Wireshark a while. Decided to use it for some network analysis
>> > today, using it for the first time ev
Actually ... that will work! Its the ChmodBPF steps to change the
permissions so that the 'admin' group can access the devices.
On Tue, Sep 14, 2010 at 10:36 AM, Rainer Müller wrote:
> On 2010-09-14 12:40 , Jasper Frumau wrote:
> > Installed Wireshark a while. Decided to use
On 2010-09-14 12:40 , Jasper Frumau wrote:
> Installed Wireshark a while. Decided to use it for some network analysis
> today, using it for the first time ever. Got an error "There are no
> interfaces on which a capture can be done". I believ I need teh capture
> support
Installed Wireshark a while. Decided to use it for some network analysis
today, using it for the first time ever. Got an error "There are no
interfaces on which a capture can be done". I believ I need teh capture
support driver like wincap for Windows. Which one can I install using
M
On 29 Sep 2009, at 20:28:43, Ryan Schmidt wrote:
On Sep 29, 2009, at 22:24, Merton Campbell Crockett wrote:
On 29 Sep 2009, at 19:57:34, Bryan Blackburn wrote:
On Tue, Sep 29, 2009 at 07:51:41PM -0700, Merton Campbell Crockett
said:
I use Wireshark constantly to diagnose application and
On Sep 29, 2009, at 22:24, Merton Campbell Crockett wrote:
On 29 Sep 2009, at 19:57:34, Bryan Blackburn wrote:
On Tue, Sep 29, 2009 at 07:51:41PM -0700, Merton Campbell Crockett
said:
I use Wireshark constantly to diagnose application and network
problems. I have two Mac Pro systems. The
On 29 Sep 2009, at 19:57:34, Bryan Blackburn wrote:
On Tue, Sep 29, 2009 at 07:51:41PM -0700, Merton Campbell Crockett
said:
I use Wireshark constantly to diagnose application and network
problems. I have two Mac Pro systems. The one at work is a
MacPro1,1. At home, I have a MacPro3,1
On Tue, Sep 29, 2009 at 07:51:41PM -0700, Merton Campbell Crockett said:
> I use Wireshark constantly to diagnose application and network
> problems. I have two Mac Pro systems. The one at work is a
> MacPro1,1. At home, I have a MacPro3,1.
>
> After upgrading to OS X 10.6.
I use Wireshark constantly to diagnose application and network
problems. I have two Mac Pro systems. The one at work is a
MacPro1,1. At home, I have a MacPro3,1.
After upgrading to OS X 10.6.1, I downloaded MacPorts 1.8 and ran into
the problem that everyone seems to have encountered
On 18/9/09 11:03, Ryan Schmidt wrote:
I have filed a ticket requesting the port be updated:
http://trac.macports.org/ticket/21472
Wireshark has been updated to 1.2.2 and everything works fine now.
Thanks for your help :)
Mike
___
macports-users
On 18/09/2009 11:03, Ryan Schmidt wrote:
I have filed a ticket requesting the port be updated:
http://trac.macports.org/ticket/21472
Great, thanks.
Mike
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org
On Sep 18, 2009, at 03:51, Mike Zanker wrote:
I've installed MacPorts 1.8.0 on a new Snow Leopard installation
(Mac Pro 1,1; 32-bit kernel). Wireshark builds fine and appears to
run but nothing is captured (even though running as root). There is
an error message:
merlin:~ mike$
Hi,
I've installed MacPorts 1.8.0 on a new Snow Leopard installation (Mac
Pro 1,1; 32-bit kernel). Wireshark builds fine and appears to run but
nothing is captured (even though running as root). There is an error
message:
merlin:~ mike$ sudo tshark -i en0
Password:
Could not open
On 16/set/09, at 02:35, Don Wright wrote:
Can I just delete gdk-pixbuf-csource, or is this just the
first bump in the road.
You could enforce gtk2 installation using -f, this will overwrite gdk-
pixbuf-csource and other files already present.
You should definitely check why do you have gdk-p
On Sep 15, 2009, at 19:35, Don Wright wrote:
I’ve tried installing Wireshark on my mac and am getting the
following error messages. Can I just delete gdk-pixbuf-csource, or
is this just the first bump in the road.
-- Don
don$ sudo port install wireshark
Password:
---> Fetching g
> I¹ve tried installing Wireshark on my mac and am getting the following
> error messages. Can I just delete gdk-pixbuf-csource, or is this just the
> first bump in the road.
>
> -- Don
>
> don$ sudo port install wireshark
> Password:
> ---> Fetching gtk2
>
On 31 May 2009, at 14:27:29, Jeremy Huddleston wrote:
The error is 'renderproto', not randr. You seem to not have the
xorg-renderproto port active.
gtk2 depends on xorg-libXrandr which depends on xrender which
depends on xorg-renderproto
Would this mean that the Wires
nd/or xorg-randrproto and/or
xrandr?
like "sudo port install xorg-libXrandr xorg-randrproto xrandr"
It's just a guess from my side
Harry
2009/5/31 Merton Campbell Crockett
I've attempted to upgrade Wireshark to the latest version but keep
running
into the follow
What if you install: xorg-libXrandr and/or xorg-randrproto and/or xrandr?
like "sudo port install xorg-libXrandr xorg-randrproto xrandr"
It's just a guess from my side
Harry
2009/5/31 Merton Campbell Crockett
>
> I've attempted to upgrade Wireshark to the lates
I've attempted to upgrade Wireshark to the latest version but keep
running into the following problem. Does anyone know why this is
occurring?
checking for RANDR... configure: error: Package requirements (x11
randrproto >= 1.3 xext xextproto xrender renderproto) were not m
It appears that you're right. Actually, until I uninstalled the
+no_x11 variant and re-installed the x11 variant, there was no
wireshark in /opt/local/bin (i.e., "which wireshark" failed). I
must've picked up the nice blue Aqua icon from somewhere else. Oh well.
Hi
The Wireshark Port installs the following binaries
$ port contents wireshark
Port wireshark contains:
/opt/local/bin/capinfos
/opt/local/bin/dftest
/opt/local/bin/dumpcap
/opt/local/bin/editcap
/opt/local/bin/idl2wrs
/opt/local/bin/mergecap
/opt/local/bin/randpkt
/opt
X11 server
>> is, you will probably be happy with the +no_x11 variant on ports that
>> support it (such as wireshark).
>
>
> Okay, just for giggles, I did:
>
> sudo port -v install wireshark +no_x11
>
> Unfortunately, at the end, it complained the another variant
code package is the suite of developer tools from Apple.
> These tools are required to build ports. XFree86 is an X11 server,
> prevalent in the Linux world. If you don't know what an X11 server
> is, you will probably be happy with the +no_x11 variant on ports that
> support it (su
Robert Liesenfeld wrote:
> On May 19, 2008, at 8:20 AM, Avery Rozar wrote:
>
>> Hello Macports-users,
>> I'm trying to install wireshark using macports, but I get this
>> error, and dont know what it is telling me.
>>
>> I did install xcode 3 before I in
d ports. XFree86 is an X11 server,
prevalent in the Linux world. If you don't know what an X11 server
is, you will probably be happy with the +no_x11 variant on ports that
support it (such as wireshark).
-Robert
___
macports-users maili
On May 19, 2008, at 8:20 AM, Avery Rozar wrote:
> Hello Macports-users,
> I'm trying to install wireshark using macports, but I get this
> error, and dont know what it is telling me.
>
> I did install xcode 3 before I installed macports, so I dont know
> why it would
Hello Macports-users,
I'm trying to install wireshark using macports, but I get this error, and dont
know what it is telling me.
I did install xcode 3 before I installed macports, so I dont know why it would
need xfree86? I thought xfee86 was an alternative, but I'm probably wron
>On 14/04/08 07:29, Mark Lucas wrote:
>>>Wireshark must be run via sudo to sniff interfaces.
>
>> Thanks, yes I know. sudo -b wireshark has always worked for me. I have
>> wireshark 1.0 working on an intel iMac so I'm assuming this is a
>> problem specific
On 14/04/08 07:29, Mark Lucas wrote:
>>Wireshark must be run via sudo to sniff interfaces.
> Thanks, yes I know. sudo -b wireshark has always worked for me. I have
> wireshark 1.0 working on an intel iMac so I'm assuming this is a
> problem specific to PPC. the point
>On 13/04/08 18:00, Mark Lucas wrote:
>> On a PPC machine running 10.5.2, having done a clean install of
>> MacPorts and then Wireshark 1.0.0_0+darwin_9, Wireshark fails to
>> display any interfaces in the Interfaces dialog or any other
>> preferences dialog .
>>
On 13/04/08 18:00, Mark Lucas wrote:
> On a PPC machine running 10.5.2, having done a clean install of
> MacPorts and then Wireshark 1.0.0_0+darwin_9, Wireshark fails to
> display any interfaces in the Interfaces dialog or any other
> preferences dialog .
>
> dumpcap -D and w
On a PPC machine running 10.5.2, having done a clean install of MacPorts and
then Wireshark 1.0.0_0+darwin_9, Wireshark fails to display any interfaces in
the Interfaces dialog or any other preferences dialog .
dumpcap -D and wireshark - D from the command line both list all the
interfaces
Hi Greg
I had this problem
Upgrading to the latest XQuartz fixed it for me
http://trac.macosforge.org/projects/xquartz/
see this blog for more info
http://www.anders.com/cms/241/Wireshark/MacPorts
Cheers
Mike
On Jan 12, 2008, at 12:23 AM, Ryan Schmidt wrote:
On Jan 12, 2008, at 02
On Jan 12, 2008, at 02:16, Greg Hauptmann wrote:
I actually get the following error when running wireshark, i.e.
after a few seconds of a capture:
Macintosh:~ greg$ wireshark --sync
The program 'wireshark' received an X Window System error.
This probably reflects a bug in the pr
I actually get the following error when running wireshark, i.e. after a few
seconds of a capture:
Macintosh:~ greg$ wireshark --sync
The program 'wireshark' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid param
On Jan 11, 2008, at 19:21, Greg Hauptmann wrote:
I'm on leopard and have performed a successful "sudo port
selfupdate", however I'm getting an error when performing "sudo
port install wireshark". The console out is below.
[snip]
---> Fetching docb
Hi,
I'm on leopard and have performed a successful "sudo port selfupdate",
however I'm getting an error when performing "sudo port install wireshark".
The console out is below.
Any ideas/suggestions?
---> Attempting to fetch docbkx412.zip from
http://svn
I had a problem upgrading wireshark from 0.99.6 to 0.99.7 but it's working
now. I eventually solved it by uninstalling the existing wireshark, and
installing the new version fresh. (I removed kerberos as well, which I
installed as an attempted fix)
I thought I'd share in case anyone
On Dec 2, 2007, at 2:48 PM, Kok-Yong Tan wrote:
Frankly, I don't get those errors you're getting...but then, as I
mentioned, I installed gtk2 +x11 instead of gtk2 +quartz... Just
for kicks, why not uninstall gtk2 +quartz, install gtk2 +x11 and
recompile wireshark and see wh
On 02/12/2007, Kok-Yong Tan <[EMAIL PROTECTED]> wrote:
> But what is it set to in Leopard, out of curiosity?
Something of the form: /tmp/launch-rKldMP/:0
Cheers
Adam
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.maco
1 - 100 of 186 matches
Mail list logo
