From: ludo@gnu.org (Ludovic Courtès)
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel@gnu.org
Subject: Re: Getting ‘core-updates’ merged
Date: Sun, 25 Nov 2018 16:54:53 +0100 [thread overview]
Message-ID: <87sgzpw3si.fsf@gnu.org> (raw)
In-Reply-To: <20181124101949.38de8ba7@scratchpost.org> (Danny Milosavljevic's message of "Sat, 24 Nov 2018 10:19:49 +0100")
Hello Danny,
Danny Milosavljevic <dannym@scratchpost.org> skribis:
> On Fri, 23 Nov 2018 14:52:42 +0100
> ludo@gnu.org (Ludovic Courtès) wrote:
>
>> ------------------------------------------
>> LD_LIBRARY_PATH="/tmp/guix-build-rust-1.22.1.drv-0/rustc-1.22.1-src/build/x86_64-unknown-linux-gnu/test/run-make/issue-26092.stage2-x86_64-unknown-linux-gnu:/tmp/guix-build-rust-1.22.1.drv-0/rustc-1.22.1-src/build/x86_64-unknown-linux-gnu/stage2/lib:/tmp/guix-build-rust-1.22.1.drv-0/rustc-1.22.1-src/build/x86_64-unknown-linux-gnu/stage0-tools/x86_64-unknown-linux-gnu/release/deps:/tmp/guix-build-rust-1.22.1.drv-0/rustc-1.22.1-src/build/x86_64-unknown-linux-gnu/stage0-sysroot/lib/rustlib/x86_64-unknown-linux-gnu/lib:" '/tmp/guix-build-rust-1.22.1.drv-0/rustc-1.22.1-src/build/x86_64-unknown-linux-gnu/stage2/bin/rustc' --out-dir /tmp/guix-build-rust-1.22.1.drv-0/rustc-1.22.1-src/build/x86_64-unknown-linux-gnu/test/run-make/issue-26092.stage2-x86_64-unknown-linux-gnu -L /tmp/guix-build-rust-1.22.1.drv-0/rustc-1.22.1-src/build/x86_64-unknown-linux-gnu/test/run-make/issue-26092.stage2-x86_64-unknown-linux-gnu -o "" blank.rs 2>&1 | \
>> grep -i 'No such file or directory'
>
>> Danny, does that ring a bell?
>
> Yes, it's a known Rust bug. We've hit it before, see thread
> "Re: 01/03: llvm: Build with RTTI by default".
>
> Also see https://github.com/rust-lang/rust/issues/43402 (the fix is
> supposed to be in 1.22.1, though).
It seems that this bug is not fully resolved. Do you know how we could
skip it in the meantime?
Thanks,
Ludo’.
next prev parent reply other threads:[~2018-11-25 15:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 8:28 New release soon? swedebugia
2018-11-14 11:44 ` Ricardo Wurmus
2018-11-14 17:57 ` Marius Bakke
2018-11-16 18:10 ` Ludovic Courtès
2018-11-16 21:15 ` Ricardo Wurmus
2018-11-16 21:20 ` Ludovic Courtès
2018-11-16 22:03 ` Björn Höfling
2018-11-17 0:58 ` Gábor Boskovits
2018-11-17 14:14 ` Getting ‘core-updates’ merged Ludovic Courtès
2018-11-22 9:41 ` Ludovic Courtès
2018-11-22 19:54 ` Björn Höfling
2018-11-23 13:52 ` Ludovic Courtès
2018-11-23 21:44 ` Julien Lepiller
2018-11-24 9:19 ` Danny Milosavljevic
2018-11-25 15:54 ` Ludovic Courtès [this message]
2018-11-26 17:59 ` Danny Milosavljevic
2018-11-26 18:18 ` Danny Milosavljevic
2018-11-28 10:46 ` Ludovic Courtès
2018-11-26 17:54 ` Björn Höfling
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=87sgzpw3si.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=dannym@scratchpost.org \
--cc=guix-devel@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 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).