Ethereal-dev: Re: [Ethereal-dev] Can't link Ethereal on Intel (Windows) based computer

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

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next
From: Guy Harris <gharris@xxxxxxxxx>
Date: Wed, 12 Jun 2002 00:50:25 -0700
On Tue, Jun 11, 2002 at 05:37:04PM +0200, andreas.sikkema@xxxxxxxxxxx wrote:
> 1. Your build environment (paths etc) is in a bad state
> 2. There was an error in building the wiretap library. 

Or perhaps

3. There was an error in the Ethereal source, fixed by this checkin:

  From: Gilbert Ramirez <gram@xxxxxxxxxxxxxxxxxxx>
  To: ethereal-cvs@xxxxxxxxxxxx
  Subject: [Ethereal-cvs] cvs commit: ethereal/wiretap config.h.win32 libpcap.c

  gram        2002/06/10 10:45:30 CDT

    Modified files:
      wiretap              config.h.win32 libpcap.c 
    Log:
    Add   #define HAVE_PCAP_H  1  to config.h.win32.
    In libpcap.c, move wtap_pcap_encap_to_wtap_encap before libpcap_open
    so that if HAVE_PCAP_H is not true, the file will still compile.
  
    Revision  Changes    Path
    1.9       +2 -1      ethereal/wiretap/config.h.win32
    1.77      +13 -12    ethereal/wiretap/libpcap.c

> Maybe removing all the .obj files from the wirteap direcotry and 
> rebuilding Ethereal would help?

...and, after that, doing a "cvs update" to get the current version of
the source and, just to make sure, removing "config.h" from the
"wiretap" directory so that Makefile.nmake copies
"wiretap/config.h.win32" to "wiretap/config.h".