rbx-build coredumps on FreeBSD

[xxx]

Hi,

I'm attempting to build HEAD on my FreeBSD 8.1-STABLE box but rbx-build coredumps when it's used in the build process.

$ rake install

<build stuff>

** Execute nkf.so
g++ -shared -lstdc++ nkf.o   -L.  -o nkf.so
** Execute build
/usr/home/pope/git-sources/rubinius/bin/rbx-build extconf.rb 
** Invoke extensions:openssl (first_time)
** Execute extensions:openssl
Building openssl
rake aborted!
Command failed with status (): [/usr/home/pope/git-sources/rubinius/bin/rb...]
/usr/home/pope/.rvm/gems/ruby-1.9.2-p0/gems/rake-0.8.7/lib/rake.rb:995:in `block in sh'
/usr/home/pope/.rvm/gems/ruby-1.9.2-p0/gems/rake-0.8.7/lib/rake.rb:1010:in `call'

<more errors>

It's rbx-build itself causing this problem - it segfaults just running it from the command line without args.

I've put the entire build log up at https://gist.github.com/760476 in case it's helpful.

I guess I could use the port, but would prefer not to if I don't have to.

[brixen]

Would you please run bin/rbx -v in a terminal and gist that.

[xxx]

Sure. https://gist.github.com/760560

If I create the runtime directory, I instead get
Runtime exception: Unable to load /home/pope/rbx/runtime/platform.conf, it is missing
as the error.

I'm configuring with ./configure --prefix=/home/pope/rbx

[brixen]

For now, do not configure with a --prefix. Just run:

./configure
rake

[xxx]

ok

$ bin/rbx -v
Segmentation fault: 11 (core dumped)

[brixen]

Do you have a ~/.rubinius_last_error file? If so, could you gist it?

[xxx]

I do, but not much in it. It's so short I'll just put it here.

Rubinius Crash Report #rbxcrashreport

Error: signal SIGSEGV

[[Backtrace]]

[brixen]

Could you install the ports one just for an additional data point? I'll have to create an instance of FreeBSD 8.1 to track this down. Are you using a 32 or 64-bit version?

[brixen]

Oh, there's one more thing you could try:

./configure --without-execinfo
rake

[xxx]

--without-execinfo does it. Thank you.

There's a test failure but there's already an issue open for it, so I think I'm good to go now.

Thanks again.

[dbussink]

Are you sure you're running the latest head? What revision number are you running?

The execinfo issue has been fixed, so it should not happen anymore. If you're using RVM, please try to uninstall rbx-head first and reinstall it after that.

[xxx]

I was using rev 9f2d7d8 for all of this. I had the same results whether I used rvm or not - this is the first time rbx has ever built successfully on this machine.