Per my earlier mail, I have uninstalled Active Perl - but continue to see the same error. --Sunny
On Thu, Oct 16, 2008 at 5:00 PM, John Sullivan < [EMAIL PROTECTED]> wrote: > [resend - sorry if you get a dupe!] > > On Thursday, October 16, 2008, 10:22:48 PM, Anders Broman wrote: > > Gussing something with Perl? > > > Your path perl: /cygdrive/c/Perl/bin/perl > > > Mine: > > > perl: /usr/bin/perl do you have Cygwin Perl? > > Ooh, ooh! I might have an idea here: > > ActiveState ActivePerl currently installs itself under C:\Perl or > C:\Perl64 by default. > > cygwin installs itself wherever you tell it and does really funky > things to %PATH% to convert it into a sane $PATH. > > Normal Win32 binary paths under cygwin generally end up like the > former perl-path. > > Cygwin's own binaries generally end up like the latter (it aliases > /usr/bin to whatever its own genuine Win32 path actually is.) > > If you had *both* installed, and ActiveState was ahead in the Windows > search path, but for some reason the cygwin perl.exe was getting > executed for the pod2html (which is just a hashbang perl script), you > might end up executing random cygwin binaries under the ActiveState > environment. Both environments are pretty weird. They were weird and > incompatible the last time I tried several years back, and AFAICT > they've only got weirder since, cygwin particularly so. > > I find running one or the other on a particular machine, but not both, > to be the only reliable way. > > John > -- > Dead stars still burn > > _______________________________________________ > Wireshark-dev mailing list > [email protected] > https://wireshark.org/mailman/listinfo/wireshark-dev >
_______________________________________________ Wireshark-dev mailing list [email protected] https://wireshark.org/mailman/listinfo/wireshark-dev
