From: Brendan Tildesley <mail@brendan.scot>
To: 52072@debbugs.gnu.org
Subject: bug#52072: [core-updates-frozen] rust-bitflags 1.2.1 fails to build.
Date: Wed, 24 Nov 2021 04:43:55 +0100 (CET) [thread overview]
Message-ID: <1692331808.40671.1637725435027@office.mailbox.org> (raw)
starting phase `configure'
bitflags-1.2.1/.gitignore
bitflags-1.2.1/build.rs
bitflags-1.2.1/Cargo.toml.orig
bitflags-1.2.1/Cargo.toml
bitflags-1.2.1/CHANGELOG.md
bitflags-1.2.1/CODE_OF_CONDUCT.md
bitflags-1.2.1/LICENSE-APACHE
bitflags-1.2.1/LICENSE-MIT
bitflags-1.2.1/README.md
bitflags-1.2.1/src/example_generated.rs
bitflags-1.2.1/src/lib.rs
bitflags-1.2.1/.cargo_vcs_info.json
phase `configure' succeeded after 0.0 seconds
starting phase `patch-generated-file-shebangs'
phase `patch-generated-file-shebangs' succeeded after 0.0 seconds
starting phase `patch-cargo-checksums'
patch-cargo-checksums: generate-checksums for guix-vendor/rust-bitflags-1.2.1.crate
phase `patch-cargo-checksums' succeeded after 0.0 seconds
starting phase `build'
error: could not find `Cargo.toml` in `/tmp/guix-build-rust-bitflags-1.2.1.drv-0` or any parent directory
error: in phase 'build': uncaught exception:
%exception #<&invoke-error program: "cargo" arguments: ("build" "--release") exit-status: 101 term-signal: #f stop-signal: #f>
phase `build' failed after 0.0 seconds
command "cargo" "build" "--release" failed with status 101
next reply other threads:[~2021-11-24 3:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-24 3:43 Brendan Tildesley [this message]
2021-11-26 9:43 ` bug#52072: [core-updates-frozen] rust-bitflags 1.2.1 fails to build zimoun
2022-01-24 21:57 ` Brendan Tildesley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1692331808.40671.1637725435027@office.mailbox.org \
--to=mail@brendan.scot \
--cc=52072@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.