# Fastthread on x86\_64?

**URL:** <https://www.ruby-forum.com/t/fastthread-on-x86-64/106636>\
**Category:** Ruby\
**Created:** [June 12, 2007, 5:33pm UTC](https://www.ruby-forum.com/t/fastthread-on-x86-64/106636 "2007-06-12T17:33:02Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![regularfry](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/45deac/32.png) [@regularfry](https://www.ruby-forum.com/u/regularfry)\
**Post date:** [June 12, 2007, 5:33pm UTC](https://www.ruby-forum.com/t/fastthread-on-x86-64/106636/1 "2007-06-12T17:33:02Z")

</div>

Is this a known-bad combination? I’m installing onto Debian Etch, and:

$ ruby -v  
ruby 1.8.5 (2006-08-25) [x86\_64-linux]

When I gem install fastthread, I get these:

In file included from fastthread.c:12:  
/usr/lib/ruby/1.8/x86\_64-linux/ruby.h:31:21: error: stdlib.h: No such  
file or directory  
/usr/lib/ruby/1.8/x86\_64-linux/ruby.h:35:21: error: string.h: No such  
file or directory  
/usr/lib/ruby/1.8/x86\_64-linux/ruby.h:45:19: error: stdio.h: No such  
file or directory  
/usr/lib/ruby/1.8/x86\_64-linux/ruby.h:67:20: error: alloca.h: No such  
file or directory  
…  
(many more errors follow)  
…  
make clean  
Successfully installed fastthread-1.0  
$ irb  
irb(main):001:0\> require ‘rubygems’;require ‘fastthread’  
LoadError: no such file to load – fastthread  
from  
/usr/local/lib/site\_ruby/1.8/rubygems/custom\_require.rb:27:in  
`gem_original_require' from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:27:in`require’  
from (irb):1

I’ve probably forgotten something obvious, but I can’t see what. Anyone  
got any clues?

---

<div class="post-metadata">

**Author:** ![regularfry](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/45deac/32.png) [@regularfry](https://www.ruby-forum.com/u/regularfry)\
**Post date:** [June 12, 2007, 5:36pm UTC](https://www.ruby-forum.com/t/fastthread-on-x86-64/106636/2 "2007-06-12T17:36:02Z")

</div>

Alex Y. wrote:

> Is this a known-bad combination? I’m installing onto Debian Etch, and:

Never mind… apt-get install build-essential was the vital step.  
_slaps forehead_