From: "Jakub Kądziołka" <kuba@kadziolka.net>
To: Marius Bakke <marius@gnu.org>
Cc: 41596@debbugs.gnu.org
Subject: bug#41596: [staging] 'librsvg-next' build failure
Date: Fri, 29 May 2020 15:37:36 +0200 [thread overview]
Message-ID: <20200529133735.3gn7e3as3r3lg4wb@gravity> (raw)
In-Reply-To: <87r1v2518g.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1109 bytes --]
On Fri, May 29, 2020 at 03:17:51PM +0200, Marius Bakke wrote:
> On the 'staging' branch, "librsvg-next" (a dependency of GNOME) fails to
> compile the 'xml-rs' Rust crate:
>
> --8<---------------cut here---------------start------------->8---
> Compiling xml-rs v0.8.1
> error[E0658]: `cfg(doctest)` is experimental and subject to change
> --> /tmp/guix-build-librsvg-2.46.4.drv-0/librsvg-2.46.4/vendor/rust-xml-rs-0.8.1.tar.gz/src/lib.rs:9:7
> |
> 9 | #[cfg(doctest)]
> | ^^^^^^^
> |
> = note: for more information, see https://github.com/rust-lang/rust/issues/62210
That's a feature that was stabilized in Rust 1.40. I have a WIP patch
that updates Rust upto 1.43.1, but it's blocked on a LLVM 9 patch backport I
haven't had time to prepare yet. I won't have the time to look into it
properly right now, but here are the relevant links:
https://github.com/rust-lang/llvm-project/commit/7d5e7c023053660ffe494d72ce471e48ecc7f49b
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959877
https://github.com/rust-lang/llvm-project/pull/43
Regards,
Jakub Kądziołka
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-05-29 13:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 13:17 bug#41596: [staging] 'librsvg-next' build failure Marius Bakke
2020-05-29 13:37 ` Jakub Kądziołka [this message]
2020-05-30 20:23 ` Efraim Flashner
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=20200529133735.3gn7e3as3r3lg4wb@gravity \
--to=kuba@kadziolka.net \
--cc=41596@debbugs.gnu.org \
--cc=marius@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.