Cargo install for crate works on Linux but not on Windows

help
1

I published a crate, TALE that is a command line REPL for a scripting language I'm working on. When I run cargo install tale on Linux, it works as expected:

image
image563×158 3.75 KB

...
image
image1074×116 4.78 KB

But on Windows, I get this error:
image

The crate installs fine on both platforms if I specify the path to the local source code and build it that way.

2

maybe your cargo is outdated? or have you configured a mirror server for the crates-io registry?

3

rustup update shows everything is at latest:

stable-x86_64-pc-windows-msvc unchanged - rustc 1.86.0 (05f9846f8 2025-03-31)

I haven't changed any cargo settings from defaults.

I got my hands on a different windows machine to try it on today, same exact toolchain, and it worked fine on that one, so now I'm at even more of a loss for what could be the issue.

4

D:\ > cargo install tale
Updating crates.io index
Downloaded tale v0.1.0
...
Compiling tale_lib v0.1.0
Compiling tale v0.1.0
Finished release profile [optimized] target(s) in 1m 45s
Installing C:\Users\bcook.cargo\bin\tale.exe
Installed package tale v0.1.0 (executable tale.exe)

Built here.

D:\ > tale
-----+- Welcome to TALE! ---->
| Type a command to get started, 'help' if you're unsure what to do, or CTRL+C to exit.
TALE +->

Seems to run.

Some general information...

D:\ > rustup update
info: syncing channel updates for 'stable-x86_64-pc-windows-msvc'
info: syncing channel updates for 'nightly-x86_64-pc-windows-msvc'
info: checking for self-update
stable-x86_64-pc-windows-msvc unchanged - rustc 1.86.0 (05f9846f8 2025-03-31)
nightly-x86_64-pc-windows-msvc unchanged - rustc 1.89.0-nightly (7b84c9e9c 2025-05-10)
info: cleaning up downloads & tmp directories

5

I observed the same as you on Windows, with the same up-to-date stable version of Rust as you, although once the crate is installed / uninstalled, any later installation runs well (even if I erase the local cache, but I must have left some remnants).

To install it, I specified the path (I had cloned it first), but perhaps --bins works fine, too. Since I installed it the first time, I can't reproduce the problem. Is that the same for you?

On Linux, no problem at all.

I'm wondering if that's because it's a workspace; there were other reports of similar problems. But the fact it happens on Windows and not Linux is strange indeed.

PS: I also had to update cargo first on Linux because of the 2024 edition requirement; perhaps it's worth checking if you really need that.