Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

getting file/folder permission issue when building #321

Open
rouzwelt opened this issue Jan 5, 2024 · 0 comments
Open

getting file/folder permission issue when building #321

rouzwelt opened this issue Jan 5, 2024 · 0 comments

Comments

@rouzwelt
Copy link

rouzwelt commented Jan 5, 2024

the build fails with this error for a dependency (revm primitives crate):

error: builder for '/nix/store/z0x30jyj4ylx5lnb98xm02jfwyl6swzv-dotrain-deps-0.0.0.drv' failed with exit code 101;
       last 10 log lines:
       >   process didn't exit successfully: `/private/tmp/nix-build-dotrain-deps-0.0.0.drv-0/dummy-src/target/release/build/revm-primitives-0876dbd51a56ccdf/build-script-build` (exit status: 101)
       >   --- stdout
       >   cargo:rerun-if-changed=src/kzg/trusted_setup.txt
       >
       >   --- stderr
       >   thread 'main' panicked at /sources/revm-primitives-1.3.0-51187b852d9e458816a2e19c81f1dd6c924077e1a8fccd16e4f044f865f299d7/build.rs:64:73:
       >   called `Result::unwrap()` on an `Err` value: Os { code: 13, kind: PermissionDenied, message: "Permission denied" }
       >   note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
       > warning: build failed, waiting for other jobs to finish...
       > [naersk] cargo returned with exit code 101, exiting
       For full logs, run 'nix log /nix/store/z0x30jyj4ylx5lnb98xm02jfwyl6swzv-dotrain-deps-0.0.0.drv'.
error: 1 dependencies of derivation '/nix/store/afpsaq2i3y7xzajchd7iffvlqjg075p9-dotrain-0.0.0.drv' failed to build

looks like it is a permission issue of file/folders that need to be set correctly during buildPhase/configurePhase.
I should mention that building with makerustPlatform works with no issue, so I assume this is only something within naersk configs. it would be good to get a fix for this

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

No branches or pull requests

1 participant