Hi all,

I just checked out the git master and followed the instructions to
configure/build with llvm. It successfully builds the vm and then the
below happens.

Is master the correct branch? I assume with llvm is the bleeding edge?

Cheers,

Mark.

PS: I love the auto-download of pre-built llvm. Saves a lot of compile
time and reduces the concern about an incompatible llvm revision.

vm/test/runner
Running 723
tests...................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................OK!
bin/mspec ci -B full --background
VM Assertion:
  set RBX_RUNTIME to runtime (or equiv)

2   rbx  0x0000000100051725 rubinius::VMException::VMException(char
const*, bool) + 101
3   rbx  0x0000000100182acb main + 651
4   rbx  0x0000000100010b08 start + 52
5   ???  0x0000000000000006 0x0 + 6

Ruby backtrace:
Abort!
2   rbx  0x0000000100051c66 rubinius::abort() + 54
3   rbx  0x0000000100183118 main + 2264
4   rbx  0x0000000100010b08 start + 52
5   ???  0x0000000000000006 0x0 + 6
Assertion failed: (0), function abort, file vm/exception.cpp, line
113.
rake aborted!
Command failed with status (): [bin/mspec ci -B full --background...]
/Volumes/HD/opt-snow/src/rubinius-master/Rakefile:20
(See full trace by running task with --trace)

-- 
--- !ruby/object:MailingList
name: rubinius-dev
view: http://groups.google.com/group/rubinius-dev?hl=en
post: [email protected]
unsubscribe: [email protected]

Reply via email to