Fanteria / todotxt-tui

Todo.txt TUI - Terminal-based Todo Task Manager
MIT License
5 stars 1 forks source link

Installation error #4

Closed inigosola closed 1 month ago

inigosola commented 1 month ago

I get the followig error when I run cargo build command:

$ cargo build --release
warning: only one of `license` or `license-file` is necessary
`license` should be used if the package license can be expressed with a standard SPDX expression.
`license-file` should be used if the package uses a non-standard license.
See https://doc.rust-lang.org/cargo/reference/manifest.html#the-license-and-license-file-fields for more information.
    Updating crates.io index
warning: spurious network error (3 tries remaining): [35] SSL connect error (schannel: next InitializeSecurityContext failed: CRYPT_E_NO_REVOCATION_CHECK (0x80092012) - La funci�n de revocaci�n no puede comprobar la revocaci�n para el certificado.)
warning: spurious network error (2 tries remaining): [35] SSL connect error (schannel: next InitializeSecurityContext failed: CRYPT_E_NO_REVOCATION_CHECK (0x80092012) - La funci�n de revocaci�n no puede comprobar la revocaci�n para el certificado.)
warning: spurious network error (1 tries remaining): [35] SSL connect error (schannel: next InitializeSecurityContext failed: CRYPT_E_NO_REVOCATION_CHECK (0x80092012) - La funci�n de revocaci�n no puede comprobar la revocaci�n para el certificado.)
error: failed to get `chrono` as a dependency of package `todotxt-tui v0.1.0 (C:\Users\XXX\Downloads\todotxt-tui-main\todotxt-tui-main)`

Caused by:
  download of config.json failed

Caused by:
  failed to download from `https://index.crates.io/config.json`

Caused by:
  [35] SSL connect error (schannel: next InitializeSecurityContext failed: CRYPT_E_NO_REVOCATION_CHECK (0x80092012)

Solved runing instalation command with a specific environment variable: CARGO_HTTP_CHECK_REVOKE=false cargo build --release'

New errors:

error: failed to run custom build command for `windows_x86_64_msvc v0.52.5`

Caused by:
  could not execute process `C:\Users\XXX\Downloads\todotxt-tui-main\todotxt-tui-main\target\release\build\windows_x86_64_msvc-41baa4e544091d4c\build-script-build` (never executed)

Caused by:
  Acceso denegado. (os error 5)
warning: build failed, waiting for other jobs to finish...
error: failed to run custom build command for `parking_lot_core v0.9.10`

Caused by:
  could not execute process `C:\Users\XXX\Downloads\todotxt-tui-main\todotxt-tui-main\target\release\build\parking_lot_core-d2bfa95b7f3da8df\build-script-build` (never executed)

Caused by:
  Acceso denegado. (os error 5)
error: failed to run custom build command for `serde v1.0.203`

Caused by:
  could not execute process `C:\Users\XXX\Downloads\todotxt-tui-main\todotxt-tui-main\target\release\build\serde-3ac1af10d854ba50\build-script-build` (never executed)

Caused by:
  Acceso denegado. (os error 5)
error: failed to run custom build command for `proc-macro2 v1.0.85`

Caused by:
  could not execute process `C:\Users\XXX\Downloads\todotxt-tui-main\todotxt-tui-main\target\release\build\proc-macro2-6642c3a79f68368c\build-script-build` (never executed)

Caused by:
  Acceso denegado. (os error 5)
error: failed to run custom build command for `winapi v0.3.9`

Caused by:
  could not execute process `C:\Users\XXX\Downloads\todotxt-tui-main\todotxt-tui-main\target\release\build\winapi-0c1dbfbca3078e01\build-script-build` (never executed)

Caused by:
  Acceso denegado. (os error 5)
inigosola commented 1 month ago

Solved!

CARGO_HTTP_CHECK_REVOKE=false cargo build --release'

... but new errors added to initial post.

Fanteria commented 1 month ago

Isn't it a problem that the antivirus marked it as malware? Can you please check if the solution provided here helps you: https://github.com/AppFlowy-IO/AppFlowy/issues/2045

If not, I will try to install Windows on a VM and replicate the issue.

inigosola commented 1 month ago

Yeah! You are right. Antivirus was the problem.