Andrew Clemons

Thanks, core built with c1d4b60 successfully now. It falls over on a subsequent crate though: ``` [....] BUILDING rand from rand v0.0.0 with features [] BUILDING term from term v0.0.0...

> Above failure fixed in 2315092 Confirmed. Thanks > current blocker is casting i128/u128 to f32 Also confirmed thanks. > MIR ERROR: ::to_f32 BB5/0: Bad i128/u128 cast

I've just tested with f4483c0. It gets further along, but fails with ``` make[1]: Leaving directory '/tmp/build_mrustc/mrustc-f4483c076291f6c13b44d67a7a8f824ea2fcc682' [RUSTC] -o prefix/lib/rustlib/x86_64-unknown-linux-gnu/lib/libcore.rlib error: int literal is too large --> ../rustc-1.19.0-src/src/libcore/num/f32.rs:25:24 | 25...

Thanks. I've checked here with GCC 5.5 and it failed too. ``` Makefile:37: recipe for target 'prefix/lib/rustlib/x86_64-unknown-linux-gnu/lib/libcore.rlib' failed ``` Valgrind says: ``` ==12316== Command: ../output/rustc -L prefix/lib/rustlib/x86_64-unknown-linux-gnu/lib/ -L ../output/libs ../rustc-1.19.0-src/src/libcore/lib.rs...

Right, I was building 346da186. I've now built 74c2ec9d with GCC 5.5.0. It fails with ``` [...] > /home/aclemons/slack-rust-bootstrap/mrustc/tmp/mrustc-74c2ec9d3c7eb09540a2a5de3127390fa8252179/bin/mrustc rustc-1.19.0-src/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...

Ok, dd4e3c88 builds again. Thanks.

Also fyi, dd4e3c8 does not currently finish on x86_64 (GCC 5.5) either. I'm getting a SIGABRT here: ``` [...] [RUSTC] -o prefix/lib/rustlib/x86_64-unknown-linux-gnu/lib/libcore.rlib Command terminated by signal 6 ```

(I'm using rbenv here): ``` $ gem install rails [...] $ rails new ruumba [...] $ cd ruumba $ echo "gem 'ruumba'" >> Gemfile $ bundle install $ bundle exec...

@matthewhively Just confirming you are passing in `-e` or `--disable-ruby-ext` when invoking ruumba? Otherwise all files will be renamed to blah.erb.rb when copying to the temp directory and that in...

Bump