[Brian Oleksa <oleksab@xxxxxxxxxxxxxxxxxxxxxx>]

Graham

What is weird about the hole thing is that I kept my "old" sources in 
tact just in case the new sources blow up (like they did).

I can still build the old sources using the current set up on this same 
machine.

Plus I can also run "verify tools" with no problem with the new source 
code...but as soon as I build it....it blows up.

I am hoping wireshark is not that finicky between different source 
trees...???

I guess I will take you advice and uninstall perl and reinstall it (or 
something).....but again....the perl that is installed works fine with 
my older source tree build....
so why wouldn't it work fine with they new source tree build...????

I followed the directions to the "T" other than reinstalling all the 
apps again...(like perl, python, cygwin...etc)...as there should not be 
a need to as they do indeed already work.

Just wanted to see what your thoughts where before I start messing with 
things that appear to be working correctly.

Thanks,
Brian



Graham Bloice wrote:
> Brian Oleksa wrote:
> > I was wondering if somebody can give me a hand here...????
> >
> > I can verify the tools, I can run setup.....but when I build...I am 
> > getting the following error:
> >
> >         "C:\Python26\python.exe" rdps.py print.ps ps.c
> >         rm -f svnversion.h
> >         perl make-version.pl
> > Version configuration file version.conf not found.  Using defaults.
> > This is a build from SVN (or a SVN snapshot).
> >       5 [main] perl 276 child_copy: linked dll data write copy failed, 0xBD2000.
> > .0xBD2370, done 0, windows pid 276, Win32 error 487
> >
> > I tried this work around...but it still fails.
> > http://www.wireshark.org/lists/wireshark-dev/200804/msg00088.html
> >
> > Any help is greatly appreciated.
> >
> > Thanks,
> > Brian
> >
> >   
> I think your build environment is messed up somewhere involving perl.  
> I think you need to go back to the beginning and re-create your build 
> environment exactly as described in the developers guide.  When you 
> can build successfully with win32, then you can go on to the x64 
> build.  I've never needed any of these "fixes" to the build 
> environment, but then I run a vanilla English Vista x64 system.
>
> Note that you can't just compile the win32, then the x64 versions 
> without cleaning up all the objects produced for the other machine 
> type.  You need to run "nmake -f Makefile.nmake distclean" in between 
> build attempts of different machine types.
>
> --
> Regards,
>
> Graham Bloice
> ------------------------------------------------------------------------
>
> ___________________________________________________________________________
> Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
> Archives:    http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
>              mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe