Wireshark-dev: Re: [Wireshark-dev] Release 00.99.4 missing file?
From: "Bill Florac" <bill.florac@xxxxxxxxxxxxxx>
Date: Wed, 8 Nov 2006 10:22:12 -0600
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
- Follow-Ups:
- Re: [Wireshark-dev] Release 00.99.4 missing file?
- From: Robert Trybis
- Re: [Wireshark-dev] Release 00.99.4 missing file?
- References:
- Re: [Wireshark-dev] Release 00.99.4 missing file?
- From: Robert Trybis
- Re: [Wireshark-dev] Release 00.99.4 missing file?
- Prev by Date: Re: [Wireshark-dev] Release 00.99.4 missing file?
- Next by Date: Re: [Wireshark-dev] Release 00.99.4 missing file?
- Previous by thread: Re: [Wireshark-dev] Release 00.99.4 missing file?
- Next by thread: Re: [Wireshark-dev] Release 00.99.4 missing file?
- Index(es):