[Imstk-developers] MD5 issue with libusb

[Dzenan Zukic]

Maybe some download was incomplete. Try deleting the downloaded file and
see if it is correctly re-downloaded when you configure.

Dženan Zukić, PhD, Senior R&D Engineer, Kitware (Carrboro, N.C.)

On Wed, Sep 27, 2017 at 4:34 PM, Milef, Nicholas Boris <milefn at rpi.edu>
wrote:

> What's strange is that I can download it (or rather CMake downloads it).
> The last update on SourceForge was in January, which was before the MD5
> hash was changed in iMSTK. The MD5 hash on SourceForge matches what's in
> the CMake file.
> ------------------------------
> *From:* Dzenan Zukic [dzenan.zukic at kitware.com]
> *Sent:* Wednesday, September 27, 2017 4:21 PM
> *To:* Milef, Nicholas Boris
> *Cc:* imstk-developers at imstk.org
> *Subject:* Re: [Imstk-developers] MD5 issue with libusb
>
> If SourceForge is not down or corrupted, they might have updated the .7z
> file which contains the source by some minor version. That is a plausible
> explanation for MD5 mismatch. Or an error in downloading. This is
> speculation, I haven't compiled iMSTK in a while.
>
> Dženan Zukić, PhD, Senior R&D Engineer, Kitware (Carrboro, N.C.)
>
> On Wed, Sep 27, 2017 at 4:05 PM, Milef, Nicholas Boris <milefn at rpi.edu>
> wrote:
>
>> Has anyone been having issues with libusb recently? I'm getting an MD5
>> mismatch. On Windows, it can't compile because of this (you would need to
>> do a new clone).
>>
>> _______________________________________________
>> Imstk-developers mailing list
>> Imstk-developers at imstk.org
>> http://public.kitware.com/mailman/listinfo/imstk-developers
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/imstk-developers/attachments/20170927/dd880650/attachment.html>