Ethereal-users: Re: [melan@xxxxxxxxxxxxxxxxxxxx: Re: [ethereal-users] Problems on IRIX6.5]

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

From: Guy Harris <guy@xxxxxxxxxx>
Date: Thu, 2 Dec 1999 19:25:17 -0800 (PST)
> Autoconf-problem/Ethereal device-problem on IRIX6.5:
> 
>   I'm using Autoconf version 2.12
>   tcpdump works fine and I compiled ethereal with the latest
>   release of libpcap (tcpdump was compiled with an older version).

Try compiling "tcpdump" with that version of "libpcap" as well; I'm
curious whether it works.

>   Ethereal complaints no ethernet device or insufficient permissions
>   even I'm running ethereal as root.

Hmm.  Perhaps the "ioctl"s it's doing to get the list of interfaces
don't work on Irix, or don't work the way they work elsewhere.

Just out of curiosity, what happens if you run "tcpdump" *without*
specifying a device on which to capture?  The "libpcap" code to pick the
first interface (which is the default interface) uses code similar to
what Ethereal uses to generate the list of interfaces.

>   If I use the configure script thats within the source code package
>   of ethereal there are no complaints about @LEXLIB@. But I have
>   to copy the pcap-includes to the places where the ethereal-configure
>   expects them to be.
> 
>   Where is there an entry like
>      AC_SUBS(SHELL)
>      SHELL=/bin/sh
>   in ethereal-configure.in /ethereal-aclocal.m4 ?

There isn't one.

It's generated by "autoconf".

>   The linux autoconf e.g does not automatically generate a subsition
>   for @SHELL@ too. So I guess it's not an autoconf-irix-problem.

It may be an Autoconf 2.12 problem:

	tooting$ autoconf --version
	Autoconf version 2.13

which is also what I'm running at home, and what I suspect Gilbert has
on the machine on which he generates the distribution tarballs.

If it doesn't work with 2.12, we should perhaps put an AC_PREREQ call
into "configure.in".  I'll try running 2.12 and see if there's a problem
and, if so, put

	AC_PREREQ(2.13)

into "configure.in".

I'll also look at providing "--with-XXX" flags for all the libraries we
use, and having the optional argument to those flags specify a directory
under which to look for headers and libraries.  (Unfortunately, Autoconf
doesn't provide much in the way of mechanisms for doing that....)