8000 time-macros fails with proc-macro = 0 despite being in proc-macro.nix · Issue #21 · oxalica/nocargo · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

time-macros fails with proc-macro = 0 despite being in proc-macro.nix #21

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

Open
therishidesai opened this issue Mar 7, 2024 · 0 comments

Comments

@therishidesai
Copy link
Contributor

I am getting this error when I have a project with the rust time crate:

error: builder for '/nix/store/rkrrfg6by2fbim5a7vqj22i3kiznrsxy-rust_time-macros-0.1.1.drv' failed with exit code 1;
       last 8 log lines:
       > Running phase: unpackPhase
       > unpacking source archive /nix/store/0066jydmydrgnmgw8n6id7ki4xx18did-crate-time-macros-0.1.1.tar.gz
       > source root is time-macros-0.1.1
       > setting SOURCE_DATE_EPOCH to timestamp 1601350743 of file time-macros-0.1.1/Cargo.toml
       > Running phase: patchPhase
       > Running phase: updateAutotoolsGnuConfigScriptsPhase
       > Running phase: configurePhase
       > Cargo.toml says proc-macro = 0 but it is built with procMacro = 1

But it is in proc-macro.nix here

@therishidesai therishidesai changed the title time-macro fails with proc-macro = 0 despite being in proc-macro.nix time-macros fails with proc-macro = 0 despite being in proc-macro.nix Mar 7, 2024
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
0