["Greg Morris" <GMORRIS@xxxxxxxxxx>]

That was it... Thanks, Ed...

 

Greg

>>> "Ed Meaney" <emeaney@xxxxxxxxx> 06/12/02 01:05PM >>>

Greg,

 

I ran across this last night as well.  wtap_process_pcap_packet needs to be added to wtap.def  to be exported.

 

Ed

 

 

 

-----Original Message-----
From: ethereal-dev-admin@xxxxxxxxxxxx [mailto:ethereal-dev-admin@xxxxxxxxxxxx] On Behalf Of Greg Morris
Sent: Wednesday, June 12, 2002 11:41 AM
To: andreas.sikkema@xxxxxxxxxxx; gharris@xxxxxxxxx
Cc: ethereal-dev@xxxxxxxxxxxx
Subject: Re: [Ethereal-dev] Can't link Ethereal on Intel (Windows)based computer

 

Guy,

 

I have been building Ethereal for well over 6 months now without any problems. So I don't anticipate my build environment is bad. The problem only started occurring after the Monday CVS update. I have built the wiretap directory independently and do not receive any errors after Gilberts update. Gilbert had made the update due to my build problems. He thought that his changes would correct the problems. It did correct the build but as you can see I am still having problems with the link process. I know that the function wtap_process_pcap_packet is contained in the libpcap.c file. I also know that you checked in a fix last week for this file. I suspect that the changes are what are causing my errors. I am not sure but I went back through my emails to find any changes to this file and those were the last changes before I started having problems. I have deleted the "obj, dll, and lib" files from my build and also performed a nmake makefile.nmake -clean without any success. If you have any insight on this issue it would be greatly appreciated. I was wanting to make some more changes to the NCP decodes but have been unable to build to test....

 

 

 

Greg Morris
gmorris@xxxxxxxxxx
Novell Technical Support (WSS/GRT Client)
Novell, Inc., the leading provider of Net services software

>>> Guy Harris <gharris@xxxxxxxxx> 06/12/02 01:50AM >>>
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".