Wireshark-dev: Re: [Wireshark-dev] Problem with dev environment
From: Gregory Seidman <gsslist+wireshark@xxxxxxxxxxxxxxxxxx>
Date: Wed, 8 Dec 2010 11:44:34 -0500
I wound up solving the problem by setting up a VM for my dev environment
with nothing but what is required. Everything is now working. I expect it
was ActiveState Perl causing problems, but I depend on it for other things
on my workstation.

Thanks anyway,
--Greg

On Wed, Dec 08, 2010 at 04:02:00PM +0000, Christopher Maynard wrote:
> Gregory Seidman <gsslist+wireshark@...> writes:
> 
> > Note that I am working with the source for 1.2.1 (ugh, I know) because
> > that's what we're still using. Yes, I wish I could get on a more current
> > version, but for now I can't.
> 
> Can you try 1.4.2?  Not necessarily to deploy/use because apparently you can't,
> but just to see if your problem is indeed tied to the 1.2.x version or not.
> 
> > When I
> > try to actually build, however, it fails on the very first attempt to
> > compile something, which happens to be lemon. The error is 
> > 
> > LINK : fatal error LNK1104: cannot open file 'C:/Perl/lib,C:/Perl/site/lib,.'
> 
> Maybe post your environment (PATH, etc.) and full output following a distclean
> of the build leading up to the failure?
> 
> > I have ActiveState Perl installed on this machine, 
> 
> You could try to temporarily uninstall ActiveState Perl, just to see if this
> clears up the problem.  If it does, hopefully a reinstall of it won't
> reintroduce the problem.
> 
> Another thing you could check is the vcvarsall.bat and vcvars[arch].bat files. 
> Before lemon is compiled, the proper environment is set up by calling
> vcvarsall.bat which in turn calls vcvars[arch].bat where the PATH and other
> environment variables are set.  Perhaps there's some reference to Perl in yours
> somewhere?
> 
> 
> ___________________________________________________________________________
> 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
>