maidsafe / rust_sodium

This crate is no longer maintained. Looking for maintainers.
BSD 3-Clause "New" or "Revised" License
77 stars 34 forks source link

[Windows] File not found #38

Closed ffflorian closed 6 years ago

ffflorian commented 7 years ago

Hi MaidSafe, thanks to https://github.com/maidsafe/rust_sodium/pull/33 we are successfully building neon projects with libsodium cross-platform :slightly_smiling_face: ... well, almost.

When I try building rust_sodium in a Jenkins Windows job, I get the error "The system cannot find the path specified". On Linux and macOS there is no such problem... It is possible that this is a Jenkins error, but maybe you have an idea what this could be about?

Here is the full log:

[...]
Compiling rust_sodium-sys v0.2.0 (https://github.com/maidsafe/rust_sodium?rev=a1a17b261a0081b94e10179a11816c7894708f34#a1a17b26)
error: failed to run custom build command for `rust_sodium-sys v0.2.0 (https://github.com/maidsafe/rust_sodium?rev=a1a17b261a0081b94e10179a11816c7894708f34#a1a17b26)`
process didn't exit successfully: `C:\Users\jenkins\Documents\jenkins\workspace\Wrapper Windows Production\electron\node_modules\libsodium-neon\native\target\release\build\rust_sodium-sys-95df8c375f7de787\build-script-build` (exit code: 101)
--- stderr
thread 'main' panicked at '

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!   unwrap! called on Result::Err                                              !
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
C:\Users\jenkins\.cargo\git\checkouts\rust_sodium-55555f070d27ffcc\a1a17b2\rust_sodium-sys\build.rs:154,27 in build_script_build

Err(
    Error {
        repr: Os {
            code: 3,
            message: "The system cannot find the path specified."
        }
    }
)

', C:\Users\jenkins\.cargo\registry\src\github.com-1ecc6299db9ec823\unwrap-1.1.0\src\lib.rs:67
note: Run with `RUST_BACKTRACE=1` for a backtrace.

neon ERR! cargo build failed

Thanks in advance for your help!

ffflorian commented 6 years ago

Seems like this was a Jenkins error.