Skip to content
This repository has been archived by the owner on Aug 3, 2023. It is now read-only.

README - Windows installation via cargo is missing external openssl dependency #1765

Closed
Kage-Yami opened this issue Feb 13, 2021 · 2 comments
Assignees
Labels

Comments

@Kage-Yami
Copy link

🐛 Bug Report

For installing wrangler on Windows via cargo, the README fails to mention that openssl is a runtime external dependency; only perl is mentioned as a compile-time external dependency.

Environment

  • operating system: Windows 10 19042
  • output of rustc -V: rustc 1.50.0 (cb75ad5db 2021-02-10)
  • output of node -v: Not installed
  • output of wrangler -V: Reported error shows / wrangler 1.13.0 after fixing
  • contents of wrangler.toml N/A

Steps to reproduce

  1. Install rustup - https://rustup.rs/
  2. Install scoop - https://scoop.sh/
  3. Install perl external dependency: scoop install perl
  4. Install wrangler: cargo install wrangler (which succeeds)
  5. Attempt to login: wrangler login (error appears)

The issue can be fixed by installing openssl external dependency: scoop install openssl

What did you expect to see?

The usual login message on the CLI:

Allow Wrangler to open a page in your browser? [y/n]

What did you see instead?

This error in a popup window (screenshot attached):

The code execution cannot proceed because libssl-1_1-x64.dll was not found. Reinstalling the program may fix this problem.

image

@koeninger
Copy link
Contributor

Starting from a fresh windows install, installing the VS C++ tools, rustup, and Strawberry Perl as recommended by https://www.perl.org/get.html works for me without having to explicitly install openssl. Perhaps there's something about the way scoop installs perl that it doesn't include openssl?

Assuming I'm reading correctly that scoop install openssl worked for you, I'll add a note to the readme.

koeninger pushed a commit that referenced this issue Feb 24, 2021
note about #1765
@Kage-Yami
Copy link
Author

Yup, additionally running scoop install openssl did the trick for me, so that update sounds good to me. 🙂

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants