Re: [Wireshark-dev] Win32 build error return code 0x66666666

2006-09-07 Thread Cook, Timothy
WS windir=C:\WINDOWS O:\wireshark-0.99.3a> -Tim > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > VOCAL Technologies, LTD > Sent: Thursday, September 07, 2006 9:23 AM > To: wireshark-dev@wireshark.org > Subject: [Wireshar

[Wireshark-dev] Win32 build error return code 0x66666666

2006-09-07 Thread VOCAL Technologies, LTD
I am building from the source distrobution 0.99.3 ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-dev

Re: [Wireshark-dev] Win32 build error return code 0x66666666

2006-09-07 Thread Cook, Timothy
D] > [mailto:[EMAIL PROTECTED] On Behalf Of > VOCAL Technologies, LTD > Sent: Thursday, September 07, 2006 8:53 AM > To: wireshark-dev@wireshark.org > Subject: [Wireshark-dev] Win32 build error return code 0x > > Thank you Tim, I reinstalled Cygwin tools, and I was able

[Wireshark-dev] Win32 build error return code 0x66666666

2006-09-07 Thread VOCAL Technologies, LTD
Thank you Tim, I reinstalled Cygwin tools, and I was able to compile, but am now unable to link. I checked my path to make sure I am using the MSVC linker, and I get this error: ftype-ipv4.c(108) : error C2065: 'fvalue_t_free_list' : undeclared identifier I am working on tracking this bug down,

Re: [Wireshark-dev] [Win32 build error return code 0x66666666]

2006-09-06 Thread Peter Johansson
VOCAL Technologies, LTD wrote: > Anders, > > yes, I am doing this all from a Cygwin window, and it appears that sed is > working properly. I am under the impression that there are things that I > still need to modify in config.nmake, which is causing path issues. > > Thanks, > > Hi Andy, you n

Re: [Wireshark-dev] [Win32 build error return code 0x66666666]

2006-09-06 Thread Graham Bloice
TED] Behalf Of Cook, Timothy > Sent: 06 September 2006 15:23 > To: [EMAIL PROTECTED]; Developer support list for Wireshark > Subject: Re: [Wireshark-dev] [Win32 build error return code 0x] > > > Do you intend to build using MSVC & CYGWIN tools? > Was your Win32 build

Re: [Wireshark-dev] [Win32 build error return code 0x66666666]

2006-09-06 Thread Cook, Timothy
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > VOCAL Technologies, LTD > Sent: Wednesday, September 06, 2006 10:15 AM > To: wireshark-dev@wireshark.org > Subject: Re: [Wireshark-dev] [Win32 build error return code > 0x666

Re: [Wireshark-dev] [Win32 build error return code 0x66666666]

2006-09-06 Thread VOCAL Technologies, LTD
Anders, yes, I am doing this all from a Cygwin window, and it appears that sed is working properly. I am under the impression that there are things that I still need to modify in config.nmake, which is causing path issues. Thanks, Andy ___ Wireshark

Re: [Wireshark-dev] Win32 build error return code 0x66666666

2006-09-06 Thread Anders Broman \(AL/EAB\)
Hi, Do you have the required Cygwin tools installed ( sed etc)? Brg Anders From: [EMAIL PROTECTED] on behalf of VOCAL Technologies, LTD Sent: Wed 9/6/2006 3:49 PM To: wireshark-dev@wireshark.org Subject: [Wireshark-dev] Win32 build error return code 0x

[Wireshark-dev] Win32 build error return code 0x66666666

2006-09-06 Thread VOCAL Technologies, LTD
OK, so I have traced my bug back a bit, and have found the source of the problem...the problem seens to be between Makefile.nmake and config.nmake... In Makefile.nmake, the section where config.h is constructed using sed, this seems to be where the build process fails. If I run the build, I get "