From: Chris Marusich <cmmarusich@gmail.com>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Rust 1.19 fails to build on i686 on ‘staging’
Date: Wed, 13 Feb 2019 20:35:51 -0800 [thread overview]
Message-ID: <87a7izhtqw.fsf@gmail.com> (raw)
In-Reply-To: 87imxo9r0k.fsf@gmail.com
[-- Attachment #1.1: Type: text/plain, Size: 2797 bytes --]
Hi Danny,
Chris Marusich <cmmarusich@gmail.com> writes:
> Hi Danny,
>
>> Sounds good. I've successfully applied the patch to a clean checkout of
>> Guix at the current master branch head
>> (c7cf43ddec9be5389d3a2623d6414d9b55354f64). I've kicked off a build on
>> an x86_64-linux system (Guix running on a Debian foreign distro) via:
>>
>> guix environment --pure guix
>> # And then, in the pure environment:
>> ./bootstrap && ./configure --localstatedir=/var && make -j 1 && echo
>> built guix > /tmp/mylog && time ./pre-inst-env guix build --max-jobs=1
>> --cores=1 -K -s i686-linux rust@1.19.0
>>
>> It's gonna take a long time to finish. I'll let you know how it goes!
>
> The build failed because it ran out of memory. This machine won't work.
> I've started the build on another machine with more memory, and I'll let
> you know how it goes.
The build failed after 3 hours. I've attached the full build log. The
final bit was:
--8<---------------cut here---------------start------------->8---
Backtrace:
6 (primitive-load "/gnu/store/0q88w9lgl5maks0qcrymkcymv87…")
In ice-9/eval.scm:
191:35 5 (_ _)
In srfi/srfi-1.scm:
863:16 4 (every1 #<procedure 83625d0 at /gnu/store/w8ki740gbcib…> …)
In /gnu/store/w8ki740gbcibbifmljwjpd0vmix5jw8q-module-import/guix/build/gnu-build-system.scm:
799:28 3 (_ _)
In ice-9/eval.scm:
619:8 2 (_ #(#(#(#<directory (guile-user) 817e910>) (# # …) …) …))
In ice-9/boot-9.scm:
260:13 1 (for-each #<procedure 8bf0770 at ice-9/eval.scm:333:13…> …)
In /gnu/store/w8ki740gbcibbifmljwjpd0vmix5jw8q-module-import/guix/build/utils.scm:
616:6 0 (invoke _ . _)
/gnu/store/w8ki740gbcibbifmljwjpd0vmix5jw8q-module-import/guix/build/utils.scm:616:6: In procedure invoke:
Throw to key `srfi-34' with args `(#<condition &invoke-error [program: "output/rustc-build/rustc" arguments: ("-C" "linker=/gnu/store/mhkpjv29ssmr4cm71654x4c5gm40ncjb-gcc-5.5.0/bin/gcc" "-Z" "force-unstable-if-unmarked" "-L" "output/target-libs" "src/libcore/lib.rs" "-o" "output/target-libs/libcore.rlib") exit-status: #f term-signal: 8 stop-signal: #f] 8181580>)'.
--8<---------------cut here---------------end--------------->8---
My understanding is that "term-signal: 8" means the process (rustc) was
terminated by signal 8 (SIGFPE on my system according to "kill -l"). Is
that right?
I looked in the failed build directory, but I couldn't find a core
dump. When I manually ran the command...
/gnu/store/jxq[...]-mrustc-0.8.0/bin/mrustc src/tools/cargo/src/bin/cargo.rs [...]
...it actually succeeded.
Does this tell you anything useful? I will keep the build directory
around for now, so please let me know if you'd like me to check anything
else.
--
Chris
[-- Attachment #1.2: 49wkd7l2bk8yszgv9i0y6vr26k892l-rust-1.19.0.drv.bz2 --]
[-- Type: application/octet-stream, Size: 182963 bytes --]
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2019-02-14 4:36 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 14:39 Rust 1.19 fails to build on i686 on ‘staging’ Ludovic Courtès
2019-01-28 15:22 ` Danny Milosavljevic
2019-01-28 15:27 ` Danny Milosavljevic
2019-01-28 15:35 ` Danny Milosavljevic
2019-01-29 8:36 ` Ludovic Courtès
2019-01-30 17:59 ` Danny Milosavljevic
2019-02-05 11:28 ` Danny Milosavljevic
2019-02-05 11:35 ` Danny Milosavljevic
2019-02-11 21:34 ` Danny Milosavljevic
2019-02-12 11:47 ` Chris Marusich
2019-02-12 12:06 ` Danny Milosavljevic
2019-02-13 2:59 ` Chris Marusich
2019-02-13 5:49 ` Chris Marusich
2019-02-14 4:35 ` Chris Marusich [this message]
2019-02-14 17:14 ` Danny Milosavljevic
2019-02-15 9:11 ` Chris Marusich
2019-02-15 10:51 ` Danny Milosavljevic
2019-02-16 10:53 ` Chris Marusich
2019-02-18 14:38 ` Danny Milosavljevic
2019-05-24 13:55 ` Danny Milosavljevic
2019-07-19 5:53 ` Chris Marusich
2019-07-21 17:53 ` Ricardo Wurmus
2019-01-28 15:50 ` Danny Milosavljevic
2019-01-28 18:41 ` Ricardo Wurmus
2019-01-28 20:25 ` Danny Milosavljevic
2019-01-31 5:51 ` Mark H Weaver
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=87a7izhtqw.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--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).