Wireshark · Wireshark-dev: Re: [Wireshark-dev] Release 00.99.4 missing file?

["Robert Trybis" <rt@xxxxxxxxxxxxx>]

Okay, I think I have finally got a clean run through the build.
The nmake seems to have run to completion without errors and I can see;
	12/11/2006  14:58           135,056 capinfos.exe
	12/11/2006  14:58           268,732 dumpcap.exe
	12/11/2006  14:58           162,020 editcap.exe
	12/11/2006  14:58           131,808 mergecap.exe
	12/11/2006  14:58            84,244 randpkt.exe
	12/11/2006  14:37            69,684 rdps.exe
	12/11/2006  14:58           145,272 text2pcap.exe
	12/11/2006  14:58           588,240 tshark.exe
	12/11/2006  14:58         3,202,920 wireshark-gtk2.exe
	12/11/2006  14:55         3,069,976 wireshark.exe

Because I had been having problems with the build I started executing
the build from within PFE (Programmer's File Editor) as an easy way to
capture and examine the build output. This seemed a harmless thing to do
as PFE appears to open a Command window and execute the commands.
However it looks as if running the build in that way does not behave in
exactly the same way as running the build directly in a Command window.

Anyway, main problem build problems solved - now onto why the exe does
not find the dlls.

Thanks for all the help
RT

> -----Original Message-----
> From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-
> bounces@xxxxxxxxxxxxx] On Behalf Of Bill Florac
> Sent: 08 November 2006 21:57
> To: Developer support list for Wireshark
> Subject: Re: [Wireshark-dev] Release 00.99.4 missing file?
> 
> The "cd.." will make epan would working directory. So it copies the
> mkstemp.c and strptime.c files from the root directory to the epan
> directory.  (Odd but it does not copy the header file)  I confimed
this
> by deleting the files in epan, and the script copied them again.
> 
> So, by deduction, it seems you are missing these files.  They do not
> seem to be self-generated so you should find them in your
> C:\wireshark_source_00_99_4\ directory.  They are in the SVN version
> sytem so you should have them.
> 
> Bill
> 
> 
> 
> -----Original Message-----
> From: wireshark-dev-bounces@xxxxxxxxxxxxx
> [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Robert
Trybis
> Sent: Wednesday, November 08, 2006 3:33 PM
> To: Developer support list for Wireshark
> Subject: Re: [Wireshark-dev] Release 00.99.4 missing file?
> 
> Bill,
> 
> Here is what I got in the build output;
> 	cd ..
> 	..\tools\lemon\lemon t=..\tools\lemon\lempar.c dtd_grammar.lemon
> 	flex -odtd_parse.c dtd_parse.l
> 	flex -odtd_preparse.c dtd_preparse.l
> 	flex radius_dict.l
> 	xcopy ..\mkstemp.c . /d
> 	xcopy ..\strptime.c . /d
> 
> Can you confirm which directories the two files appear in on your
> system?
> 
> Regards
> RT
> 
> 
> > -----Original Message-----
> > From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-
> > bounces@xxxxxxxxxxxxx] On Behalf Of Bill Florac
> > Sent: 08 November 2006 16:22
> > To: Developer support list for Wireshark
> > Subject: Re: [Wireshark-dev] Release 00.99.4 missing file?
> >
> > I think you need to look further back into the nmake output. You
> should
> > see this:
> >
----------------------------------------------------------------------
> >         cd ..
> >         ..\tools\lemon\lemon t=..\tools\lemon\lempar.c
> dtd_grammar.lemon
> >         flex -odtd_parse.c dtd_parse.l
> >         flex -odtd_preparse.c dtd_preparse.l
> >         flex radius_dict.l
> >         xcopy ..\mkstemp.c . /d
> > ..\mkstemp.c
> > 1 File(s) copied
> >         xcopy ..\strptime.c . /d
> > ..\strptime.c
> > 1 File(s) copied
> >
----------------------------------------------------------------------
> > It may give you a clue as to what is going wrong. You could just
copy
> > the two file by hand...
> >
> > Bill
> >
> >
> >
> > -----Original Message-----
> > From: wireshark-dev-bounces@xxxxxxxxxxxxx
> > [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Robert
> Trybis
> > Sent: Wednesday, November 08, 2006 10:10 AM
> > To: Developer support list for Wireshark
> > Subject: Re: [Wireshark-dev] Release 00.99.4 missing file?
> >
> > I have got the path correct for XCOPY, I get "invalid number of
> > parameters" if I run it from the command line.
> >
> > Could I move mkstemp.c and strptime.c , by hand - where should I put
> > them?
> > I feel I am very close to getting this working.
> >
> > Regards
> > RT
> >
> >
> > > -----Original Message-----
> > > From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-
> > > bounces@xxxxxxxxxxxxx] On Behalf Of Lars Ruoff
> > > Sent: 08 November 2006 15:15
> > > To: Developer support list for Wireshark
> > > Subject: Re: [Wireshark-dev] Release 00.99.4 missing file?
> > >
> > > is xcopy in the PATH?
> > > On the command line type xcopy.
> > > The PATH to add on WinXP might be C:\WINNT\system32\ instead of
> > > C:\Windows\system32\
> > >
> > > Lars
> > >
> > > Robert Trybis wrote:
> > > > I am in C:\Program Files\wireshark which is where I installed
the
> > > > sources using SVN and I am using the commands you mentioned;
> > > > 	nmake -f Makefile.nmake distclean
> > > > 	nmake -f Makefile.nmake all
> > > >
> > > > The files mkstemp.c and strptime.c both exist in C:\Program
> > > > Files\Wireshark
> > > >
> > > > Regards
> > > > RT
> > > >
> > > >> -----Original Message-----
> > > >> From: wireshark-dev-bounces@xxxxxxxxxxxxx
[mailto:wireshark-dev-
> > > >> bounces@xxxxxxxxxxxxx] On Behalf Of Ulf Lamping
> > > >> Sent: 08 November 2006 13:47
> > > >> To: Developer support list for Wireshark
> > > >> Subject: Re: [Wireshark-dev] Release 00.99.4 missing file?
> > > >>
> > > >> Robert Trybis wrote:
> > > >>> I have tried again after deleting the wireshark directory and
> > > > getting a
> > > >>> clean copy of 00.99.4. Under XP the build ends prematurely
with
> > the
> > > >>> lines given below.
> > > >>>
> > > >>>
> > > >> Both files should be copied by epan\Makefile.nmake:
> > > >>
> > > >> mkstemp.c: ..\mkstemp.c
> > > >>     xcopy ..\mkstemp.c . /d
> > > >>
> > > >> I don't know what's going wrong here.
> > > >>
> > > >> What commands do you use?
> > > >>
> > > >> It should be enough to call the following in the *sources root
> > dir*:
> > > >>
> > > >> nmake -f Makefile.nmake distclean nmake -f Makefile.nmake all>
>
> > > >> Any ideas why these files appear
> to
> > be
> > > > missing and how to work round it?
> > > >>> I did not go through the process of doing the automated
library
> > > > download
> > > >>> again, but presumably I should not have to do that?
> > > >>>
> > > >> No, that won't help.
> > > >>> Regards
> > > >>> RT
> > > >>>
> > > >>> Generating Code...
> > > >>> Compiling...
> > > >>> tap.c
> > > >>> tap.c(284) : warning C4090: 'return' : different 'const'
> > qualifiers
> > > >>> tcap-persistentdata.c
> > > >>> tcap-persistentdata.c(988) : warning C4101: 'ti' :
unreferenced
> > > > local
> > > >>> variable
> > > >>> timestamp.c
> > > >>> to_str.c
> > > >>> tvbparse.c
> > > >>> tvbuff.c
> > > >>> unicode-utils.c
> > > >>> value_string.c
> > > >>> xdlc.c
> > > >>> xmlstub.c
> > > >>> inet_aton.c
> > > >>> inet_pton.c
> > > >>> inet_ntop.c
> > > >>> mkstemp.c
> > > >>> fatal error C1083: Cannot open source file: 'mkstemp.c ': No
> such
> > > > file or
> > > >>> directory
> > > >>> strptime.c
> > > >>> fatal error C1083: Cannot open source file: 'strptime.c': No
> such
> > > > file
> > > >>> or directory
> > > >>> Generating Code...
> > > >>> NMAKE : fatal error U1077: 'cl' : return code '0x2'
> > > >>> Stop.
> > > >>> NMAKE : fatal error U1077:
> > 'C:\PROGRA~1\MICROS~4\VC98\BIN\NMAKE.EXE'
> > > > :
> > > >>> return code '0x2'
> > > >>> Stop.
> > > >>> _______________________________________________
> > > >>> Wireshark-dev mailing list
> > > >>> Wireshark-dev@xxxxxxxxxxxxx
> > > >>> http://www.wireshark.org/mailman/listinfo/wireshark-dev
> > > >>>
> > > >> _______________________________________________
> > > >> Wireshark-dev mailing list
> > > >> Wireshark-dev@xxxxxxxxxxxxx
> > > >> http://www.wireshark.org/mailman/listinfo/wireshark-dev
> > > > _______________________________________________
> > > > Wireshark-dev mailing list
> > > > Wireshark-dev@xxxxxxxxxxxxx
> > > > http://www.wireshark.org/mailman/listinfo/wireshark-dev
> > > _______________________________________________
> > > Wireshark-dev mailing list
> > > Wireshark-dev@xxxxxxxxxxxxx
> > > http://www.wireshark.org/mailman/listinfo/wireshark-dev
> > _______________________________________________
> > Wireshark-dev mailing list
> > Wireshark-dev@xxxxxxxxxxxxx
> > http://www.wireshark.org/mailman/listinfo/wireshark-dev
> > _______________________________________________
> > Wireshark-dev mailing list
> > Wireshark-dev@xxxxxxxxxxxxx
> > http://www.wireshark.org/mailman/listinfo/wireshark-dev
> _______________________________________________
> Wireshark-dev mailing list
> Wireshark-dev@xxxxxxxxxxxxx
> http://www.wireshark.org/mailman/listinfo/wireshark-dev
> _______________________________________________
> Wireshark-dev mailing list
> Wireshark-dev@xxxxxxxxxxxxx
> http://www.wireshark.org/mailman/listinfo/wireshark-dev