On Tue, Jun 26, 2001 at 07:22:37AM -0600, yoshi9@xxxxxxxxxxxx wrote:
> I am working with a custom libpcap library and want to link it to ethereal,
> instead of the standard one that comes with the package. I tried:
> --with-pcap=/usr/src/custompcap
> but it still uses the standard pcap.
There *is* no "--with-pcap" flag in the current Ethereal release;
./configure --help
displays all the flags that are supported.
> Could you please advise?
Either
1) install the custom libpcap under "/usr/local/include" and
"/usr/local/lib", *if* the standard libpcap isn't there -
this *might* work, i.e. *if* the linking rules that the
configure script stuffed into the Makefile search those
directories, it should find the libpcap header files and
libraries there;
2) do a "make clean", and then edit the Makefile and put in the
appropriate "-I" and "-L" flags by hand (you'll have to read
the Makefile to figure out where to put them);
3) get the current CVS version of Ethereal from anonymous CVS:
http://www.ethereal.com/development.html#anoncvs
and make sure you have all the *additional* tools needed to
build from CVS installed (autoconf, automake, libtool, Perl,
Python, GNU "make", Flex, and either Bison or Berkeley YACC;
there might be others that I've missed), and use the
"--with-pcap" that I just checked in to CVS;
4) get the next nightly CVS snapshot of Ethereal:
http://www.ethereal.com/development.html#snapshots
and make sure you have all the additional tools needed to
build from CVS installed, and use "--with-pcap" *if*, after
running "./autogen.sh" completes, running "./configure --help"
reports "--with-pcap" as a valid option (this is to make sure
you don't get a snapshot that was made before I checked in my
changes);
5) wait for the next Ethereal release (I don't know when it will
come out) which should support "--with-pcap".
Note that if any of the first 4 suggestions look as if they're not going
to be easy to do, you should probably take the 5th suggestion....
