Re: Rust 1.19 fails to build on i686 on ‘staging’

Chris Marusich writes: > Danny Milosavljevic writes: > >> can we give thepowersgang (author of mrustc) an ssh account on a guix machine >> reachable from the internet, for debugging this problem? >> >> It would be good if "guix build -K" kept the sources on that machine. > > Is/are the

Re: Rust 1.19 fails to build on i686 on ‘staging’

Danny Milosavljevic writes: > can we give thepowersgang (author of mrustc) an ssh account on a guix machine > reachable from the internet, for debugging this problem? > > It would be good if "guix build -K" kept the sources on that machine. Is/are the thepowersgang still willing to help us out?

Re: Rust 1.19 fails to build on i686 on ‘staging’

Hi, can we give thepowersgang (author of mrustc) an ssh account on a guix machine reachable from the internet, for debugging this problem? It would be good if "guix build -K" kept the sources on that machine. Thanks! pgp_prUbn7rtD.pgp Description: OpenPGP digital signature

Re: Rust 1.19 fails to build on i686 on ‘staging’

Hi Chris, On Sat, 16 Feb 2019 02:53:30 -0800 Chris Marusich wrote: > > (i.e. the things you did before, just inside a i686-linux guix > > environment. That only provides minimal--almost no--isolation from > > the host, so it should allow us to test whether the personality is the > > only

Re: Rust 1.19 fails to build on i686 on ‘staging’

Hi Danny, Danny Milosavljevic writes: > Can you try the following (if you didn't already)? > > [...] > > (i.e. the things you did before, just inside a i686-linux guix > environment. That only provides minimal--almost no--isolation from > the host, so it should allow us to test whether the

Re: Rust 1.19 fails to build on i686 on ‘staging’

Hi Chris, On Fri, 15 Feb 2019 01:11:02 -0800 Chris Marusich wrote: > Here's more info about what I did. On my x86_64-linux Guix System > machine, where the build failed, I ran the following commands: > > --8<---cut here---start->8--- > cd

Re: Rust 1.19 fails to build on i686 on ‘staging’

Hi Danny, Danny Milosavljevic writes: > On Wed, 13 Feb 2019 20:35:51 -0800 > Chris Marusich wrote: > >> 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 >>

Re: Rust 1.19 fails to build on i686 on ‘staging’

Hi Chris, On Wed, 13 Feb 2019 20:35:51 -0800 Chris Marusich wrote: > 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? According to upstream [1], it might be SIGABRT, but I see your

Re: Rust 1.19 fails to build on i686 on ‘staging’

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

Re: Rust 1.19 fails to build on i686 on ‘staging’

Hi Danny, Danny Milosavljevic writes: >> > Would you have some time and a free computer to be able to build >> > rust 1.19.0 with >> > >> > ./pre-inst-env guix build -K -s i686-linux rust@1.19.0 >> > >> > on guix master with the patch below? >> >> I have a spare computer. It only has 2 GB

Re: Rust 1.19 fails to build on i686 on ‘staging’

Hi Chris, On Tue, 12 Feb 2019 03:47:53 -0800 Chris Marusich wrote: > > Would you have some time and a free computer to be able to build rust > > 1.19.0 with > > > > ./pre-inst-env guix build -K -s i686-linux rust@1.19.0 > > > > on guix master with the patch below? > > I have a spare

Re: Rust 1.19 fails to build on i686 on ‘staging’

Hi Danny, Danny Milosavljevic writes: > Hi Chris, > > upstream says that compiling rust 1.19.0 works fine for them on i686 with > their mrustc > master (since they have applied our variable-length integer decoding patch): > > https://github.com/thepowersgang/mrustc/issues/108 Good to hear

Re: Rust 1.19 fails to build on i686 on ‘staging’

Hi Chris, upstream says that compiling rust 1.19.0 works fine for them on i686 with their mrustc master (since they have applied our variable-length integer decoding patch): https://github.com/thepowersgang/mrustc/issues/108 >Hmm... works for me, using gcc (Debian 6.3.0-18+deb9u1) 6.3.0

Re: Rust 1.19 fails to build on i686 on ‘staging’

Chris and I compared what gets sent by the parent on i686 (where it breaks) vs on x86_64 (where it doesn't break): There are no differences. The next step will be to find out what the child process does with the data. I suspect that the child processes' input deserializer is broken. For

Re: Rust 1.19 fails to build on i686 on ‘staging’

Hi Ludovic, Ludovic Courtès writes: > Rust fails to build on i686 on ‘staging’, so I don’t know if it’s > deterministic (the “unexpected EOF” reminds me of parallel build issues > with half-baked makefiles): > > BUILDING crates_io from crates-io v0.9.0 with features [] >>

Re: Rust 1.19 fails to build on i686 on ‘staging’

Hi Ludo, running gdb in an i686 transparent qemu emulation gives me: $ gdb --args /gnu/store/gpc2m2f79rsgy15m65x0s5av7a41rp8b-mrustc-0.8.0/bin/mrustc src/tools/cargo/src/crates-io/lib.rs --crate-name crates_io --crate-type rlib --crate-tag 0_9_0 -g --cfg debug_assertions -O -o

Re: Rust 1.19 fails to build on i686 on ‘staging’

Hi Danny, Danny Milosavljevic skribis: > On Mon, 28 Jan 2019 15:39:33 +0100 > Ludovic Courtès wrote: >> > /gnu/store/fw4yy7cgb5ahs9s2ir00bawnsl5zj7db-mrustc-0.8.0/bin/mrustc[...] >> munmap_chunk(): invalid pointer > > Maybe the above causes > >> src/tools/cargo/src/crates-io/lib.rs:65:

Re: Rust 1.19 fails to build on i686 on ‘staging’

Hi Ricardo, On Mon, 28 Jan 2019 19:41:50 +0100 Ricardo Wurmus wrote: > Did you run “make clean-go” before? Nope. Did so now - the build of guix staging works now. Thanks! pgpaROXXhhog4.pgp Description: OpenPGP digital signature

Re: Rust 1.19 fails to build on i686 on ‘staging’

Danny Milosavljevic writes: > Something more serious seems to be up with guix staging because I get, > on trying "make" (after "./configure --localstatedir=/var") inside guix > staging > (commit df09e1d6e71f68a8fb44bcc9f13e625f9f9701a5) on x86_64: > > Backtrace: > In ice-9/boot-9.scm: >

Re: Rust 1.19 fails to build on i686 on ‘staging’

Something more serious seems to be up with guix staging because I get, on trying "make" (after "./configure --localstatedir=/var") inside guix staging (commit df09e1d6e71f68a8fb44bcc9f13e625f9f9701a5) on x86_64: Backtrace: In ice-9/boot-9.scm: 222:29 19 (map1 _) 222:29 18 (map1 _) 222:29

Re: Rust 1.19 fails to build on i686 on ‘staging’

Possible use-after free fix in mrustc commits: https://github.com/thepowersgang/mrustc/commit/a51eea542ae086687ea2c4cb09321785f5cc6269 This was not in the mrustc 0.8.0 release yet. pgp12KN34YAvz.pgp Description: OpenPGP digital signature

Re: Rust 1.19 fails to build on i686 on ‘staging’

Hi Ludo, on second thought: On Mon, 28 Jan 2019 15:39:33 +0100 Ludovic Courtès wrote: > > /gnu/store/fw4yy7cgb5ahs9s2ir00bawnsl5zj7db-mrustc-0.8.0/bin/mrustc[...] > munmap_chunk(): invalid pointer Maybe the above causes > src/tools/cargo/src/crates-io/lib.rs:65:

Re: Rust 1.19 fails to build on i686 on ‘staging’

Hi Ludo, > while reading from child process ^ Is that a real Pentium, or qemu on x86_64? We had some problems with spawning child processes on the qemu transparent emulator. pgphnzPYl3GKD.pgp Description: OpenPGP digital signature

Rust 1.19 fails to build on i686 on ‘staging’

Hello, Rust fails to build on i686 on ‘staging’, so I don’t know if it’s deterministic (the “unexpected EOF” reminds me of parallel build issues with half-baked makefiles): --8<---cut here---start->8--- BUILDING crates_io from crates-io v0.9.0 with features []