Ethereal-dev: Re: [Ethereal-dev] Building Ethereal under MacOS X 10.2

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

From: Guy Harris <guy@xxxxxxxxxxxx>
Date: Wed, 19 Nov 2003 13:55:51 -0800
On Nov 19, 2003, at 1:33 PM, Devin Heitmueller wrote:

Ok, so I finally broke down and bought a PowerBook.
And it came with Jaguar, not Panther?  (Or did you buy it a while ago?)

I'm trying to get Ethereal to compile, but am having a problem with the
dependencies. I have the Apple Developers SDK installed already, so the
compiler looks fine, but I am having trouble getting the glib source to
compile.
If your PowerBook came with Jaguar, spending $129 or so might make your 
life a fair bit more pleasant here. :-)  (I don't know whether there 
were free upgrades available to users who bought sufficiently close to 
the release of Panther.)
(Panther, for example, includes dlcompat's "dlopen()"/"dlsym()" 
implementations, so you don't have to go through as much effort to get 
plugin support.)
Glib compiled out of the box for me on Panther, as did GTK+.

To all you OSX users out there, is there a version of glib that you
recommend for use with Ethereal?  What about GTK?
1.2.10 in both cases.

  Libpcap?
The one that comes with OS X is probably Good Enough.

(Hint: "sudo chown {yourself} /dev/bpf*" lets you run Ethereal - or tcpdump, or snort, or... - as yourself, rather than as root. That applies to all BPF-based systems, although you might have to use "su" and run it from a new shell if you don't have "sudo", although
	1) you have to do it after every reboot on Mac OS X, as "/dev" is 
implemented with devfs;
	2) you'd have to do the same thing on AIX *but you still have to run 
AIX's tcpdump, or an application built with current-CVS or 0.8 beta1 
libpcap, as root after a reboot, in order to create the devices in the 
first place*;
	3) on most versions of {Free,Net,Open}BSD, and probably BSD/OS, "/dev" 
is on disk so you'd only have to do that once;
	4) on recent 5.x FreeBSD's, "/dev" is implemented with devfs, *but* 
it's controlled by a policy file so you could, I think, arrange that 
you own "/dev/bpf*".)