From: "Daniel Sockwell" via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 57867@debbugs.gnu.org
Subject: bug#57867: Tealdeer build fails
Date: Sat, 17 Sep 2022 11:55:01 +0000 [thread overview]
Message-ID: <0b37b04494c2f19e679bc6765072884d@codesections.com> (raw)
In-Reply-To: <21_uKPbmYw9lk1dKRtNbk4d_vN2Qt9DmuQdJjlpa6oyEKD2Xn5Wp0OUQakLz5lLId2rDvMX0A__pFdEsZ-1nixsUoZ1Pyb5hO4eH1mHI5-c=@pm.me>
I have also run into this build failure.
The relevant error message from the build log appears to be:
Compiling openssl-macros v0.1.0
error[E0659]: `parse_quote_spanned` is ambiguous (`macro_rules` vs non-`macro_rules` from other module)
--> /tmp/guix-build-tealdeer-1.4.1.drv-0/tealdeer-1.4.1/guix-vendor/rust-pin-project-internal-0.4.22.tar.gz/src/pin_project/derive.rs:859:67
|
859 | proj_generics.make_where_clause().predicates.push(parse_quote_spanned! { span =>
| ^^^^^^^^^^^^^^^^^^^ ambiguous name
|
note: `parse_quote_spanned` could refer to the macro defined here
--> /tmp/guix-build-tealdeer-1.4.1.drv-0/tealdeer-1.4.1/guix-vendor/rust-pin-project-internal-0.4.22.tar.gz/src/utils.rs:22:1
|
22 | / macro_rules! parse_quote_spanned {
23 | | ($span:expr => $($tt:tt)*) => {
24 | | syn::parse2(quote::quote_spanned!($span => $($tt)*)).unwrap_or_else(|e| panic!("{}", e))
25 | | };
26 | | }
| |_^
note: `parse_quote_spanned` could also refer to the macro imported here
--> /tmp/guix-build-tealdeer-1.4.1.drv-0/tealdeer-1.4.1/guix-vendor/rust-pin-project-internal-0.4.22.tar.gz/src/pin_project/derive.rs:7:5
|
7 | *,
| ^
= help: use `self::parse_quote_spanned` to refer to this macro unambiguously
next prev parent reply other threads:[~2022-09-17 12:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 19:36 bug#57867: Tealdeer build fails Cairn via Bug reports for GNU Guix
2022-09-17 11:55 ` Daniel Sockwell via Bug reports for GNU Guix [this message]
2022-09-17 12:46 ` Maxime Devos
2023-01-05 18:00 ` Simon Tournier
2022-12-28 3:53 ` Corvo Liu
2022-12-29 11:19 ` Josselin Poiret via Bug reports for GNU Guix
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0b37b04494c2f19e679bc6765072884d@codesections.com \
--to=bug-guix@gnu.org \
--cc=57867@debbugs.gnu.org \
--cc=daniel@codesections.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).