Thanks Bill. Bug 4356 was logged.
Your assumption was correct, I was unclear. I built an installer for my build of wireshark using NSIS, then installed wireshark and ran to no avail; the MSVCR71.dll error still appeared.
On Sat, Dec 26, 2009 at 3:59 PM, Bill Meier
<wmeier@xxxxxxxxxxx> wrote:
Matt Miling wrote:
> I built wireshark using MSVC 2008 Express Edition and specified
> MSVC_VARIANT=MSVC2008EE in config.nmake. I then ran wireshark.exe from the
> wireshark-gtk2 directory and received an "Unable To Locate Component" error
> dialog:
>
> "The application has failed to start because MSVCR71.dll was not found.
> Re-installing the application may fix the problem."
>
> After installing wireshark using nsis, I received the same error.
>
> I verified that msvcr90.dll is installed properly.
>
> As a test, I obtained a copy of MSVCR71.dll and put it in the same directory
> as wireshark.exe, and wireshark ran, but that's cheating. I'd like to run
> against msvcr90.dll
>
development version of Wireshark I see that msvcr71.dll is needed by
krb5_32.dll and two DLLs upon which krb5_32 dll depends.
I'm no expert on Windows dependencies but I do see that the kfw
(kerberos for windows ?) library package was recently changed in the
WIN32 libraries for Wireshark.
See
http://anonsvn.wireshark.org/viewvc?view=rev&root=Wireshark-win32-libs&revision=293
"
Author: gerald
Date: Wed Dec 23 00:02:08 2009 UTC (3 days, 20 hours ago)
Log Message:
Drop the locally-compiled kfw package in favor of MIT's.
"
I expect this is the reason why MSVCR71 is now required.
This sounds like a bug; I'll leave it to Gerald Coombs to determine how
this should be dealt with.
I suggest filing a bug (bugzilla.wireshark.org) so it doesn't get lost.
Also: re:
> After installing wireshark using nsis, I received the same error.
I assume you mean installing the Wireshark veresion you built...
Bill Meier