Rust compiler is required on Windows #313

New Issue

SrChanning · 2023-07-24T04:07:01Z

SrChanning commented

2023-07-24 04:07:01 +00:00

This should probably be mentioned somewhere in the installation instructions. When running the ./setup_cuda.bat script on Windows, the install will yield errors when trying to compile the tokenizers module, which apparently requires the Rust compiler to be manually installed beforehand.

Running it without the Rust compiler will not cause the setup script to fail, but will cause the start.bat script to fail due to the tokenizer module not being installed correctly, in turn causing the tortoise-tts to be missing.

The solution is to install the Rust compiler and both the Python and C++ development workloads from the Visual Studio community installer.

This should probably be mentioned somewhere in the installation instructions. When running the ./setup_cuda.bat script on Windows, the install will yield errors when trying to compile the tokenizers module, which apparently requires the Rust compiler to be manually installed beforehand. Running it without the Rust compiler will not cause the setup script to fail, but will cause the start.bat script to fail due to the tokenizer module not being installed correctly, in turn causing the tortoise-tts to be missing. The solution is to install the Rust compiler and both the Python and C++ development workloads from the Visual Studio community installer.

mrq commented

2023-07-24 18:09:55 +00:00

Rust compiler is required on Windows

Absolutely disgusting. I'll re-validate the setup on my Windows machine, I'm pretty sure it does not have any compilers to use in the PATH outside of MSYS2/MinGW GCC, and I know Pip absolutely is stubborn about using that anyhow.

If anything, I think I'd have to freeze the tokenizers package from whatever's in my current venv: tokenizers==0.12.1.

> Rust compiler is required on Windows Absolutely disgusting. I'll re-validate the setup on my Windows machine, I'm pretty sure it does not have any compilers to use in the PATH outside of MSYS2/MinGW GCC, and I know Pip absolutely is stubborn about using that anyhow. If anything, I think I'd have to freeze the tokenizers package from whatever's in my current venv: `tokenizers==0.12.1`.

mrq commented

2023-07-24 18:12:20 +00:00

Strange, it (re)installed fine with the setup bat for me (left is my old venv, right is the new one).

Perhaps your pip wasn't able to fetch a precompiled wheel and instead had to compile it?

Strange, it (re)installed fine with the setup bat for me (left is my old venv, right is the new one). ![image](/attachments/be7890be-d376-4afd-bd29-2285d6d62f46) Perhaps your pip wasn't able to fetch a precompiled wheel and instead had to compile it?

image.png

60 KiB

NoM commented

2023-07-25 10:29:25 +00:00

It does work on windows in python 3.9-3.10, but it crashes on the regular.

I've had to run it entirely on Linux, as it's rocksolid on the same machine.

It does work on windows in python 3.9-3.10, but it crashes on the regular. I've had to run it entirely on Linux, as it's rocksolid on the same machine.

FergasunFergie commented

2023-09-05 06:46:39 +00:00

This is not true. I am running through a Powershell prompt with the venv. It is true I am using the same environment that I generated when I installed tortoise-tts. Were there a few errors and issues I had to debug? Yes, mostly related to installing newer packages.

Sign in to join this conversation.